Game design is the most important part of every game, whether it’s a simple runner or a title of a “Dragon Age” scale. Every specialist in every industry needs professional tools to do his job right. There are special IDEs for developers, professional software (i.e. Adobe, Autodesk) for artists, but there are no specific tools for game design. So, videogame designers always had to use different workarounds to do their job. The main challenge is that assets, called 'game design' for any given project, are never kept in one document, because these are quite different.
For example, dialogues must have a diagram-like layout to keep them organized, a game library database requires more structured storage, character’s data additionally require images storage, level maps should also have some visuals, etc.. So what can we do?
How do we track possible variations and flows of non-linear dialogues throughout the entire game? Well, some specialists use thousands of stickers, others build Visio-like flow charts. Big companies build their custom-developed set of tools to handle specific project needs — something that indie studios usually can’t afford and actually don’t need.
In order to achieve consistency in design and create visually appealing games, the information that is generated by game designers should be:
Tools that are shown in this category don’t require a lot of coding knowledge. Most of them are made to provide the simplest developing experience to anyone. Still, there are pitfalls to consider. These tools aren’t so easy as they look at first sight. While they are suitable for small and common games, it’s quite difficult to create a unique project without any comprehension. Let’s see what our software options are.
When we started looking for suitable game design tools, Mind Maps were our first choice. And we quickly ditched the idea, because only after 3 hours into a project, mind map started to look like this:
Right now, our current project named Rise Of Colonies has a game database of 16 Megabytes in size, and it mostly consists of text data. That’s really a lot of text! I’m even afraid to think what a Mind Map of that size would look like. An additional issue is software. Desktop software choices are quite limited, so we found FreeMind to be the one with the most feasible export features. But the issue with that software is that for really big mind maps its UI starts glitching, so it is not suitable for professional use as you are battling with the software, not with the project. It could be used to track smaller mind maps (i.e. menu layout), though.
We see that game studios use different Wiki systems (i.e. Atlassian Confluence, MediaWiki, etc.) quite frequently. Generally, it’s a good choice to keep all the information structured and well-maintained. However, it can’t be reused in-game by Copy-Paste means.
Additionally, it is not suitable for character dialogues at all.
When we just started considering different dialogue handlers out there, we looked through available Unity plugins on the Asset Store and found no suitable assets that could meet our project’s needs.
Software like Twinery or yEd also didn’t work for us, because it is designed for a specific usage: Twinery is more for creating standalone interactive stories, it is not customizable with extra properties and entire game structure can’t be maintained in it. While yEd is more like a graph builder application, much like Microsoft Visio, it is also not really suited for all game design tasks.
Finally, we’ve discovered Articy Draft — a visual environment solution that we’d previously overlooked (mainly due to its aggressive advertising as the golden hammer (or silver bullet)). At least that was the initial impression we gained from its promo website. However, after taking a quick look at the software, we realized that this tool can be successfully used in our processes, though not exactly as advertised. Our next article will be dedicated solely to this tool and how we use it in our Rise of Colonies project level editing.
I guess we are pretty much done for today, however, there’s one more specific tool that I would like to mention - Microsoft Excel or its free counterparts like LibreOffice and others.
This tool has a lot of hidden power in it, specifically:
In our studio, we use this software for initial level design for many of our grid projects. A typical level looks like this and it is very well imported/exported using CSV files as an intermediate format:
The software solutions we described above can be easily used for many of your projects, but feel free to use other tools that make your creative process more slick and convenient - your creativity depends on it, so start applying your creativity selecting the right tools for the job. There’s also a bunch of custom tools (like, i.e. level editors) that you might need for your project, and we will cover those in one of our following articles!