Postpartum: Mainichi – How Personal Experience Became a Game
This will be a design article on my game Mainichi, aiming to be insight to my thought process during its creation and serve as a guide for others to make games. To get the most out of this, download Mainichi here and then come back to read this! If the download is giving you problems, use my contact info and I’ll send you a copy. For extra reading, I also suggest getting a copy of anna anthropy’s Rise of the Videogame Zinesters, as I’ll be speaking to many of the ideas she advocates in it.
There is a movement. A movement that says “You can too.” It is growing in size, accessibility, and voice. Game design is, and always has been, for everyone, but the narrow path the industry took blocked off many peoples’ opportunity to join in on this artistic revolution. It’s assumed you must have the best graphics, know how to code, have the money to develop a game that can speak to the world.
I only know life with computers and video games in them. My father is a programmer and shared a love for technology with his children. I grew up surrounded by games and, naturally, wanted to make them. But my father never passed down the skill to code, and I never realized how important programming fit into making a game until I tried making them years later. Coding became a monster; I couldn’t get it and felt my creative energy dissipate every time I tried to learn. I entered university believing game design wasn’t for me and gave up on that dream to join the industry.
But now, I’ve come full circle. The industry badly needs to diversify and there’s still roadblocks. Publisher model game development is choked by putting profit above all else, and the monochromatic landscape of non-AAA development still values methods that require monetary investment and a previous buy-in to programming culture that many of us just don’t have. Despite this, I still had something to say, or rather, something I didn’t know how to say. I had something I needed others to play.
This is how Mainichi was born. It was an experiment in translating a personal experience into game mechanics, and also a push to prove to myself that I can make a game, even if the video game industry wouldn’t accept me. I want Mainichi to be a call to arms, a triumph of the personal. I made a game that only I could make, and I’m hoping this exercise empowers others to express a life that is uniquely theirs.
The biggest roadblock I had to overcome was choosing the program I would use to make my game. I asked for suggestions, consulted lists, and tried out many to no avail. I ran into many bumps; usually, the more free and open source something is, the more programming is integral to the making process. Though, some did come with their own scripting language that was easier to learn and a viable method for those who aren’t completely code-phobic like I am. Many of the more popular game makers are primed for certain types of games, like shooters or platformers. Looking to make something akin to an adventure game, the obtuse methods to simple get someone walking across the screen on a level plane and generating a textbox from an NPC were quick to grate my nerves.
If there was something I learned, it’s the increasing amount of tools for people to use all assume different competencies, wants, and conventions. Authoring programs are prepared for certain users, and make it easy or difficult to do particular things. This isn’t simply a practical thing to know, but political. Many programs assume you have the privilege, tastes, and wants of the hegemonic man. However, some of these tools come with communities that make it easier to subvert this assumption, and is, in particular, something I encourage others to factor in when choosing a program for themselves. Here is what I came up with for myself and the needs I perceived I needed for my game ideas:
*Programming unnecessary or extremely minimal/optional
*No to low cost
*Made it simple or easy for me to use textboxes, characters, variables, cutscenes
*Has an active enough community to provide custom content
These and other factors contributed to me picking RPG Maker VX, despite its price tag. Mostly, my personal disposition and skills overcame the cost for it after not feeling compatible with all my other options- I was familiar with the toolset already, had the skills to edit its art assets enough for my own devices, and most of my ideas would benefit from the assumption of an RPG/adventure game being made. There were narrow expectations about the kind of game I wanted to make inside those conventions, but there was room to subvert these paradigms. As an aside, RPGMVX does have a cheaper sibling, RPGMXP, that I ended up not choosing because I had the familiarity with the former. However, for those new to both and interested in using them, XP is as viable, just for different reasons. I think others can find similar, free programs and still do what I did with Mainichi, RPGMVX just happened to be right for me.
It’s easy to have a story or an idea. What makes a game significant is its designed experience. Coming into this experiment, I knew that current attempts of doling out social awareness just through story devices plainly didn’t work. I had to choose methods of design to communicate the feelings of my experience to the player, because otherwise I could simply point them to an essay I’ve done. I would say Mainichi lets someone feel rather than tells them what to feel. It’s a key difference to create empathy instead of telling the player what’s right to think.
If this experiment is judged successful, I think it will be because of my philosophy of being hyper-personal, or like what my colleague Jenn Frank says is “alarmingly specific.” This applied not only to the topic but the design as well; I wanted to draw upon my ideas about sociology, postmodern art, ludonarrative resonance, and diversity politics in video games and have them influence the way the player interacted with the rules. I wanted this game to be dripping with the intersection of all of my influences, and create a new way of looking at design as a byproduct. I think for a personal piece like this to work, you have to speak to the world in general through a very specialized perspective.
How to design a game for social good is a fraught question. It’s difficult to position the player in a way that doesn’t have them exploit the minority and unknowingly replicate the problematic ideologies the game set out to defeat. This is why I stressed reactivity of the system and eliminated min/maxing of any sort. When you look at the system as a metaphor for society, the suffering that happens to the character doesn’t become something the player enables but joins ranks against.
There is something to be said about being too referential in a game, but I decided to be extremely so. I made the character after my likeness and named them after myself, I have a Japanese title, there’s a Dragon Age II cameo, etc. However, everything does have a personal link to add to the aesthetic and ‘meaning’ of the piece. Since the game is essentially interacting with a system, it could be replicated with numbers and without any sort of cultural representation. So it felt right to imbue as much of the game with my personal easter eggs because the game won’t make complete sense without the meta-awareness of how it fits in. And really, all games that try to mean something have to do that as well.
I also recognized there would be audiences for my game, but no ‘perfect player.’ There is no one person that can absorb everything this game is meant to do. I’m not even the perfect player for my game. Rather, I knew that it would be released to the world and many people of different relationships to games would play it, including those who don’t game at all. So my game doesn’t have a target audience like many other games, and I didn’t have a genre in mind when making the game. However, I was aware of the different expectations people would bring to my game.
A lot of this game is speaking to the game development community. It is a community that finds making a game about minority issues near-impossible, so I ended up making one in about a week. There are also different paths for it to be analyzed, genealogy-wise, and one could see Mainichi as an offspring of Dys4ia and Passage. From Dys4ia I am intentionally making my game political through the personal, merely repeating the idea in a different format to diversify how we see, define, and interface with games. Another game in this lineage would be Merritt Kopas’ LIM, which also relies on mechanics replicating emotional experiences. I also see Mainichi as a critique to Passage in this regard; just because this isn’t AAA development doesn’t mean the types of games coming out of the indie scene aren’t dominated by heterosexual white men’s narratives. I want the community to know that some people don’t have the luxury of mulling over something as long term and general as the passage of life towards death or saving the world. Some of us have to worry for our physical safety every day we leave the house, some of us will live and die unequal citizens in a system that doesn’t care; the street scene in Mainichi hopes to be referential to the design of Passage for the community of developers that care about that sort of design canon.
Because of the look and that it is in fact made with an RPG Maker, I knew some players would be bringing the baggage that comes along with RPGs. I also have quite a lot to say about RPGs, how I think they are evolving, and my answer to ‘what is an RPG.’ So I specifically highlighted certain conventions, like choice, time management, NPCs, cause/effect, multiple paths to the end goal. I then proceeded to flip the expectations players would have with elements; the choices you make aren’t epic or demarcated by a clear morality, the player is taught to avoid as much interaction as possible, and the player will be depressed looking for the ‘good’ ending. Mainly, I find RPGs abstract things so we can interact with them, an exercise in turning something qualitative into a system. The player gains empathy through my attempt of abstracting how people gender me, and allowed the player to experiment in the system to realize the experiences I’ve been through.
Outside of the highbrow stuff, I wanted to communicate an experience that I couldn’t do with words alone. Ultimately, this could be a project in telling my best friend why I was often depressed despite the good intentions of my support group. Similarly, I wanted players with cisgender privilege to also empathize with one aspect of having a queer gender or presentation. It can also serve as a tool for a trans* person to share with their friends if they have the same trouble explaining like I did.
A huge reason I made Mainichi was to say that, yes, anyone can make a game of critical merit. You don’t have to be a programmer, you don’t need a whole bunch of disposable income, be on a triple digit design team, or a part of the indie in-crowd. The important thing is to know game design is something everyone has the capacity to work on, and the implementation into a program is the hard part.
This is important to note because video games aren’t the only types of games there are: I am currently working on a card game that will allow players to simulate and interrogate the dynamics of a first date or sex. In addition, as The Border House has already shown, there are also non-traditional formats of digital games that beg to be used and experimented with, like Twine and Ren’py. What I think a lot of the non-AAA developers forgot was that one leaves the publisher model behind in order to do something different. I’ve seen many failed projects because so many want to make the next Final Fantasy with RPG Maker and don’t see the dissonance in politics concerning that. Instead, take part in diversifying not only the characters and stories we see in games, but how we fundamentally interact with them as a whole.
(Originally posted at The Border House)
