Don’t worry, it’s coming.
You see, early during the warming up, I realized that I didn’t know a lot about the collision library I had adopted. So, I decided to take extra time learning the ins and outs. Now, you might call this cheating, but heck, it’s a warmup. And besides, I wouldn’t want to be learning it in the middle of the compo, now would I? It’s better this way.
Now, you may be wondering why I’m using a new collision library, bump.lua, in the first place. Well, a few reasons. For one thing, I’ve had big problems with my own platformer code in the past. I normally use the method of checking collision like this, dividing to allow checking against single points. But, when applying this method, I sometimes get glitches like floating a pixel above the ground or not fully moving to reach the wall next to you. Now, I know exactly why these glitches occur, and I even have a slim idea on how to fix it. But bump.lua promised perfect displacement so you will reach the floor and wall every time. And it doesn’t have to be used for just tiles, the same lib can also work for entity collision. Of course, it checks against rectangular bounding boxes instead of my previously known method, but that never worked out so well, anyway. So, I’m using it, while being wary of COMMANDMENT 6, of course. 😉
by quick look your Advanced library sure look advanced, even too advanced. Rules state “All publicly available libraries and middleware are allowed.”, and you have published yours, however, it also states “All game code and content must be created within the 48 hours.” Your library is not generic graphics/audio/3D/mouse/keyboard library, but hundreds of lines of premade game code, and game mechanics. You are supposed to create all game mechanics in 48 hours, not take premade code and change levels and graphics to fit the theme.