Unkillable Barons in Seasons.wad

[Nash]

WAD file: http://www.mediafire.com/file/d19d89037 ... s.zip/file

Download cblood.pk3 from here: download/file.php?id=33887

How to reproduce:

1) Load Season.wad and cblood.pk3 in that order
2) summon BaronOfHell
3) MDK the Baron replacement to attempt to kill it

The Baron will not only survive, it will also become an un-interactable enemy that lives forever and cannot be damaged (but they can still kill you!).

[Graf Zahl]

Can't fix. This happens because that mod contains a Dehacked patch that interferes with the replacement. The replacement takes place before Dehacked gets applied so what you end up is a real baron with some states swapped around and your altered Baron which now has its states pointing to bogus content.

[Xaser]

This seems really fishy. cblood.pk3 isn't touching the monsters' states -- how can the states get messed up?

Related: I ran into this problem with another wad (an in-development thing, but the scenario is the same as Nash's), and the symptoms are identical, which is way too coincidental for random corruption.

Weirdly, the XDeath state seems to work just fine in my experience. That isn't covered by Nash's test case just yet, but it's probably something to add & check.

[Graf Zahl]

This seems really fishy. cblood.pk3 isn't touching the monsters' states -- how can the states get messed up?

The states of the original Baron are fine. It's the states of the replacement that get messed up, because the Dehacked patch swaps some around and only does it in the original.

[Xaser]

Hmm, all right -- so in other words, the states get modified, but the state labels on the replacement are still pointing at the old (now "wrong") locations? Seems to clear up the mystery if so.

[Graf Zahl]

Yes, that's precisely what happens.

[Xaser]

Thanks -- makes sense, then.

Guess that means I don't need to troubleshoot my own (ZScript) code, then. I thought that may have been causing a problem originally.