MAPINFO AddDefaultMap reading

[Daniel]

Hi

I'm trying to make a "AddDefaultMap" section on a MAPINFO lump in PWAD, but the properties aren't making any affect on Doom default maps. Seems that the engine reads first the "Oficial" map definitions in ZDOOM.PK3, then afterwards, it reads MAPINFO lumps in PWADs. This makes the "AddDefaultMap" option useless, because the map data for all levels are based on the first DefaulMap. Is this proposital? This seems to be a bug...

[Kate]

AddDefaultMap is not for existing definitions, it is only for new definitions following it. It was intended to be used to be combined with DefaultMap so you don't have to type all of the options at once:

Code: Select all

DefaultMap
{
    [...]
    gravity = 800
}

[...maps...]

AddDefaultMap
{
    gravity = 200
}

[...more maps...]

[Blzut3]

I've seen this kind of post a few times now, so out of curiousity what are you trying to set retroactively? A block to do this could be added, but given the purpose of mapinfo I'm not sure it's the proper way to do things anyways (that is to say most of the map properties really are more for setting based on the design of the map).

[Daniel]

I thought that we could change internal maps... but seems to do so, we have to "copy and paste" original DOOM 1 and 2 map definitions.

[Xaser]

The important part was this bit:

out of curiousity what are you trying to set retroactively?

Though the way defaultmap works won't change, listing what specifically you were trying to do might help identify something that might be implementable as a global setting (in the gameinfo block). Otherwise, nothing will happen.