Contumacious Commuter (Uys 2021) is built with Godot Engine (Engine n.d.). The game is a combination of many prototypes across the 7 disciplines of game development. This essay discusses three of the disciplines in depth, which are narrative design, game design, and art direction. These are also the disciplines I highlighted at the start of the module as being most excited about mastering (Uys 2021). I’ll also cover a bit of programming, as it’s my dominant skill, but there’s always room for improvement.
A lesson I learned during this process was that I, as a programmer, can’t rely on just my programming skills to make a game. A game designer needs as many skills as they can muster, as almost anything that you can be good at, can become a useful skill for a game designer (Schell 2019).
This is a tall order, especially for a small studio, or a single-person micro/nano studio like myself. As such, Renaud Forestié reminds us to minimise scope, as “it’s really about putting the minimum effort possible to do what works” (Unity 2018).
I set out to consider the development of this prototype the “pre-production” phase of Mark Cerny’s The Method (Academy of Interactive Arts & Sciences 2012), after which I would have a “publishable” first playable, and be ready to enter the production phase, which should only involve content creation for the game, and not be spent making any new game-changing decisions.
More importantly, prototyping is supposed to be a time-saving experiment in that each prototype should be designed to answer a question (Schell 2019: 109), which I certainly feel I’ve achieved. However, I did learn that I should have involved play-testers much earlier than I did, as valuable feedback from testers that fundamentally change some aspects of the game, came quite late in the process.
I start with narrative design, as it was the one discipline I initially discounted in a moment of weakness (Uys 2021), but I have a growth mindset (Stanford Alumni 2014), and did a Coursera course in narrative design (Coursera n.d.). This discipline became the one I (by far) had the most fun with, and wrote over 5,000 words for (Uys 2021) to come up with the game’s story structure and core emotional elements including theme, plot, character, and dialogue (Lionbridge 2020).
Not only does a story provide greater emotional satisfaction and sense of progress to the player in terms of dramatically meaningful (rather than abstract) goals (Adams 2014: 208), but it gave me — the designer — a deeper understanding and love of my game, and the worldbuilding provided plenty of lore and content to inform the other disciplines:
Along with creating settings and determining the world's scope, a narrative developer's worldbuilding influences art design and sound design by suggesting what the game should look and sound like.(Heussner 2015: 49)
Also, the level designer will mine your backstory to find narratively appropriate content to put in the game (Heussner 2015: 58,62), even if players will only see the tip of the narrative iceberg (Heussner 2015: 61).
The fact that the narrative design influences so many of the other disciplines, definitely puts it near the top of my todo list for future games, right after coming up with genre, core mechanics, and context (Skolnick 2014). I hope that it will edge me closer to success, as video game reviewers typically have low expectations for the narrative quality in games, and anything vaguely better than the norm would make them sit up and take notice (Skolnick 2014).
Worldbuilding needs research (Heussner 2015: 49), but since this is just magical realism and based on real, normal life I already know, I got away with skimping on in-depth research. I might benefit from this time-saving technique by making future games using what I already know, as a developer’s own experience, or that of their team, can be excellent sources of inspiration (Heussner 2015: 53).
Ernest Adams states “coherence” and “dramatic meaningfulness” as requirements of a good story, in that the events in the story must not be irrelevant or arbitrary, but must harmonise to create a pleasing whole (2014: 211). I therefore rewrote some of the narrative: in an earlier version, the protagonist encounters random enemies, but in the latest version the protagonist encounters friends of the antagonist that the protagonist learned about in a photograph. The photograph then also becomes a list of enemies you can expect to encounter, and cross off as you beat them.
Linear stories are simpler as it requires less content, and are less prone to bugs and absurdities like continuity errors (Adams 2014: 221), and I learnt that this works best for this game. I didn’t have to develop systems to support open worlds and branching narratives, and could focus on the card mechanic, and a suitably entertaining linear story to carry us forth.
In keeping with building a prototype and having a minimum viable product, I decided to tell as much of a story as the player needed in a couple of images, the first image already being on the game’s main menu. There were no written words for the player to read, and no recorded words for the player to listen to. This has knock-on savings in terms of internationalisation, voice acting, and so forth (Sylvester 2013: 330). Those 2 images told all the player needed to know, and saved me a bunch of time.
When I planned the game initially, I kept Schell’s “Plan To Cut Rule” in mind, which is to make sure that you build it in such a way that if 50% of the budget was removed, you could still have a shippable game (2019). Alongside that is the “50% Rule”: all gameplay elements should be fully playable at the half-way mark in your schedule, so you spend half the time getting the game working, and half the time making it great (2019).
Keeping to these rules were my saving grace in the end, as personal circumstances took a 6-8 week bite out of my schedule. As such, the prototype is as simple and bare as it can possibly be. I will definitely keep this in mind for future endeavours and be ruthless about getting the core of the game done in good time.
The “possibility space” (Indie Games Collective 2015: 603) in my prototype is only the playing cards. I’ve found that having a small surface area of interaction makes the design much simpler, and testing easier, and reduces risk (GDC 2017). For future games, I will focus on getting the one core interaction perfect before implementing subsequent possibility spaces. Besides, the world wouldn’t miss yet another another crafting system (Google n.d.).
Limiting the possibility space ties in with McEntee’s “Rational Design”, which is all about eliminating unnecessary information, making things inherently readable, understandable and apparent, introducing mechanics in an orderly and easily digestible fashion, and preserving the learning and difficulty curves of a game, known as macro flow (2012).
When traveling on public transport, one can encounter annoyances like elbow jabs, knee bumps, smelly food, and so forth. These annoyances are the “attacks” you can execute using the playing cards, to push the enemy’s annoyance level up in an effort to defeat them and transition to the next level. Games can actually play a powerful role in creating empathy and other strong, positive emotional experiences (Isbister 2017), so I hope this game will send a message about being a more conscientious fellow commuter.
A lesson that I learnt about myself and art direction, is to make decisions and stick with them, as one can carry on changing designs forevermore (Sylvester 2013: 363-9). (Even as I’m writing this, I’m thinking about changes I can make to the game’s art, but I won’t, as I’m too far along.)
When making games, I prefer abstract over realistic depictions of characters, as this leaves more to the player’s imagination, just like the nonsense babble in The Sims (Isbister 2017: 36). Scott McCloud agrees:
Thus, when you look at a photo or a realistic drawing of a face, you see it as the face of another.(2017: 36)
But, when you enter the world of the cartoon, you see yourself.
Fig. 1: McCloud 2017. Understanding Comics.
On directing art for something one wants to ultimately sell, raises the question: do I make what I want, or do I make what they want? The IGD720 module suggested we research the target market (“Week 5: Art Direction for Indie Games: Game Development IGD720 20/21 Part-Time Study Block S2” n.d.). Simon Carless also discusses this matter in his latest newsletter, where he studies an indie game which disregarded the market, contrary to the popular notion of “must make this game fit into the market, or else” (2021).
My view is that if you do research now, and release in 2 years, then you’re 2 years out-of-date, so you might as well make something artistically daring. This fits with the business model I currently have in mind for my venture, which is to self-fund and work on games 20-40% of the time: if the game fails, I’m not financially ruined, as I earned an income during the other 60-80%. I know this is a grossly simplified (and naïve) view, and we’ll learn more about the entrepreneurial side of this in a future module, so I’m on the fence.
One of the most valuable tools I picked up during this module is Lee Petty’s Four Fs (mediaXstanford 2017: 1587), which allowed me to make big-sweep and concise decisions about the game early on.
Stardew Valley took one person 4 years (Baker 2016) and Gorogoa took over 7 years (Kohler 2017), although the developer paid for some help at the end. Conversely, there are studios like Sokpop collective (Collective n.d.), who are a team of 4 who makes a new game every month, which is a tight cadence for any studio. These conflicting durations raises the question: how long should I spend on art? Stardew Valley’s success is a bit like winning the lottery, where-as the Sokpop guys have a more sustainable and regular monthly income (“Sokpop Collective: Patreon Earnings + Statistics + Graphs + Rank” n.d.). Since I’m more in favour of guaranteed income and not “betting the farm”, simple, low-effort art is the way to go for me.
A first iteration of the prototype employed SquiggleVision (Snyder and Lyman 2001) to make the line art seem alive, and I drew 4 or 5 variations of the same picture to achieve the effect. Having to extrapolate this across multiple characters would have been expensive and time-consuming, so I used a shader to wiggle the line art instead. Learning shaders is one of my SMART goals (Uys 2020), and definitely a core ingredient in my toolbox.
I thought that I reduced risk by implementing a 3rd party Godot card game framework (Zer0 2021), but it ended up taking me a while to wrap my head around the framework, which risked putting the project way past the deadline. On the other hand, once I had the framework in my head and started submitting suggestions and enhancements, I realised what a solid and flexible foundation I had to work on. There’s a whole community around the framework, so it’ll always be maintained. My future projects and endeavours will also stand on the shoulders of giants, and involve the community and special interest groups as much as possible, which will also alleviate the loneliness experienced by indie developers (SpaceCow 2020).
Some lessons that I learnt during the prototype development, is that every discipline is equally important: one weak pylon will make the entire structure come tumbling down (Adams 2014), and that game design cannot be learned from books, but with experience (Sylvester 2013: 47).
Prototyping is supposed to be a time-saving experiment in that each prototype should be designed to answer a question.(Schell 2019: 109)
Prototyping answered yes to the question of whether “active turn time” works well in a card game. Even with the basic set of cards that I made for the prototype, I found that I had to think much faster, which made for more exciting gameplay than having regular turn-based play.
Fig. 2: Uys 2021. Excerpt from poll
Prototyping also answered yes as to whether using shaders is a time-saving tool in some cases, like with SquiggleVision.
The 5th of Jesse Schell’s 10 tips for productive prototyping is to paralellise prototypes productively (2019: 110). I managed to parallelise a couple of my prototypes by coding during the times when I’m awake and fresh, and drawing the art while I’m hanging out with the kids and supposed to be away from screens, which is a great way to get more prototyping loops done.
Is the toy fun?
A ball is a toy, but baseball is a game. You should make sure that your toy is fun to play with before you design a game around it.(Schell 2019)
Shuffling the cards, dealing a hand, and moving the telegraphing arrow around the screen is already fun and looks good, so this is a promising base for the game to build on.
Could this be a “game for change” (“Home Page - Games For Change” n.d.), and teach players to be a more conscientious fellow commuter, by shedding light on the annoyances of public transport? Only time will tell.
Future work will include more levels, characters, cards, buffs and debuffs/nerfs (Game Maker’s Toolkit 2019), rewards, and achievements.
- ANDERSON, Linda (ed.). 2006. Creative Writing: a Workbook with Readings. New York: Routledge.
- ADAMS, Ernest. 2014. Fundamentals of Game Design. Third edition. Berkeley, CA: New Riders.
- BAKER, Chris. 2016. “The 4 Years of Self-Imposed Crunch That Went into Stardew Valley.” Available at: /view/news/267563/The_4_years_of_selfimposed_crunch_that_went_into_Stardew_Valley.php [accessed 17 May 2021].
- CARLESS, Simon. 2021. “Steam Sales for ’the Other 50%’ - a Return!” Available at: https://newsletter.gamediscover.co/ [accessed 18 May 2021].
- COLLECTIVE, Sokpop. n.d. “Sokpop Collective.” Available at: https://sokpop.co/ [accessed 18 May 2021].
- COURSERA. n.d. “Story and Narrative Development for Video Games.” Coursera. Available at: https://www.coursera.org/learn/video-game-story [accessed 18 May 2021].
- ENGINE, Godot. n.d. “Godot Engine - Free and Open Source 2D and 3D Game Engine.” Godot Engine. Available at: https://godotengine.org/ [accessed 17 May 2021].
- FORSTER, E. M. 1985. Aspects of the Novel. San Diego: Harcourt Brace Jovanovich.
- GOOGLE. n.d. “Gaming ‘Crafting Fatigue’ - Google Search.” Available at: https://www.google.com/search?q=gaming+%22crafting+fatigue%22 [accessed 18 May 2021].
- HEUSSNER, Tobias. 2015. The Game Narrative Toolbox. New York: Focal Press/Taylor & Francis Group.
- ISBISTER, Katherine. 2017. How Games Move Us: Emotion by Design. First MIT Press paperback edition. Cambridge, Massachusetts London, England: The MIT Press.
- KOHLER, Chris. 2017. “The Puzzle Of A Lifetime.” Kotaku. Available at: https://kotaku.com/the-puzzle-of-a-lifetime-1821235999 [accessed 17 May 2021].
- LIONBRIDGE. 2020. “Narrative Game Design for Every Audience.” lionbridge. Available at: https://www.lionbridge.com/blog/gaming/designing-winning-game-narrative-every-audience/ [accessed 28 Jan 2021].
- MCCLOUD, Scott. 2017. Understanding Comics. Reprint. New York: William Morrow, an imprint of Harper Collins Publishers.
- MCENTEE, Chris. 2012. “Rational Design: The Core of Rayman Origins.” Available at: https://gamasutra.com/view/feature/167214/rational_design_the_core_of_.php [accessed 18 May 2021].
- SCHELL, Jesse. 2019. The Art of Game Design: a Book of Lenses. Third edition. Boca Raton: Taylor & Francis, a CRC title, part of the Taylor & Francis imprint, a member of the Taylor & Francis Group, the academic division of T&F Informa, plc.
- SKOLNICK, Evan. 2014. Video Game Storytelling: What Every Developer Needs to Know about Narrative Techniques. Berkeley: Watson-Guptill.
- SNYDER, Thomas F. F. and Andre LYMAN. 2001. “United States Patent: 6252604 - Method of Animating an Image by Squiggling the Edges of Image Features.” Available at: https://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.htm&r=1&f=G&l=50&s1=6252604.PN.&OS=PN/6252604&RS=PN/6252604 [accessed 18 May 2021].
- SYLVESTER, Tynan. 2013. Designing Games: a Guide to Engineering Experiences. First edition. Sebastopol, CA: O’Reilly.
- UYS, Juan. 2021. “Contumacious Commuter by Juan Uys.” itch.io. Available at: https://opyate.itch.io/contumacious-commuter [accessed 17 May 2021].
- UYS, Juan. 2021. “IGD 720: Week 1 — Reflecting on the Skills Audit.” Available at: https://juanuys.com/ [accessed 17 May 2021].
- UYS, Juan. 2021. “Juanuys/Ccgdd.” GitHub. Available at: https://github.com/juanuys/ccgdd [accessed 18 May 2021].
- UYS, Juan. 2020. “Juan Uys’s SMART Goals.” Available at: https://juanuys.com/ [accessed 18 May 2021].
- ZER0, Divided by. 2021. “db0/Godot-Card-Game-Framework.” Available at: https://github.com/db0/godot-card-game-framework [accessed 17 May 2021].
- ACADEMY OF INTERACTIVE ARTS & SCIENCES. 2012. “D.I.C.E. Summit 2002 - Mark Cerny.” Available at: https://www.youtube.com/watch?v=QOAW9ioWAvE [accessed 6 Feb 2021].
- GDC. 2017. “How to Make and Self-Publish a Game in 12 Months.” Available at: https://www.youtube.com/watch?v=4tbPbMRcMFQ&t=337s [accessed 18 May 2021].
- GAME MAKER’S TOOLKIT. 2019. “How Games Get Balanced.” Available at: https://www.youtube.com/watch?v=WXQzdXPTb2A [accessed 18 May 2021].
- INDIE GAMES COLLECTIVE. 2015. “The Triforce of Game Design - Iain Lobb.” Available at: https://www.youtube.com/watch?v=Gn6QWyRnNNA&t=603s [accessed 18 May 2021].
- SPACECOW. 2020. “How I Finished My Indie Game (Even When I Hated It).” Available at: https://www.youtube.com/watch?v=zoG-uwWaJJM [accessed 18 May 2021].
- STANFORD ALUMNI. 2014. “Developing a Growth Mindset with Carol Dweck.” Available at: https://www.youtube.com/watch?v=hiiEeMN7vbQ [accessed 29 Jan 2021].
- UNITY. 2018. “Best Practices for Fast Game Design in Unity - Unite LA.” Available at: https://www.youtube.com/watch?v=NU29QKag8a0 [accessed 6 Feb 2021].
- MEDIAXSTANFORD. 2017. “Elements of Art Direction.” Available at: https://www.youtube.com/watch?v=NwXThTYbZY4&feature=youtu.be [accessed 25 Feb 2021].
List of figures
- Figure 1: MCCLOUD, Scott. 2017. Understanding Comics. Reprint. New York: William Morrow, an imprint of Harper Collins Publishers, p. 36.
- Figure 2: Uys 2021. Excerpt from poll during development of game prototype.