The idea is quite interesting, but I'm not convinced that all possible rectangles are solvable. It's easy to come up with a dead end. For example, I took your fourth example and after the second stage, I placed the next Z on the left differently, and then one more on the right, and came up with this...

I did this myself at one point - for some unknown reason, I have one module that uses a local variable named, and a global for the rest of the program also called mouse. For a while it wasn't an issue, but when I eventually wanted to make use of the functionality of the global version, I found that...

I don't know that particular game, but I've played quite a few text adventure games, and even used a text adventure writing system called The Quill for ZX Spectrum and another called DAAD for PC. Most text adventures in that time were based on one- or two-word sentences: INVENTORY, TAKE GEM, OPEN CH...

Globals have two big pitfalls. First, they are prone to bugs. Consider this situation (very simplified, but hopefully you'll understand how it generalizes): function swap_a_and_b() tmp = a a = b b = tmp end a = 7 b = 8 tmp = 9 swap_a_and_b() print(tmp) You typically expect tmp to still be 9, but bei...

It appears that I'm smarter than ChatGPT. lol Surprised? You shouldn't ;) The formulas answered for one of the questions make no sense whatsoever (the ones "based on the ratio of the longer and shorter axes"). The answer you need is: local speed = 1 -- in pixels per second local dt = 1/60...

I'm not sure which method is best suited for a more complex game. Interested in hearing others' opinions on this. If you don't care missing presses or releases within a single frame, then you're good using isScancodeDown (generally speaking, always avoid isDown, for the benefit of non-QWERTY keyboa...

Maybe you wanted to use love.graphics.setBackgroundColor instead?

Just use left-alignment instead of justification. Even if it worked as you expect, it would have to justify the whole line every time one is completed, and if you're still reading that, it's uncomfortable. If you absolutely want to try it, you can try printing all lines except the last one justified...

I think you have made a mess of coordinate systems. According to the code, self.x and self.y are in screen coordinates, while it appears that Camera:setPosition(x, y) expects world coordinates. Your coordinate transformation formulas are messed up. My recommendation is that you use a camera library ...