SetActorState can cause ghosts
Posted: Sun Mar 21, 2010 12:08 pm
I'm just flagging this up because it just happened to me and it possibly needs some consideration. I don't think it is a bug but it may be viewed as undesirable behaviour and, perhaps, Graf or Randy may want to treat it as a bug.
Anyway, I was messing with a script that did an enemy some damage and I wanted to make sure that the enemy (which has a very low pain chance) would go into its pain state. So, I used SetActorState to force the enemy into its pain state after damaging it. However, in the course of me messing around, I noticed that the enemy didn't die no matter how often I damaged it. Then I noticed that it had also become immune to "kill monsters" and MDK.
What happened (I think) is that the script killed the enemy but them immediately forced him into his pain state (which then went back to his see state) and the enemy had now become a ghost in the same style as those of an archvile-resurrected crushed body.
So, given that ghosts are generally viewed as being undesirable, I thought that it might be worth flagging up but, like I said, it's probably not a bug as such, more a case of "don't do that". It's something to be aware of though and it might be something that Graf or Randy will want to plug.
Anyway, I was messing with a script that did an enemy some damage and I wanted to make sure that the enemy (which has a very low pain chance) would go into its pain state. So, I used SetActorState to force the enemy into its pain state after damaging it. However, in the course of me messing around, I noticed that the enemy didn't die no matter how often I damaged it. Then I noticed that it had also become immune to "kill monsters" and MDK.
What happened (I think) is that the script killed the enemy but them immediately forced him into his pain state (which then went back to his see state) and the enemy had now become a ghost in the same style as those of an archvile-resurrected crushed body.
So, given that ghosts are generally viewed as being undesirable, I thought that it might be worth flagging up but, like I said, it's probably not a bug as such, more a case of "don't do that". It's something to be aware of though and it might be something that Graf or Randy will want to plug.