BlackBulletIV wrote:No I'm not calling destroy twice.

But that's why it's crashing. (even with garbage collecting stopped)
You have two self.stuck.joint:destroy() functions in Player.lua. It looks like there is a condition where the game ends up calling both.

miko wrote:... so this is why this crashes.

To be more specific, it allocates a huge amount of resources that have to be freed on closing. That takes forever and makes it look like it stopped working.

BlackBulletIV wrote:But... The game doesn't work properly if I don't do that.

I don't see how calling destroy twice on the same joint could accomplish more, it just sets a boolean value.
Well, you have more experience with Box2D and I didn't look through your code. Perhaps someone else knows more?

Actually, it's your code that destroys the joint twice, which makes LÖVE go boom.
The destroy function is not checking if it already has been called, so do it yourself (for now)!

What? Why? Don't tell it's just because it takes a bit for beginners to understand what's really going on. Well, the function is called setFont and not setAndCreateFont. It delivers more than it should! :P I told bartbes once that this makes it easier to fall into this trap and he said: "yes, ...

Create all your fonts at the loading stage. You're wasting a lot of time and memory if you do it on every update. (main.lua line 57)
Make sure you always pass a font object to love.graphics.setFont in the update and draw functions.

How would I go about fixing the lag? The difference you see between the system cursor and your drawn cursor probably comes from vertical synchronization. If vsync is enabled, the graphics card will not send the next frame until the monitor has fully drawn the last one. This means the framerate gets...

I've never seen a list on the wiki. LÖVE should be able to load everything that is on the feature list of DevIL.
http://openil.sourceforge.net/features.php

Some more obscure ones might fail though.

Or where else on Windows can you put them where the EXE will find them anyway? Windows will search in the following places in that order: - The directory where the exe is located that is requesting the library. - The current directory. - The System directory. 32-bit Windows default: C:\Windows\Syst...

Wikipedia has a short list how some C libraries generate their numbers. http://en.wikipedia.org/wiki/Linear_congruential_generator#Parameters_in_common_use I think the last column is also interesting, it shows the range of the random number. The Windows SDK defines the following in stdlib.h: #define...