Ignore DEHSUPP

[NiGHTMARE]

For the Negative 1 project, a few non-replacing things have been added via DEHEXTRA. A couple of people wanted the project to be ZDaemon compatible, so a DEHSUPP was created for players using that port.

Unfortunately, when GZDoom detects the DEHSUPP lump it will automatically disable the DEHACKED lump. My request is therefore for a way for modders to make GZDoom simply ignore a DEHSUPP lump if it's present, possibly via GAMEINFO or MAPINFO.

Thank you

[wildweasel]

Any reason why the DEHSUPP and companion DEHACKED lumps for the ZDaemon version couldn't be in a separate file?

[NiGHTMARE]

I was thinking in terms of player convenience, and possible oversight. For instance, I've lost count of the number of people who've asked why they can't get BTSX to work and it's because they're only loading one of the two included wads.

[Gez]

The thing about DEHSUPP is that it allows ZDaemon's DEHACKED to extend to stuff not normally covered by DEHACKED. Which means that if it's present, the assumption can be that it's needed, and if it's needed then the DEHACKED lump is not going to be compatible with ZDoom's own DEHACKED support, because it'll refer to things and frames that are not from vanilla Doom, Boom, or MBF.

The proper way is then to make equivalent changes using ZDoom's own control lumps (ZMAPINFO, DECORATE, etc.).

[NiGHTMARE]

Ah, but recent versions of GZDoom *can* use things and frames not in Doom, Boom, and MBF. Support for the DeHackEd extensions from Doom Retro and also found in PRBoom/UMAPINFO, etc. was added back on 31st December last year.

(Specifically things 150-249 and frames 1089 to 4000 are now available for use.)

ZDaemon of course has not added these extensions, but DEHSUPP can be used to replicate them. Hence this request