Hello! I've now come across this problem in two very different custom scripts, so I thought I should report it. Basically I think that sometimes a script will update a variable internally but not simultaneously within the Fsm it is used in. For example, I've got a test project doing some arrays to spawn a very basic procedural generated box terrain. If I have a state machine assigning height to each X/Z coordinate box, and I use debug scripts I can see that everything is generating correctly, but for some reason within the Fsm the height variable is being assigned to the NEXT box in line, resulting in one box being at 0 height (due to a null value being assigned). I've since discovered this in a completely different project where a string is being updated a couple times within a function and part of the time the final output is not the correct string in the Fsm but appears correct in the internal Debug script. I can send a copy of the array project via a pm link if you'd like to see it for yourself.