Update 1.2 Changes since 1.1: Added character filters for limiting what glyphs gets outputted. Added [in] parameter 'imageFile' for specifying the filename of the input image. Added "builtin" as a special value for the fontFile parameter. Added --silent option for disabling output to stdo...

Update 1.1 Changes since 1.0: Outputted glyphs are packed a lot better. Added [edit] parameter 'trim' for controlling trimming of transparent pixels around glyphs. Added [out] parameter 'imageBounds' for controlling the dimensions of outputted images (e.g. power-of-two). Added [out] parameter 'imag...

Only the files you require() will actually run, so if you only call require("collision_circles") in main.lua then it doesn't matter what arrow_follow.lua or any other file contains as those will not run. main.lua: -- Only uncomment one line: -- require("collision_circles") -- Unc...

Just have a single line in main.lua where you require() the file you want to run.

https://i.imgur.com/F8BwYA7.png This is a command line program that converts a simple custom bitmap font format to BMFont (loaded with love.graphics.newFont ). There is also some basic support for rasterizing TrueType fonts. Why does this exist? LÖVE supports two bitmap font formats: BMFont, and it...

@Jayverb
Yes. Just look at what the updated default exporter outputs to see where you can get the coordinates.
No problem!

Update 1.8 Changes since 1.7: Particle systems can now have individual position offsets. Fixed particle path previews not using the specified area distribution. Templates: Values have been moved to the 'exported' namespace (i.e. particleSystems is now exported.particleSystems). (Values are also ava...

That would be great for placing stuff on a background image :) Yeah, I was thinking that. How would I put this in the main.lua ? So I can access a parameter say on particleDatas[2] for example. Just access parameters with the dot syntax. In the example there are two particle systems, which means th...

@Jayverb
Particle systems' position and movement in the game is something that's outside the scope of this program I think, though I can see cases where exporting an "initial position" for particle systems could be useful. I'll add that to the todo list.

@Jayverb Instead of making anything in the exported module global, just say particleDatas[1] or particleDatas[2] etc. in main.lua to refer to the different particle systems if you don't want to use loops like in the example project. It's generally bad to create globals if it's not absolutely needed....