MAPINFO / UMAPINFO

[Thelokk]

I've been heavy on abusing this forum lately, so going to get straight to the point:

If I want to have as much cross- platform compatibilty as possible, should I use MAPINFO or UMAPINFO to define level names, skies etc? Even better, can I have both lumps in the WAD so the port picks and chooses, or that will create compatibility issues? From my tests it seems UMAPINFO works by default in more ports, but it can't do some stuff I really want that MAPINFO can (ie removing story text and other non-progression stuff). Thanks!

Edited March 25, 2022 by Thelokk

[ViolentBeetle]

You can have multiple, some would take priority based on port. UMAPINFO is supposed to be cross-port and also less of a chore due to actually applying default values. ZMAPINFO might be needed to disable jumping and the like, if you are into this sort of things.

[brick]

14 hours ago, Thelokk said:

From my tests it seems UMAPINFO works by default in more ports, but it can't do some stuff I really want that MAPINFO can (ie removing story text and other non-progression stuff)

UMAPINFO can actually do quite a bit more than you'd think, including removing story text (use intertext = clear on a map whose exist would normally trigger these, such as MAP06; use intertextsecret = clear for MAP15 and MAP31 to eliminate the secret exit texts), adding story text at any map you want (use intertext = "text" or intertextsecret = "text"). You can even change behaviours of boss monsters (such as having Cyberdemon kill end the map on any map other than E2M8, or Spiderdemon death NOT end E3M8). Check the Doomwiki page for all the possible keys. MAPINFO can do a lot more things though, such as forcing specific behaviour for that map on or off (jumping/crouching/etc; regular old-syntax MAPINFO can do this, you don't need to go for the ZDoom-only ZMAPINFO), but it'll work on fewer ports.