[1.4.8 r833] Mapinfo Thing - Is this intended?

Bugs that have been resolved.

Moderator: Graf Zahl

Locked
dark-slayer-201
Posts: 149
Joined: Thu Jul 16, 2009 14:31

[1.4.8 r833] Mapinfo Thing - Is this intended?

Post by dark-slayer-201 »

Code: Select all

Execution could not continue.
File E:/Games/Doom/GZDoom/mapinfo.pk3 is overriding core lump mapinfo/doom2.txt
I use this mapinfo for using different High Quality music and GFX with different iwads. It used to ignore this error, but not anymore.
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Re: [1.4.8 r833] Mapinfo Thing - Is this intended?

Post by Graf Zahl »

Yes, this is fully intended to prevent you from releasing screwed up mods. The internal MAPINFOs contain stuff that's subject to change without notice which would break your mod.
User avatar
Gez
Developer
Developer
Posts: 1399
Joined: Mon Oct 22, 2007 16:47

Re: [1.4.8 r833] Mapinfo Thing - Is this intended?

Post by Gez »

The problem with wholesale replacements like what you did is that if there is one little addition -- like externalizing another hardcoded thing into the gameinfo block for example -- then the whole game crashes down. Because before that piece of data was in the exe, now it's expected to be in the pk3, and unless you update your override mod it will not be. The game tries to access it, finds nothing, and aborts or crash.

You can still do you mapinfo replacement thing. Just make a different file for each iwad and use the ini's autoload feature to load them as appropriate. This way, the core mapinfo files are still read entirely and additions do not provoke crashes.

Another example, when the generic damage factor feature was introduced, the updated actor definition for Actor was at first forgotten by mistake. As a result, the game didn't crash, no, but it defaulted to a default value of 0, meaning that nearly all actors were now immune to practically everything since they had a damage factor 0.

So you can expect only problems from doing things this way. You should not try to be "clever", especially not when there are already perfectly working methods to do what you want to achieve.
Locked

Return to “Closed Bugs”