Okay, I've looked at this, and the problem lies with the REMOVE MONSTER action, which really SHOULD NEVER BE USED.
Comments next to the original bungie code say this:
Code: Select all
// THIS IS VERY DANGEROUS BECAUSE IF WE DELETE A MONSTER WHICH IS ALREADY IN A SPATIAL
// THE ATTACK AI WILL CALL GET_MONSTER_DATA ON NONE (which is why this parameter is
// undocumented)
Basically, it makes a single call in the code ("delete_monster") as well as adjusting damage stats (responsible for all the player's %'s and such), and calls it a day. This has two issues. First, delete_monster should NOT be called without doing a lot of extra work to make sure nothing else references this monster.
This is what kill_monster does (it removes all references to the monster, and then calls delete_monster too). In your case, delete_monster actually ends up being called twice (once for remove monster, and once for kill monster), which seriously messes up the integrity of the game. Basically, don't use REMOVE MONSTER.
However, the fact that KILL MONSTER wasn't adjusting the stats is IMHO a bug, and I'm fixing it for the 1.5.2 release. So you should be fine with just using kill monster, and it will work as intended when 1.5.2 ships.
And don't forget, DO NOT USE REMOVE MONSTER.

[/color]
Edited By Myrd on 1138253298