A game maker for students with a deadline
If you have a project due and no intention of becoming a programmer first, the constraint is time, not talent. This removes the part of the work that eats the time.
The maths of a student project
A term project is maybe forty usable hours, spread thin, competing with everything else. If you are learning a language, wiring input handling and debugging why the collider is offset, thirty of those hours are gone before the game has an idea in it. The thing you hand in is a technical exercise with a title screen.
Take the code out and the arithmetic changes completely. You spend the forty hours on the world, the pacing and the feel, which is what the project was supposed to be about and what anyone marking it or looking at it later actually responds to.
That is the whole pitch. Not that it is easier. That the time goes to the part that shows.
How the work splits
You build the world by hand. Terrain, water, weather, buildings, characters, placed in a builder that behaves like a level editor. This is the part where your taste is the input and where describing something in a sentence would be slower than just doing it.
Director 1 writes the code. You describe behaviour and it writes GDScript into your project. You do not have to read it, though it is there and it is ordinary. What you do have to do is play the result and say what is wrong, over and over, which is the part that makes a game good.
The game runs locally on the copy of Godot bundled with the app, at your laptop's framerate. Building needs an internet connection; playing what you built does not. That matters on a library wifi day.
What you end up with
A real Godot project in a folder you own. Not an export from a closed tool, not a save file on someone's server. If your course requires you to submit source, you have source. If you want to keep working on it after the module ends, in Godot directly, nothing stops you.
That also matters for a portfolio. A project that opens is worth more than a video of a project. And because Godot is open source and widely used, the thing on your disk is legible to anyone who looks at it professionally.
Being honest about one thing: if the assessment is specifically on your programming, this is the wrong tool for that assessment. Use it for the design module, the game jam, the personal project, the thing you actually wanted to make.
Cost, because you are a student
The download is free and there is a free plan. Indie is $10 a month, Pro is $50, and both buy more usage rather than a better engine. There is no student discount and no education tier, so the free plan is the student plan unless you decide the usage is worth ten dollars in a heavy month.
Stage Engine is a desktop app for Mac and Windows. It installs on your own laptop, which is usually easier than getting anything installed on a lab machine.
Questions
- Is there a student discount?
- No. There is a free plan, Indie at $10 a month and Pro at $50. The free plan is a genuine plan rather than a trial.
- Can I submit the source code for my course?
- Yes. The project is a normal Godot project with ordinary GDScript in it, sitting in a folder on your machine.
- Is this cheating on a programming assignment?
- If the assignment is assessed on your code, then using a tool that writes the code is not appropriate. For a design project, a jam or your own work, it is exactly what it is for. Ask your tutor rather than us.
- Will it run on my laptop?
- It needs a Mac or a Windows machine you can install software on. It does not run in a browser, on a Chromebook or on a tablet.
- How fast can I get something playable?
- Usually inside the first session. Making it good is the rest of the term, same as anything.