If i recall correctly, it also works if you have the game in a love, and you get the source base directory, that will be the directory that contains the love file.

About resolution I got it, but how can I make them fit in all screen sizes by programming? Depends on whether your game allows the visible area of the world being differently sized on different resolutions or not. If it's allowed, then you just show a bigger chunk of the world, no extra scaling and...

Disable os-wide shortcuts, or remap them if the os allows you that, or remap the pause key to p or something if it doesn't.

For me, they're constantly twitching, but that's an issue with my window manager.
Either try math.floor-ing the x and y coordinates of your squares in your love.draw, or try running it in fullscreen, whether the issue exists there as well, or not.

Don't know about your android question, but for the other, here's some code as an example: local song local loopStart, loopEnd function love.load() -- mp3 files can't "wrap" precisely, due to how they work, so don't use them. song = love.audio.newSource("song.ogg") -- good for th...

You're welcome. :3 Technically, it's enough to modify the SoundData, and queue that up with the QSource, if using that; but it could be done faster of course, using pure FFI arrays. Also, OpenAL does have a built-in way to queue data constantly, though löve itself doesn't (expose it nor implements i...

Unfortunately, even if you modify the SoundData object, it won't have any effect on an already playing source unless you load it into the Source again. But, i did experiment with realtime sound generation myself, and currently, lpghatguy's QueuableSource module would be something you should try in m...

Hey Ivan, First, nice work on this awesome little lib! (Though it won't deter me from trying to come up with something else still! : ) Second, i have a question; running your relative time test lua made me aware of a small-ish issue, namely that i used unnecessarily long phrasing in at least the &qu...

It's a tricky situation, since if when you're implementing the multiplayer, you decide on a way to communicate between clients, it may conflict with how you built the singleplayer parts up, leading to you needing to rewrite that to support multiplayer. I personally would think out how the communicat...

Well, since the game already has the images stored inside somewhere, either in one or more files (atlas or individual ones), if you do use multiple atlases, then i suppose you could also store a number at the start of the file, denoting which tileset to load.