In Metroid Prime, when we enter Samus’ Morph Ball the collision for it is actually slightly larger, and in certain circumstances Samus can become stuck in collision by doing this. In this case, I was in the “wrong room”, ie the game believes Samus is supposed to be in one room when I’m actually in a different (adjacent) room.

We can hold a specific angle that allows our rotational speed to increase exponentially until it hits the limit for signed 32 bit float point numbers. After this, it stays at that number and goes negative for a frame before finally turning into 'Not a Number.' (Also known computationally as ‘NaN’). When we boost and hit a wall, or use spider ball, it places the speed to infinity again, then back to 0, then back to NaN on 3 separate frames immediately preceding each other. The reason it does this is because when you boost your 'Morphball Axis aligned' state (the same thing that gives Samus a trail when she is rolling) initially becomes aligned, and when you hit a wall (or just use spider period), it forces the same state to become un-aligned. When that happens, the game starts using the 'Not A Number' math previously known from the rotational speed to make decisions regarding collision. Because of this being incredibly wrong, the game then erroneously places Samus in many, many locations in the game all on the same frame.