ZDoom 2.3.1 released

[MartinHowe]

In an effort to prevent another of Randy's threads being derailed successfully, I have a relevant question....

Ah, well. I tried.

The TAR archive format has been mentioned as a possible supported type... believe me, this thread has been lying broken across the tracks long since

[Xaser]

I wonder why we don't just say "TARchive"?*

*Brought to you by the Save a Syllable™ Foundation.

In all seriousness though, plain TAR has no compression, so what's the advantage of it versus a regular WAD? I guess you can have actual directory structures this way, but ZIP has that too and it's a spacesaver anyway.

[randi]

A tape archive can compress better than a zip, since the directory information can be compressed too (and it doesn't have redundant copies of it, either) and multiple files can be compressed together in one block. The latter property makes it particularly unsuitable for use as a real-time psuedo-filesystem.

[mickey96]

Wow!

Time passes! Just downloaded it. Time to test on LITF I, II and III.

BTW does anyone know how to replace an item, weapon or player properly without any problems and/or warnings.
a simple example: DoomPlayer : PlayerPawn.

[HotWax]

BTW does anyone know how to replace an item, weapon or player properly without any problems and/or warnings.
a simple example: DoomPlayer : PlayerPawn.

Code: Select all

actor DoomPlayerNew : PlayerPawn replaces DoomPlayer

[Nash]

That won't really work though, will it? I thought the only way to properly replace the player is to erase the original DoomPlayer and define a custom one in KEYCONF?

[HotWax]

That won't really work though, will it? I thought the only way to properly replace the player is to erase the original DoomPlayer and define a custom one in KEYCONF?

True. So I guess his example wasn't really that simple.

For most actors you just replace them as above. (e.g. "actor MyHellKnight : BaronOfHell replaces HellKnight")

For players you must still define a new actor with a unique name, but without the replaces keyword. (e.g. "actor MyDoomPlayer : PlayerPawn") Then you need to make a KEYCONF lump with this in it, which will replace the player's normal class with your new class:

Code: Select all

clearplayerclasses
addplayerclass MyDoomPlayer

[Hirogen2]

In Japan, yes. They use YYYY/MM/DD so it's logical.

They use YYYY-MM-DD (or yyyy年mm月dd日) — not YYYY/MM/DD² — and thusly follow ISO-8601. They also write the (full) names of persons in the MSB³ order like the ISO date by default.

²Rule of thumb: '.' for European DD.MM.YYYY, '/' for the Imperial MM/DD/YYYY, and '-' for ISO-8601 YYYY-MM-DD. Nonwithstanding the users who abuse a punctuation with a different number ordering
³Most Significant... Part. oh well.

[Gez]

²Rule of thumb: '.' for European DD.MM.YYYY

I have never seen that used. Only DD/MM/YY, DD MM YYYY or DD month YYYY.

[Phobus]

We had a German language teacher from Austria who used the dots between numbers in the date - I just assumed it was interchangeable.

[esselfortium]

We had a German language teacher from Austria who used the dots between numbers in the date - I just assumed it was interchangeable.

I've always assumed it's interchangeable as well. I have a tendency to use dots between the numbers; oops <_<

[Graf Zahl]

Some countries use DD,MM,YYYY or even DD'MM'YYYY so there's lots of ways to write a date...

[Project Shadowcat]

Or you have someone like me who dates things (on his artwork) without a spacer whatsoever.

[Hirogen2]

Or you have someone like me who dates things (on his artwork) without a spacer whatsoever.

Note to self: backups in electronic format (predominantly, files) use such a format

[Rachael]

I use such a format when I'm supervising and using a computer to document it. I include the full date and time, with no spacers.

Example... the time for this post, in -5 (EST) would be marked as 20090324195835. I timestamp every notable event this way.