Changes don't take hold

BenSawyer

I was trying to prototype some ideas with this tool. However, in working with it today I've repeatedly made logical changes to actors and then not seen the changes "take hold" with the actors in the environment. It almost seems random what takes hold and what doesn't.

For example, I create a rule to update the Game Attribute game.score to game.score+ some value when an actor is touched. For the life of me I can't get the changes to stick.

I've tried carefully not to have any discrepancies between the prototype parent actor and any actors deployed in the scene. I've screwed around with layers but I've had this problem happen multiple times in different ways and contexts.

Is GameSalad really this buggy and inconsistent?

UPDATE: After completely reverting to previous save point... then deleting the non-updating attribute, and rebuilding it from scratch, it seems to be sticking for now, but I'll be damned if I can understand why it took this to get it to work, I'd tried that before so not 100% sure what made it work this time... back to the pixelmines...

Braydon_SFX

Yeah you needed the load and save attributes :-)

BenSawyer

Actually this isn't a save load problem, the actual code changes don't take hold. Literrally logic that works in one operational prototype doesn't work in another. It's not a question of the variable itself not keeping state.