What happened when one game writer tried making a game in 30 days with Godot
The article follows a writer/narrative designer who tried to make a game in 30 days using Godot, starting from essentially zero engine experience. That makes it relevant beyond just Godot users: it’s a compact case study in how quickly a non-programmer can become productive, where the bottlenecks actually show up, and what gets lost when you’re learning the engine while also trying to ship something playable.
For developers, the interesting part is the practical overlap between design, writing, and implementation. A month is long enough to build something real, but short enough that every unfamiliar editor, node setup, and iteration loop has immediate cost. It’s a reminder that engine choice affects not just code, but the whole content pipeline and how much a solo or small-team dev can realistically absorb in a sprint.
“What’s it like for a narrative designer to learn a game engine from scratch?”
- what
- A game writer/narrative designer attempted to build a game in 30 days using Godot.
- who
- The article is by Game Developer and focuses on one game writer/narrative designer; Godot is the engine used.
- when
- The project was completed over a 30-day period.
- impact
- Useful for designers and narrative folks evaluating how steep the learning curve is when moving into hands-on implementation.
Encouraging experiment, but clearly hard and friction-heavy
Follow Godot updates
See relevant stories in your personalized news feed.
Discussion