Some Rotation Values Break Sprite Collision

[123outerme]

Some rotation values and intersection points can cause sprite collision (using Separating Axis Theorem) to bug out and give off the wrong Minimum Translation Vector. This vector will usually pull sprite1 in instead of sending it outwards. More testing has to be done on this.

[123outerme]

I think this has been fixed by fixing the default MTV the functions would output. Initial testing seems to confirm this, but I'm not sure it was thorough enough to call it fixed.

[123outerme]

Collision was broken in commit c95a51e, but fixed in d032173. Fixed, as in, back to the previous state of not being quite sure if it's 100% working.