Because I'm curious if there is a way or not.

Other than the screen dimensions, which can be reached via the love.graphics module, is there any way to access the information set in conf.lua inside the rest of the code? For example, accessing the title and author information, or whether the game is in Release Mode or not.

Hello, friends!

http://www.ludumdare.com/compo/ludum-da ... &uid=11038

To add to the above: when you divide by the magnitude of the vector, you are "normalizing" it. Your original vector was { magnitude * direction_of_x, magnitude * direction_of_y } When you normalize it, you are doing this: { magnitude * direction_of_x / magnitude, magnitude * direction_of_y...

I usually just wrap all my module functions in a table as the end of the file, and return it: local function foo(a) --... end local function bar(a) --... end return { foo = foo, bar = bar, } Alternatively, if you'd rather not write local all the time, declare a table and make functions values in the...

Looks neat, but I'd move away from using the module function to create your modules. It's depreciated in Lua 5.2, so if LOVE ever makes the switch you'd need to restructure all your modules.

The easiest way to solve this problem is through vectors. Before you get a solution, give this a good read to understand what vectors are:

http://www.wildbunny.co.uk/blog/vector- ... rs/vector/

Nicely done. You could improve the game by adding a short "You won!" or "You solved the puzzle" message. The transition between the solved puzzle and the new one is a bit abrupt. I am curious: How do you check if the solution is unique? It looks like he builds the solution, then...