bump.lua - minimal collision detection lib

[kikito]

Hello there!

I've spent more time that what I wanted doing this, but I'm finally releasing this - another collision detection lib! It's called bump.lua

Note: This post is about an old version of bum. Post about bump.lua 2.0

The latest version can always be downloaded from github:

https://github.com/kikito/bump.lua

What does it do? Well, it does collision detection.

Comparison with HardonCollider

(TL;DR - if you are making a game with only bounding boxes, and you don't have incredibly fast objects, use bump. Otherwise, use HC)

So it is very similar to HardonCollider. But it does several things differently.

• Well, first and foremost, bump only handles axis-aligned boxes. No polygons, no circles, not even rotated boxes. If you wanted to use bump.lua with those, you would have to implement the collision part for those objects yourself (or just use HardonCollider).
• There is only one instance of bump at any given time. This means that you can't have several "worlds" occurring simultaneously, like you can in HC.
• bump doesn't take velocity into account when making calculations. This means that if you have very fast objects, they might "go through" others. In bump.lua, you have to pad your object's velocity.

Those are the negative parts. The good:

• The interface is simpler. For example, since there are only boundingboxes, you just have a method for adding stuff (bump.add) and one for removing stuff (bump.remove).
• You don't need to use "bump objects" - you can use your own objects. The catch is that you have to tell bump how to get a bounding box for any object that you want to insert. By default bump will just try to call object:getBBox() to get the bounding box of the object (4 numbers - left, top, witdh, height). But you can change how the bounding box is calculated with the bump.getBBox callback.
• You don't need to tell bump when an object has changed positions - it tracks object movement automatically.
• The two main functions are called bump.collision(item1,item2,dx,dy) and bump.endCollision(item1, item2). Since there is only one instance of bump running at any given time, you can define them the same way you define LÖVE callbacks, without having to "pass them on to a constructor" (see the demo for an example).
• Groups/Categories/etc are handled via a callback, called bump.shouldCollide(item1, item2). If you make it return false, item1 and item2 will not generate collisions.
• You can use bump as a spatial hash - bump.each(f, l,t,w,h) will apply the function f to all the items in the box defined by l,t,w,h.
• The "update" function in bump is called bump.collide(). Called without parameters, it will calculate all collisions. But if you pass it a region with l,t,w,h, it will calculate collisions in that region only.
• There are some heuristics in how the order of the collisions executed. This should help when doing a platformer game, for example.

Demo

I'm attaching a platformer demo. It features a player character (move him with the arrows), a random blocky level, and 20 "gold coins" to pick up. The game is pretty much impossible if you just "jump around" to find the 20 gold coins. So I've included a "fly mode", which can be toggled on an off with the right shift key. Or you can try re-generating the level with the return key.

There is also a debug mode which will show you the underlying spatial grid, as well as the FPS/memory used (activate it with the TAB key).

bump-demo.png (13.12 KiB) Viewed 19989 times

My next step with this library is using it on battle-cry. Please try it out and let me know if you have any questions or comments.

EDIT: Attaching demo with v1.2. I'm leaving v1.0 attached for performance comparison

[Zeliarden]

Yo! Cant move the player.

[kikito]

What do you mean? Are you using the arrow keys?

[TechnoCat]

The demo works great for me.
What is so great about these collision detection libraries is that they remove days of dev time from the beginning of projects.

[ishkabible]

Ya, I'm having major issues with the controls. as soon as it hit somewhere I couldn't move. I went into fly mode and then I could only go up; I couldn't fall

[Nixola]

I've got no problems at all with the demo, except for the FPS dropping down to 20 when I activate debug mode, but I'm on a netbook so it's ok

[dreadkillz]

Nice lib! The demo works fine for me (Windows 7 64)

[kikito]

Ya, I'm having major issues with the controls. as soon as it hit somewhere I couldn't move. I went into fly mode and then I could only go up; I couldn't fall

That is weird. It means that there's something wrong with the left-right controls. I'll check it out.

[dreadkillz]

Just a question from trying to learn from your code. I'm a little confused by your colon syntax. I thought it would be used to pass a table as an argument to the function, but you are using it to pass a string I think.

Here's the snippet from your love.draw:

Code: Select all

  love.graphics.print(("coins: %d"):format(player.coins), 10, 10)

So for the above code, you are passing ("coins: %d") to format?

[Nixola]

Yes, it's passing a string to "string.format"; every string has a metatable with the field __index similar to this:

Code: Select all

function(t, i) return string[i] end