What does return?

If it's something other than "C", try to switch to the standard C locale. This should fix the issue.

The basic concepts would be the same in both cases. You just have one player instead of many players. You may be overestimating the ingenuity of your work if you're convinced that people will be so eager to steal it, even though you can't even figure out how to do it in the first place. You're in wa...

It made me wondering though, couldnt LOVE just make an exception to its linear filter for 0.0 alpha pixels to blend with neighbors only by alpha channel and not the colors? That's not LÖVE's linear filter, that's how the blendmode formula in the hardware works. You can use premultiplied data instea...

programmatically you'd have to do the equivalent of this: Or just convert to premultiplied alpha: local img = love.image.newImageData('tex.png') img:mapPixel(function(x, y, r, g, b, a) return r * a, g * a, b * a, a end) -- but you have to remember to set the correct blend mode: love.graphics.setBle...

That's because the transparent pixels have a color, too - they are probably white in your texture, and filtering causes that white to bleed into the purple. Make them the same color as the interior and the issue will disappear.

I'm not asking for help on how to make it work, I'm giving suggestions on how to make it better. If there's nothing to run, don't show a run button. A basic UX principle.

When I select the one example folder in this and click run, nothing happens. Maybe show only buttons that actually do something? The example code: -- Load an image and display it local image function love.load() image = love.graphics.newImage("assets/chest.png") end function love.draw() lo...

Yeah, it's not really in a finished state that would be fit for release. The ROM loader alone is a bad hack that restarts LÖVE when you drop a file, because the JIT shits the bed really badly if you run different ROMs in the same session. Never even tested it on Windows or MacOS. I had to "figh...

A well written library should account for that and allow to be required from any path. I personally would steer clear from libs that don't do this because it's a red flag, and you're probably dealing with bad code that will have more problems down the line. You can modify package.path (pure Lua) or ...

For integer constants you can do this in LuaJIT: local ffi = require('ffi') local MyEnum = ffi.typeof([[ struct { enum { CONST_A = 23, CONST_B = 1337, CONST_C = 42, }; } ]]) print(MyEnum.CONST_B) -- 1337 MyEnum.CONST_A = 1 -- error: attempt to write to constant location This works for integers only ...