#pannenkoek2012

Like, no developer in their right mind would consider the scenario in which the player uses inhumanly precise inputs to manipulate RNG for 39 days straight and make a pendulum speed up to billions of times its normal speed, crashing the game.

But then other glitches are like the X and Z values being in the wrong order when calculating enemy collision so they end up stuck in endless loops or trying to move past each other.

To try and summarize the problem as briefly as possible, the bug occurs in places where there's a gap in level geometry, and gaps occur because the positions of polygon points are truncated. This only causes an issue if your geometry has T-vertexes, which is a big no-no in modern 3D modeling, and can easily be solved by sub-dividing a few polygons.

Below is an example I found online of a T-vertex that needs to be solved (since explaining what they are takes too many words)

In this example, you can fix the T-vertex by turning that triangle into two triangles.

To put it into perspective, if your 3D models have T-vertexes in the modern era some 3D modeling software won't let you render them without flashing a warning to fix it first.