A decent alternative is also to just ask users their preferred language when they launch your project, at least the first time. That leaves less room for ambiguity. Of course, this assumes you have localizations available for a given set of languages.

Have you tried debugging how long it takes to open love2d (with an empty project or otherwise) outside VSCode? I have no experience with using that particular extension, but I'd check if it's the whole PC that's affected, or just his VSCode setup.

You'll need to register an account with Apple and Google, both of which (I believe) requiring a fee before you can submit to their respective stores. After that's done, you can follow the steps on the wiki . For Android there might be a more ready-made solution that I might not be aware of, since I ...

Love2d is a framework (or engine), that wraps up libraries like SDL, OpenAL, Box2d, and bunch of others into one package. The purpose of this is to make your life easier, in that it essentially provides a box of tools for you to use - rather than asking you to implement everything yourself (graphics...

To add to the previous answers, there really isn't much you can do to solve this. At worst, you may need to get a different keyboard, preferably one with some implementation of n-key rollover which helps with keyboard ghosting issues. Cheap USB keyboards usually don't have this feature, since they m...

If you know the scaling factor used to scale up the images while drawing, then you just divide the dimensions by the scaling factor, yeah. Of course, that assumes that you know the resulting drawn dimensions of the image. This is because getDimensions returns the dimensions of the texture, it won't ...

If you have an image, you can get its dimensions with getDimensions. Multiply these by your scaling factor.

I believe you need to post your code if you want further help. Particularly that post about your timer being a variable and not a number, which shouldn't be an issue. Essentially, you'd keep your timer variable as-is, but when you display it on-screen, you'd apply math.floor (or other rounding mecha...

It doesn't. Since the behavior is not codified in any official reference or specification as far as I'm aware, that behavior may be subject to changes between versions of lua/luajit. Can think of it like undefined behavior, that may work for you in the moment, but not necessarily in different enviro...

I'm not sure there's any easy way to implement (presumably) Windows-style toolbars directly from löve and lua itself, without modidying löve C++ source code to add the needed hooks and functionalities. You could maybe call some of the Windows system functions via luajit's FFI (eq. CreateWindowEx ), ...