Misfiring Rules - HELP
KiwiLee
Member Posts: 181
I have a rule that is based on (self.JustSpawned? = true) which is the default in the prototype. This is in each actor at the top so the first thing that should happen when an actor is spawned is it sets up attributes based on other parts of the gameplay and then unticks the boolean so the code doesn't happen again.
This code in is the prototype actor and new actors when spawned are 'pure' clones with no overrides of attributes etc as these are all set in code.
Sometimes when I am destroying one of the clones I am getting the rules being fired in ALL actors on the screen. I know this as I am getting the debug log messages fired. Although not all of them but the two CHANGE ATTRIBUTES are always happening.
So I have a rule within a rule and it appears that the second rule which is based on a game.xxx attributes is the one being fired everytime in all actors in this scenario.
Any tips? Ideas?
Lee.
This code in is the prototype actor and new actors when spawned are 'pure' clones with no overrides of attributes etc as these are all set in code.
Sometimes when I am destroying one of the clones I am getting the rules being fired in ALL actors on the screen. I know this as I am getting the debug log messages fired. Although not all of them but the two CHANGE ATTRIBUTES are always happening.
So I have a rule within a rule and it appears that the second rule which is based on a game.xxx attributes is the one being fired everytime in all actors in this scenario.
Any tips? Ideas?
Lee.