Invalid mobjs continue running their MobjThinker hooks for the same frame they are removed

If, for example, you have two MobjThinker hooks, and the first one removes the object it is operating with, the object will still call the second MobjThinker hook despite no longer being valid.

Pretty sure that isn't supposed to happen.

.

invalidtest.wad - Example WAD creates a custom object and adds the command funny which spawns one instance of it.

MT_FUNNY has two MobjThinker hooks - One removes the mobj, the second prints the result of querying its valid attribute. Both run.

i definitely ran into this before - had to get around it by using mobj.fuse = 1 in the first hook instead of P_RemoveMobj

...oh wow, did we never account for mobjs being removed in-between multiple hooks of the same type? Sounds like something that would apply to other hook types too, not just MobjThinker.

mentioned in issue #551 (closed)