For a checkpointing system, our project uses behaviorless "checkpoint" sprites. When the player overlaps these checkpoints, the global variables cpX and cpY are set to the checkpoints coordinates. When the player dies, we restart the layout, and so long as cpX and cpY arent both 0, we set the player's position to cpX and cpY.
Now, there's a teensy bit of lag when it restarts, and if you hit the "up" key (no other key triggers it, but you can hit other keys along with "up") during this lag, the player starts at the default starting location instead of the cpX and cpY. However, if the player then dies before hitting the 1st checkpoint, they start at the correct one on the reload (otherwise they start at that new checkpoint) provided they didnt hit "up" on the load again.
It looks the variable is being stored A'ok, so I'm wondering if the problem is in the behind the scenes stuff that happens in limbo.
Is there any reason that Construct 2 or the browser would cause this? If not, I'll keep looking for bugs, though for the life of me I cant find one that would cause this. Testing on Chrome