FakeKraid
Member
I'm not trying to be snarky, but is there some reason why bounding boxes are set to integer type while x and y are floating point real type? It was taking me forever to figure out why my collisions started behaving wonky when I unlocked my movement (I previously was using code to snip and store sub-pixel movement to isolate it from collision calculations), and it turns out that it's because my code uses those variables to check for collisions and snap to surfaces, and when my x or y is not a round number that leaves a disjoint there. Is there any plan to make these variables floating point real anytime soon or is there some reason why that can't or shouldn't be done? Either way I'll be creating customized variables to replace those, but this took me completely by surprise.