It seems to me that you have a problem understanding OOP in general, not necessarily OOP applied to Lua. IMHO, the way classes work in Lua is overcomplicated and the basic OOP principles get lost under a layer of unfriendly syntax. I'd suggest doing an OOP crash course in a language that's been buil...

First off, the user data can be anything. It's just a reference that you can set to whatever info you want the fixture to have, in order for you to be able to distinguish between them in the callbacks. It can be a string, or a table or an instance of a class that you wrote. Second, you should use Az...

@i_love_u : you need to reset the jump counter only when the player touches the ground again. You are currently resetting it on all collisions. In the beginContact() callback, you need to check the identity of the two fixtures and, if it's the player and the ground, reset the jump counter. You will ...

Thanks for the update, random generation works properly now.

Why would one stream while coding? What's the message to transmit and what's the audience?

@drunken_thor : speaking of optimizations and speed, while nosing around in the code, I think I noticed that the library currently draws all shadows, for all bodies, for each light. From what I can see, it doesn't take into account whether there is something between a body and a light, or whether th...

This is really helpful for debugging physics issues, I was thinking about writing something similar for my own use but found this first :) Thanks a lot. I do have one observation to make: your math.randomseed(1) call will forever break random number generation in the project that is being debugged. ...

Sorry, I might not have been clear enough - I was thinking that each rayCast() call went to it's own thread; things would've been a bit more complicated if it were so.
Thanks for the clarification

From what I can see at a glance, you're calling check_collision() from love.update(). The update() method is called loads of times per second which means that the "img_hit" image stays on for a frame, at most. You need to implement a mechanism that allows the image to stay as "img_hit...

Casting a ray through the map has big chances of hitting more than one entity. For each entity, the callback method is called. The wiki says that: You cannot make any assumptions about the order of the callbacks. http://www.love2d.org/wiki/World:rayCast However, I need to get these callbacks in a ma...