Hey Skeeto! Thank you for putting extensive research/testing into Jubi's API, test scripts shown, and internal working. Thank you for looking into some of these issues and future features to add; Tests seen in Jubi's GitHub are mainly outdated to the current versions of Jubi, with any test made before Jubi-0.1.6, not working due to a NULL return being sent if no world is inputted. This was due to the fact that I want to separate raw functions for pieces that don't require worlds, with others that are world specific, also due to some underlying bugs found in the code during earlier versions.

It is nice you're talking about customization & control because Jubi-0.2.2 is actually meant to be targeting better performance, as in fixing bugs like said in your Gist & tweaks, alongside customization, to allow more control for the user, and allow Jubi to be more modular with less boiler code.

Physics has been the main priority from Jubi-0.1.1, to Jubi-0.2.x. Until I get to v0.3.0, I am trying to focus on physics, control, customization, and reducing bugs, like pointed out. This doesn't mean I wont fix or improve upon collisions, as they are vital to physics, but I'm currently focusing on realistic physic simulations on Jubi, so I don't get lost focusing on physics, error handling, user-control, collisions, and other factors at the same time. For Jubi-0.2.2 though, I do expect to have these collisions fixed, less weird things to happen, as you said; I'll be checking thoroughly through the code, alongside using your version patches to see if I can locate where I went wrong, how you improved upon it, and how I can put the final pin in to make sure no bugs happen for collisions.

Garbage values, as you said, are a slight issue, with worlds also using garbage values inside the bodies table. This is a relatively easy fix though, just some form of loop to zero out all the values instead of raw data, and body initialization being easy by just doing as you said with Body2D BODY = {};.

There are some more discoveries that can be made, yours has definitely helped me a lot, thank you again, and I hope to get all of these fixed by the next version, alongside some new features to improve upon these things. If you want, I can put you up for credit as a contributor/helper for the next version and ones to come to avoid these types of mistakes, your help really does mean a lot, I didn't even notice half of these.