The formula for the current beat of a song given a song's playing position (in seconds) and a BPM: bpm / 60 * songTime So if your BPM was 120 and the song is at 1 second, then the current beat is 2. This gets a lot more complicated with BPM changes, but if you're not dealing with that, then this sho...

You best bet might be to require busted from love, and not the other way around, then perhaps add an optional flag (e,g, '--test') to test your code when you run your game, though there's a lot of ways to do it from there.

The second best way would probably be to use a bunch of smaller simple shapes, or a polygon. mlib does what you're probably looking for.

You should probably update your drivers on Ubuntu from a different repository from the main. I recall Ubuntu's sources being notoriously outdated.

You're thinking about things too one-sidedly. Opening up Tiled, saving a map, and loading it with STI doesn't take that long at all. Making a tile set and translating map data to game objects is a part of both processes.

If you need to make a game where Tiled isn't suited, don't use Tiled.

I'm gonna put it aside for now, actually. For a lot of the reasons airstruct pointed out, and for a few others, which might be restatings of what's been said anyway: 1) There's not a lot of ways I can create a new language that's based on Lua without being redundant or without becoming what MoonScri...

That's still a good idea, yeah. I'll look into that some other time.

One major feature of Lua that almost every Lua programmer uses, and that heavily influences how it looks, is that there's no need to have a separator between statements. There's one exception to that rule, because the syntax is ambiguous as-is and a statement separator breaks the ambiguity. I think...

Is your aim to retain compatibility with Lua, at least for the not very advanced features? I see problems with that. Not really looking for compatibility here. Just wanting it to look like Lua, since I like the way Lua looks, but not all of how it functions. I listed compatibility on the README, bu...

Like this: local tab tab = { 1, 2, 3, 'foo' } function checkThing( x, y, z ) local remove = false for i = 1, #tab do remove = remove or x == tab[i] end if remove then table.remove( tab, 1 ) end Here's a more complex example: --> (lua) local a, b a = 5 b = 10 do --> (lua) local b a = 15 local b = 20 ...