That’s why I add the ID of the colliding objects to a list, deactivate them, and only reactivate them once the loop is over. Doing so in a loop, you might wonder how the loop ends if the object ends inside the collision area. I then align the object to the block, without the additional pixel and I get a reliable collision detection every frame, since I leave the object inside the collision area.

This way I don’t rely on the weird way the backed-in functions works.

To solve the issue, I simply check the collision 1 pixel ahead in the direction of the moving block. From my observation, when the player is pushed by a block and perfectly aligned with it, the next frames return no collision despite the block colliding and moving toward the player. When moving an object with a speed inferior to 1, this speed is insufficient to trigger the collision every frame. They don’t trigger very accurately, and the two functions return result a bit different in the decimals realm. Turns out, the problems were the place_meeting() and collision_rectangle() functions. The object was not aligned and clipped haphazardly in front of the moving block. I spent quite a lot of time trying various logics to no success. I spent quite a lot of time trying to figure out a way to push my character object with a moving block and what was, in my mind, really easy turned out to be a nightmare. Of course the camera has to lag behind and make it look laggy.

Gamemaker studio 2 collision