What I currently have is that, on a layout (we'll call it layout 1), I have an object. When you click that object, it teleports you to another layout (we'll call it layout 2), then teleports the player in layout 2 to a specific position. These two events happen because of the same action (clicking and object in layout 1), and are staged in the correct order (go to layout, then go to position). However, when I click the object in layout 1, you are transferred to layout 2, but not teleported to the position.
So, I tried another method. I had it so when you clicked the object in layout 1, you would go to layout 2, the player in layout 2 would be destroyed, then a new player would be created in the position I wanted him to be in. When I tested, the player was once again transferred to layout 2, but the player was not destroyed or created in a new location.
It seems the engine is forgetting the other actions I told it to trigger on that event, and only wants to transfer to layout 2. Layouts 1 & 2 run on the same event sheet, I just can't seem to figure out the problem. Bug, maybe?
Here's a .capx, showcasing the first method I tried: