[library] bump 2.0 – Collision Detection

[Jasoco]

Impressive. It works now. You're the best. Looking forward to the next version. About that first issue, I had originally had the playerFilter on the second call but even then it wouldn't work for me and at some point I removed both and forgot to put both back. Oops. Silly me. The issue had to be somewhere else though. I'll look and compare the code when I get home tonight and see what changes you made. Learn from them. I do make the player narrower and shorter than he really would be anyway.

[ELFUERTE]

I need help understanding how the procedure of moving an object's body works.
Here's my code.
http://hastebin.com/jasapigivu.lua
You can ignore all the love.graphics.print,i used those for debugging.
The player is displayed as the "a" letter on the screen. Collisions dont work ATM. The createBlocks function should work though.

[Apito]

@kikito

Thanks for the quick reply! Also thanks again for your libraries, middleclass is also really helpful. I'm new to lua and game programming (but have some web programming experience) but if I happen to find the cause I'll send it your way.

[kikito]

@ELFUERTE: I strongly recommend that you spend some time indenting code. It might look like a chore at first, but it helps discovering and avoiding bugs surprisingly often. (It also makes it easier for others to review ). Since I plan to release a new version of bump soon, I would recommend you to wait for me to do so; the new version will be easier to use in the base case.

@Apito

[boobeebah13]

error: bump.lua:600: table index is nill

[Jasoco]

We need more context than that.

That line belongs to the World:querySegmentWithCoords function. Are you passing nil values to it?

Edit: Wait, this thread is for version 2.0. That's waaaaay out of date. Why did you bump (lol) this thread? Are you actually using 2.0? Because 3.0 has more features. I don't even know what code is in 2.0.

[NightKawata]

We need more context than that.

That line belongs to the World:querySegmentWithCoords function. Are you passing nil values to it?

Edit: Wait, this thread is for version 2.0. That's waaaaay out of date. Why did you bump (lol) this thread? Are you actually using 2.0? Because 3.0 has more features. I don't even know what code is in 2.0.

Yeah I'd stay away from bump 2.0. Refering to the one who necroposted, that's something that a lot of people do here, and that really needs to be addressed/let's not do that. (Just make a seperate topic for the oldie stuff in support and development)

Anyhoo, the easier answer is to simply use bump 3.0, as no offense to kikito, it is a lot more versatile, it's by far much less of a pita to use (okay kiki let's face it compared to the bump 3 way the bump 2 way isn't even comparable =p), and you'll probably enjoy utilizing it a fair bit more!

[Jasoco]

I don't know why kikito would be offended. I'm pretty sure he knows how much worse 2.0 was. 3.0 was like a total rewrite and made it so much easier to use.

So yeah, don't touch 2.0. Let's let this thread disappear into obscurity in a few months when it finally drops off the first page. (Why are threads never locked on this forum?)

[zorg]

(Why are threads never locked on this forum?)

That, or them being moved to an archival subforum might be a good idea... didn't a thread about these things happen already?

[Jasoco]

(Why are threads never locked on this forum?)

That, or them being moved to an archival subforum might be a good idea... didn't a thread about these things happen already?

Probably, but we should stop posting in here so it can die if no one is going to lock it.