Don't worry, Eamonn, sharing your ideas probably won't hurt you. Either: You were able to finish the game, and someone else did too. Not very probable, and maybe the other guy will be nice.(As in won't sell his shitty implementation of the idea while giving you the middle finger.) You were able to f...

jjmafiae wrote:donst work with love 0.9.0

Love 0.9.0 isn't retro-compatible. Try with Love 0.8.0 .

Löve don't depend of .Net . It depend of: SDL ( http://www.libsdl.org/ ) OpenGL ( https://www.opengl.org/ ) OpenAL ( http://connect.creativelabs.com/openal/default.aspx ) Lua / LuaJIT / LLVM-lua ( http://www.lua.org/ ) DevIL with MNG and TIFF ( http://openil.sourceforge.net/ ) FreeType ( http://www....

Remove the parenthesis after somefunc, or you are calling the function.

When switching to fullscreen, use this. love.graphics.setMode(0, 0, true, v, f) love.graphics.setMode(love.graphics.getWidth(),love.graphics.getHeight(), true, v, f) The first line resize to fullscreen.(if the width and the height are 0, then it become of the screen resolution) The second line fix a...

Use the origin parameters:

I don't think Sprite Batches are made for always moving sprites, and anyways, I think particles systems are optimised the same way as Sprite Batches.

although they might still crash your game. In the worst case, you'll need to go to the write directory of the game and delete the offending level. Use pcall(function,args).It's like a try/catch. It return a boolean, and if succeded, what return the function. If it crashed, it return the error messa...

You can use less particles, but bigger/with more opacity.

If they are custom levels downloaded on the net, the player could execute code without expecting it ("It's just a level, right? It shouldn't be dangerous.") And once a program is executed, it can do anything a user can do. I was writing a blogpost about how customizability is always a prob...