Just adding: Youre trying to set a bolean using if cases on a bolean. Thats just adding extra steps, if you dont have anything else that uses it just do it in one go: if (0 > platformer.a.corner_lb_x) and (0 < platformer.a.corner_rt_x) and (platformer.y > platformer.a.corner_lb_y) and (platformer.y ...

It means my editor flags the function as not having a matching end, it gets eaten at line 18.
"if true then" < why have you came up with this? This line effectively is not exectuted as if true cancels itself. But it eats an extra end.

line 11 is not closed.
Get an editor with block checks, really handy.
Also look at line 18 where you have a mess.

It is whatever you want it to be.

https://www.lua.org/pil/
the free version may be 20 years old but still works.
Read the first 3 parts.

Löve hides away a lot for simplification. The main loop for example, questionable if one can learn program flow that way.

You should use the Os cursor for this, the lag is annoying.
Odd style choice for the red cards, i find it unpleasent to see the card red instead the heart.
Else it plays solid.

Iterating with:
load(value)()
will work but you should really save the table contents as function instead strings.
t = {function() lg.setColor(1,0,0) end}

Not a Löve problem.
This file doesnt play correctly in mpv either. Its probably too short.

That reasoning feels like the classic "works on my maschine" excuse. And appimages feel like a step back to a time where we had no shared libs. I now in the recent years shipping the entire thing has dramatically grown again, probably because everything grew so big and complicated and has ...

Well the guy quoted the debian packaging guide and they instruct to use the global install. With only one Löve game in there thats a bad example tho. And if you look for other games in the debian repo, they are mostly split into several parts. With some containing only resources and no exectutables ...