You could potentially use os.execute, and run some copy commands to transfer those files over. These commands may be platform specifc, like using robocopy on windows. This method may flash a command prompt on users' screens, but if you mean to do the file transfers as a one-time thing (eg. when firs...

If you mean to take the absolute value of a number, the function you're looking for is math.abs: However, if you mean something like a constant value, ie. a value that can not be changed, that's a bit more complicated topic.

Well, as the error warns you, you can not index a function. To illustrate it, consider this minimum example: local function myFunction() end -- an empty function that does nothing myFunction() -- ok myFunction.someValue() -- error, can not index a function The same goes for situations, like trying t...

While it's surprising that your example creates so much garbage, it's not also not particularly special, now is it? There are many ways to fill up RAM (excessive table creation, loading a bunch of assets into memory), force heavy CPU loads (just modifying love.run slightly could do), or cause excess...

Right, I think I intended to do that modification as well (either doing what you did, or assigning to a local variable), but must've slipped my mind.

I believe the issue stems from the following: for i, bulletToRemove in ipairs(bulletsToRemove) do world:remove(bulletToRemove) table.remove(activeBullets, bulletToRemove[i]) -- this line here end I'm reasonably sure bulletToRemove[ i ] will just evaluate to nil in this context, which means that tabl...

Welcome to the forums. The issue is here: for i = 0, totalStars, 1 do stars [1] = { -- the "1" here is the problem r = love.math.random(0,255) / 255, g = love.math.random(0,255) / 255, b = love.math.random(0,255) / 255, a = love.math.random(0,255) / 255, x = love.math.random(0, love.graphi...

You are experiencing this behavior because you are using the world:check function, as opposed to the world:move function. -- change this... local actualX, actualY, cols, len = world:check(player, futureX, futureY) -- to this local actualX, actualY, cols, len = world:move(player, futureX, futureY) As...

All the filters boil down to is that for each collider that you want to update, you provide a function. This function takes the currently updating collider, and the object it is colliding with as arguments. You can then resolve the collision based on the different objects' attributes or behavior (is...

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.