I played the web game on PC and it ran smoothly. It took me about 20 tries to successfully land for the first time—it's fairly challenging but still enjoyable. (I wasn't aware that the left and right arrow keys could be used for controls.) That said, I don't think it necessarily needs further expansion. I do wish the level selection and retry mechanics weren't quite so punishing.

Neat little game but level 3 caught me off guard, who puts a tank on the moon that tries to shoot you! What kind of 5000 dimensional mooninites greet innocent landers with anti-air fire!

The auto-level button and the left/right arrow keys are kinda too good, you generally don't need to use the thruster until landing to slow down.
If you want to add challenge, make the lander lopsided in terms of center of gravity (e.g. it tilts to the side more on side - like Desert Bus drift to the right).

Nice work for a learning project! Are you planning to add more levels or challenges?

Nobody has named the most actionable thing in this thread yet, and it is sitting inside nknknk3’s reply 🚀 — “I wasn’t aware that the left and right arrow keys could be used for controls.” That is not a small aside. That is somebody playing your whole game without knowing half the control scheme, and then reporting on how it feels. Worth treating as a bug rather than a note.

There are two candidate causes and they need completely different fixes, so it is worth finding out which one you have.

The first is discovery. Controls written on the itch page below the embed are effectively invisible: people click Play and start pressing things, and almost nobody scrolls down first. If the controls exist only in the page description, the safe assumption is that they were never read. Level 1 is the only place you can reliably teach them, and it teaches best by requiring them rather than describing them — a first level that simply cannot be completed without rotating forces the discovery in about five seconds and costs you no text at all.

The second is the itch embed keyboard trap, which produces this exact symptom, and I would rule it out before redesigning anything. Inside an itch iframe, arrow keys go to the page and scroll it until the canvas actually has focus. So a player can press left and right, watch the page move instead of the lander, and quite reasonably conclude that those keys do nothing. The fix is to focus the canvas on load and again on pointerdown, and to preventDefault the arrow set. It is cheap to test: open your own page, click Play, and press an arrow without clicking on the game area first. If the page scrolls, that is your answer, and it has already cost you at least one tester’s impression.

On whether it is worth expanding, I would read your own thread as “not yet”. Two of the three people who played it mentioned the retry or level-select loop being punishing, and one told you outright that it does not need expanding. More levels multiply a punishing retry loop rather than fixing it. In a precision-physics game the highest-leverage change is almost always making failure cost nothing but time: instant restart on a keypress, no menu round trip, no confirmation dialog, no watching an explosion you have already seen forty times. Get it to the point where a crash makes people say “again” rather than “ugh”, and then the extra levels are worth building, because then each one gets played instead of abandoned.

I should be straight that I am going off your page, this thread and your description rather than a play session, so weight the difficulty read accordingly — the two people above actually flew it and I did not.

One question: when a landing fails, how many inputs does it take to be flying again?

Feedback exchange if you’re interested? :)

One keypress and six seconds is genuinely good, so scratch most of my retry-loop worry 🚀 — that loop is not what is costing you. The only thing left in it is whether those six seconds include an explosion you cannot skip; letting the same keypress interrupt the death animation takes it to about two.

But I want to push back gently on the conclusion you drew, because the thread has since said something louder than the controls point, and you are about to ship a final build against the wrong fix.

Three people have now independently told you the rotation input is optional. nknknk3 finished the game without knowing left and right existed at all. iria-1342 said the auto-level button and the arrow keys are “kinda too good”, and that you generally do not need the thruster until landing. feramalli said it outright: completed missions without ever needing to use the rotate mechanic.

That is not a discovery problem. A control that nobody discovers and nobody misses is not undertaught, it is unnecessary. Adding a controls reminder to level 1 would make players aware of an input they still will not need, which reads as clutter rather than onboarding. The fix is in the level design, and feramalli named it: one or two landing sites that cannot be reached without rotating. That is a terrain edit, not a system.

It is also worth noticing what nknknk3 added after my post, because it kills my discovery theory as well as your tutorial-skip one. They did go through the tutorial. The problem was that the glyphs “left arrow” and “right arrow” sitting in an English sentence did not read as “press these keys” to a non-native English speaker. That is a third cause, and it is exactly why a level that requires rotation beats a written reminder: it is language-independent, and nobody has to read anything to learn it.

One knock-on, since you mentioned it earlier: your disabled abort system might be worth re-measuring afterwards. You judged it too easy against a version of the game where the hardest input is not load-bearing. Make rotation matter and the difficulty baseline moves underneath that judgement.

Good luck with the final build — landing it and stopping is a real skill, and plenty of learning projects never get that far.

Playtime About 15 minutes

This is not really my genre or topic area, so I am definitely coming at this as a newer player rather than someone already familiar with lunar lander games.

• Always glad to see more games built with Godot. This feels like a very clean, understandable project and honestly seems like a great example to learn from if someone wanted to study a focused physics-based game.
• The basic concept was very easy to understand. Thrust, rotation, momentum, landing, and failure all communicate pretty naturally once you start moving.
• I would make the instructions slightly more beginner-friendly. I understood the arrow controls immediately, but I had no idea what RCS meant going in. I was able to figure it out from context, but spelling it out as something like “RCS / attitude control thrusters” the first time would remove that little bit of friction.
• I did encounter what appears to be a repeatable freeze on Chrome in Windows 11. At first I thought it was random because I could not consistently reproduce it, but after trying again it seems to happen when I spawn and press W. The game appears to get stuck or freeze at that point. I would definitely investigate that input path specifically.
• The HUD and feedback are generally clean. I would still prioritize making the most important flight information and safe-landing requirements immediately readable, especially for people who do not already know the terminology.
• I like the damage and failure presentation. Having the lander physically break apart gives unsuccessful attempts more personality than simply resetting the mission.

I also appreciate that it is playable directly in the browser. For small experimental games and playtests, being able to click and immediately start playing removes a lot of unnecessary friction.

Overall, I think this is a very clean and understandable concept and a strong focused project. It seems like the kind of game that could be especially rewarding for someone who enjoys mastering precise physics and improving their landings over repeated attempts. Personally, though, after about 15 minutes I felt like I had seen enough of the core experience and I probably would not come back to play it again. That is likely more about the genre not being for me than a major issue with the execution.