I've discovered a behaviour with event sheets that I find peculiar and I'm wondering if anyone else has discovered it, or whether it's normal.
The game I'm making has various levels that the player can revisit. Each level has its own sheet and each of those sheets access 3 common sheets that govern things that happen on every level the player visits, such as how the player moves and reacts, how the enemies move and react, etc.
As Persist makes it impossible to restart the game from scratch I'm using arrays to save the location and health of enemies upon exiting the level so if the player revisits it they'll find everything as they left it. At the end of the layout information is stored in the arrays, at the start of the layout information is being read from the arrays. The reading and writing of the arrays in on one of the common event sheets.
Now, after that long-winded introduction, here's the peculiar behaviour.
When you leave a level the game is writing to the arrays from the common sheet. I've tested it to make sure of this. When you go back to the level, however, the information isn't getting read back. The only way I seem to be able to make it read the information is by putting all of the array reading rules on the actual event sheet for the layout, not on one of the common sheets.
Is this a known problem? Is it working as intended and I'm unaware of this? I know as far as problems go it's a tiny one, after all, I can copy and paste the reading of the arrays to each layout in 10 seconds, but the behaviour itself makes no sense and I'm wondering if anyone can explain why it is so.