Cross support for "Chocolate Doom"-style autoload directory

[elf-alchemist]

When loading a PWAD, the source port must load the contents of a subdirectory under the autoload/ whose name matches the full name of the PWAD in question, loading files as lumps and WADs as PWADs, after the aforementioned PWAD. Specific IWAD names are also expected to trigger their own autoload, and as such are reserved names.

That is, when loading PWAD, such as the following doom -iwad doomu.wad -file example.wad (treating doomu.wad as a built-in supported alias to the "Ultimate Doom" version of doom.wad), the following order is expected:

1. doomu.wad
2. Contents of autoload/all-all/
3. Contents of autoload/doom-all/
4. Contents of autoload/doom1-all/
5. Contents of autoload/doomu.wad/
6. examples.wad
7. Contents of autoload/example.wad/

The autoload/ is expected to be stored in the port's data directory, such as $XDG_DATA_DIR/<port name>/autoload/ in linux systems.

Any PWAD Name	Choco	Crispy	Woof	DSDA	Eternity	Odamex	Retro	GZDoom	Helion	EDGE-Classic
Auto-generate	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌

IWAD Type	Choco	Crispy	Woof	DSDA	Eternity	Odamex	Retro	GZDoom	Helion	EDGE-Classic
all-all	❌️	❌️	✔️	✔️	❌	❌	❌	❌	❌	❌
doom-all	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
doom1-all	❌️	❌️	✔️	❌️	❌	❌	❌	❌	❌	❌
doom2-all	❌️	❌️	✔️	❌️	❌	❌	❌	❌	❌	❌
freedoom-all	❌️	❌️	✔️	❌️	❌	❌	❌	❌	❌	❌
freedoom1-all	❌️	❌️	✔️	❌️	❌	❌	❌	❌	❌	❌
freedoom2-all	❌️	❌️	✔️	❌️	❌	❌	❌	❌	❌	❌
chex-all	❌️	❌️	✔️	✔️	❌	❌	❌	❌	❌	❌
rekkr-all	❌️	❌️	✔️	❌️	❌	❌	❌	❌	❌	❌
heretic-all	❌	❌️	-	✔️	❌	-	-	❌	-	-
hexen-all	❌	❌	-	✔️	-	-	-	❌	-	-
strife-all	❌	❌	-	-	-	-	-	❌	-	-

IWAD Name	Choco	Crispy	Woof	DSDA	Eternity	Odamex	Retro	GZDoom	Helion	EDGE-Classic
doom1.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
doom.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
doomu.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
doom2.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
doom2f.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
tnt.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
plutonia.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
freedoom1.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
freedoom2.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
freedm.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
chex.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
chex3v.wad	❌	❌	✔️	✔️	❌	❌	❌	❌	❌	❌
chex3d2.wad	❌	❌	✔️	✔️	❌	❌	❌	❌	❌	❌
rekkrsa.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
rekkrsl.wad	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌	❌
hacx.wad	✔️	✔️	✔️	✔️	❌	❌	❌	❌	❌	❌
heretic.wad	✔️	✔️	-	✔️	❌	❌	❌	❌	❌	❌
heretic1.wad	✔️	✔️	-	✔️	❌	❌	❌	❌	❌	❌
hexen.wad	✔️	✔️	-	✔️	-	-	-	❌	-	-
strife0.wad	-	-	-	-	-	-	-	-	-	-
strife1.wad	✔️	✔️	-	-	-	-	-	❌	-	-

⚠️: Should either chocolate or Crispy even have more *-all? Further investigation needed.

[elf-alchemist]

@MelodicSpaceship is there any issue to adding the remaining CQ3VE IWAD entries to Chocolate & Crispy IWAD list?

[MelodicSpaceship]

@MelodicSpaceship is there any issue to adding the remaining CQ3VE IWAD entries to Chocolate & Crispy IWAD list?

In the latest stable versions of Chocolate and Crispy, it appears that the "chex3v.wad" autoload folder doesn't work and it instead uses the "doom.wad" folder. Similarly, chex3d2.wad uses the "doom2.wad" folder. It looks like it's based on what kind of game is detected rather than the actual IWAD filename, so with Chex 3 Vanilla not explicitly supported it detects it as Ultimate Doom and thus uses the "doom.wad" autoload. Therefore, chex3v.wad and chex3d2.wad should stay marked as "not supported".

Additionally, it doesn't seem that Chocolate and Crispy handle REKKR correctly, either. Strangely, Crispy Doom does have REKKR in its IWAD list but it's still being detected as Ultimate Doom (at least on my end). It's thus probably a bug in Crispy's case, though Chocolate Doom doesn't have it in its IWAD list. Therefore, REKKR should also be marked as "not supported", at least for the Chocolate Doom column.

[elf-alchemist]

It's thus probably a bug in Crispy's case, though Chocolate Doom doesn't have it in its IWAD list.

This one's a bit tricky, REKKR as an IWAD specifically has a couple of issues that means it only runs 'properly' on Woof, where even DSDA struggles, mostly boiling down to fault tolerance on texture1/2 related assets, IIRC. For all intents and purposes, Revae has been treating it as a PWAD, instead. Considering that they aren't interested in actively working on it anymore, from the few messages I've seen them post on the DSDA discord server at least, it's likely best to simply just treat it as a plain PWAD, otherwise.

[electricbrass]

This one's a bit tricky, REKKR as an IWAD specifically has a couple of issues that means it only runs 'properly' on Woof, where even DSDA struggles

Is there a list anywhere of what issues has in other ports? Odamex has supported the iwad version of REKKR for a number of years now and I've never noticed any issues.