Time to get down to the nitty-gritty practical stuff. The topic for Day 4 was, Tools and Processes.
We started by comparing two games, side by side – Gone Home and Everyone’s Gone to the Rapture. This was to compare the game’s engines Unity vs. Unreal 4. We saw that the Unity game – Gone Home, allowed for a lot more in-depth object interaction but required a constrained environment (a house). The Unreal 4 game was set in an open world with amazing graphics but didn’t allow for much object interaction at all. So, this means that the very game engine chosen will dictate much of a game’s design and therefore the method of telling the story.
Next we dove into the assets produced in a game and the tools used to create and manage text assets. The narrative designer’s bible is the story bible (that really is the correct terminology). This document is everything narrative including the story outline, characters profiles, plot points, story intensions, emotional hits, location descriptions, game synopsis, timeline of events, even down to marketing material. Anthony uses Scrivener to build this essential document which is produced in the pre-production phase.
The class went on to discuss the obvious importance of version control when numerous assets must be maintained, tracked and changed together. For example, a change to the story bible could require a change to the game design document, manuscript and the game strings already embedded in the game engine. While we are on the subject, the game design document is different to the story bible in that it is more about the implementation of the game. For example, the GDD describes how the game looks in scenes from a game play perspective.
We talked about tools to help “get our story into the game” with Twine being the top-tool, since we are already using it for our own game projects. Inform and Inkle were also called out as useful tools that can generate game strings from story or dialogue. In many cases, studios may just collect game strings in an Excel spreadsheet.
Anthony suggested that we would provide more value as narrative designers if we understood terminology, challenges and limitations of specific game engines. The best way to do this is to practice some level design using designers such as Shadowrun Returns, Minecraft or Super Mario maker! We were also encouraged to look at GameMaker Studio, RPG Maker, Adventure Game studios for making our own games.
The class closed with the inspirational (that’s right Anthony) story of how Anthony Sweet made his way as a narrative and game designer. It took planning and eight years of execution to achieve but in Perth’s tiny market, it is certainly something to be proud of. We need to make our own plans and identify what we can offer to studios, as well as what we can improve on. A narrative designer needs to do a lot more than just write the game story, they should also be able to contribute to or write:
- Marketing material
- Coms (Internal and External)
- Style Guides – e.g. “this is the way you talk about your game” The language used. Buzz words.
- Social Media
- Character social media
- Profiles and lore excerpts
So now I will go away and think about what I can do for a studio as well as watch the Double Fine Adventure documentary to get a better idea of what really goes on during game production.