The Game Design Tools I Actually Use (And Some I Wish I Knew Earlier)
Every game designer has a moment where they realize their workflow is held together with sticky notes, a 400-row spreadsheet, and pure delusion. I’ve been there. So here’s the list I wish someone handed me earlier, tools that actually help you design better games, not just document them.
A quick note on how I ordered this: roughly from “pick it up in an afternoon” to “okay, you’ll need a weekend.” Because the right tool depends on where you are, what you’re building, and whether you want to ship something or just endlessly prototype.
Twine — https://twinery.org/
If you’ve never shipped a game and want to start, Twine is the answer. It’s free, browser-based, and lets you build branching narrative games without writing a single line of code. The output is plain HTML so sharing your game for playtesting feedback is as easy as sending a link.
It sounds retro but the skill you’re actually building is nonlinear storytelling, which is one of the hardest things to get right in any genre.
Miro — http://miro.com/
The online whiteboard that quietly became essential for game design. Use it for systems maps, player journey flows, quest diagrams, anything that lives better as a visual than a doc. The real value is that it’s collaborative and real-time, so your whole team is looking at the same thing.
A Miro board full of sticky notes is not a game design. It’s a mood board. Keep that distinction clear.
Notion — https://www.notion.so/
Underrated as a GDD tool. Notion lets you structure your design documentation in a way that’s actually readable and linkable, versus a Google Doc that turns into a 60-page scroll of outdated information.
Where it falls short: anything involving numbers, probabilities, or simulating outcomes. A table in Notion is just a table. It won’t tell you what your economy actually does.
Itembase Simulator — https://itembase.dev/sim
This one doesn’t get talked about enough. The simulator at itembase.dev lets you model game mechanics as a node graph and run simulations to see how they actually behave. Not how you think they’ll behave. How they actually play out across thousands of iterations.
Spreadsheets lie to you. You put a 30% drop rate in a cell, it stays 30% forever. But players don’t experience percentages, they experience streaks, dry spells, and lucky runs. A simulator shows you that. It also shows you where your reward loops break down before a developer writes a single line of code.
Free to use, no login required to poke around.
Articy Draft — https://www.articy.com/en/
If you’re building an RPG or any game with serious narrative branching, Articy Draft is built for it. It handles dialogue trees, character databases, story flow, and design documents all in one place. Variants and conditions stay manageable instead of spiraling into chaos.
There’s a learning curve but it pays off fast once your narrative gets complex.
itembase.dev — https://itembase.dev/
If you’re past the napkin sketch stage and actually designing a game economy, itembase.dev is worth bookmarking. It’s a visual platform that lets you manage your entire economy in one place: currencies, items, progression formulas, bundles, rarities, all connected and queryable. Want to know exactly how many coins a player earns per day at level 78? You can pull that without digging through five spreadsheets.
It also has a LiveOps timeline planner, import/export scripts, and a node-based plugin editor if you want to get fancy. The free beta is live right now so the barrier to try it is zero.
GameMaker — https://gamemaker.io/
When you want more control and you’re ready to write some code, GameMaker is the move. Its scripting language is approachable, the community is huge, and the number of commercial hits built on it should tell you it’s not a toy. Holocure, Undertale, Hotline Miami.
Check the current pricing model since it’s shifted around, but there’s a free tier to get started
Bottom Line
Most of these tools solve one specific part of the design problem: narrative flow, visual collaboration, documentation, or prototyping. The gap nobody talks about enough is simulation, which is understanding how your systems behave probabilistically before you commit to building them.
That’s the gap I tried to fill with the simulator at itembase.dev. If you’re spending hours tweaking numbers in a spreadsheet trying to guess how your economy will play out, go try it. It’s the thing I kept wishing existed before I built it.
