Return to Question

• AABB collision resolution issues
• Trouble with AABB collision response and physics
• http://gamedev.stackexchange.com/questions/98323/hard-time-implementing-aabb-collision-into-a-platformer
• 2D Platformer AABB collision problems
• 2D Platformer Collision Handling
• Collisions not working as intended
• Checking Collisions In 2D Platformer With Tiles
• And a lot more...

The problem above was solved using David's solution, now I need implement the one-way platforms. The code I have so far is this, I commented the most important parts:

• AABB collision resolution issues
• Trouble with AABB collision response and physics
• https://gamedev.stackexchange.com/questions/98323/hard-time-implementing-aabb-collision-into-a-platformer
• 2D Platformer AABB collision problems
• 2D Platformer Collision Handling
• Collisions not working as intended
• Checking Collisions In 2D Platformer With Tiles
• And a lot more...

The problem above was solved using David's solution, now I need implement the one-way platforms. The code I have so far is this, I commented the most important parts:

Found the problem, I just changed previousBottom < tileBounds.Top to previousBottom <= tileBounds.Top. Explanation:

In the tests the previousBottom was with the value of 126 and the tile top with the value of 128, so previousBottom < tileBounds.Top was true and player was pushed out. In the next update, the player bottom is equals as the tile top, so previousBottom = 128 and tileBounds.Top = 128, the condition is false, and the player pass through the platform.

Found the problem, I just changed previousBottom < tileBounds.Top to previousBottom <= tileBounds.Top. Explanation:

In the tests the previousBottom was with the value of 126 and the tile top with the value of 128, so previousBottom < tileBounds.Top was true and player was pushed out. In the next update, the player bottom is equals as the tile top, so previousBottom = 128 and tileBounds.Top = 128, the condition is false, and the player pass through the platform.