Reflecting on the past year of game development (and related stuff), I learned a few hard lessons. Here is a breakdown and some additional rambling, which is hopefully of some use to you.
An approximate plot of my games to date. I really got off track this year.
Lesson #1: Get good at failing.
Failing is super key. I know this, and I’m sure you do too. But I am still not very good at it sometimes. What is failing in the context of making games? To me, it’s learning when your game should no longer be pursued. A couple of times over the past year, I poured weeks into stuff that was not and would never be good. The “One Hundred Prisoners” project is a prime example. I had the idea of making this game. The idea was simply not a fun or worthwhile game idea. But, I didn’t realize (or want to admit it), so I kept pushing the project forward. After many weeks of making cooler looking textures and adding sounds and stuff, I finally gave up. Why? It wasn’t any good!
A crude illustration of my part of my game making process.
Lesson #2: Gameplay. Gaaaaameplay!
Games do not need to be fun*. But, they do need to be GOOD. The “One Hundred Prisoners” project was not meant to be fun. But, the end result would have been an experience that had someone basically walking up and down a hall a few hundred times. I could add some dialog and stuff, sure. But at the core of the experience, the only way the player could interact with the world was a light switch. That is not a compelling experience. The game play was not there, so the game should have been abandoned as soon as I realized that. But, as mentioned above, I decided I would work on graphics for a while, then come back to the game play. I skipped over the “Is it actually any good?” decision point, and went to the “Making it look and sound good” phase. Bad idea! But it was easier than making the decision to kill the concept and move on.
*Not looking to argue this point. There are plenty of arguments around this online already 🙂
Lesson #3: Making a framework for a game is easy. Making it a real game is hard.
A couple other projects I worked on this year (looking at you, 2D Golf) resulted in some pretty fun core game play. However, I got the games to a point where I needed to commit and make actual levels and art and stuff. But I didn’t want to. I liked the “Cool ideas!” phase of the project, but didn’t want to do the grunt work to build the rest of the game. So it got shelved. Will I come back to it? Maybe. Probably not.
I do find some joy in simply proving out a concept. Recently, I made a mario kart like thing in Unity in about an hour. However, this time I resisted falling into the “Oh, I’ll just go make mario kart now” trap. Nope. I proved the concept to myself, it was neat and fun, yay for me. Time to move on.
Lesson #4: Sometimes (Most times) fun is enough!
Games don’t need to be fun. But, a lot of games are fun! So, why not start there. Some of the mental traps I fell into in the last year were trying to stretch my game concept into being something more than it ever could be. I took a few garbage concepts, and polished them. Tried to add meaning or complexity when the core concept was no good. Guess what? They were still garbage. They just took a lot of my time.
Recently, Tom Francis started a youtube series about making a game with no experience (It’s really great, and you should watch it). I started watching the series, and in the first 8 hours of fiddling with a basic game, I got something REALLY fun completed. It’s not a game yet, it’s a little game zygote. But, it is good. I added some zazz (See “The art of screenshake“), and it feels like something that can be a fun experience.
Note, the graphics and sounds are garbage at this point (see above). But I am really refusing to let myself deviate from adding game play value and fun to the game. This is key to keeping me in the “good stuff” zone for the project (see games plot at top of post). If I add something, and it doesn’t feel good to the game, it gets dropped. I don’t care if it’s the coolest idea I’ve ever had. If it’s garbage, it doesn’t go in.
Lesson #5: Game Play Foot Notes
“A bystander asked an equestrian sculptor how he did it. The sculptor replied, ‘I just chip away everything that doesn’t look like a horse.'”
A teacher of mine once told a story to the class. He said his professor taught him to take non-core ideas out of his papers, and insert them as foot notes instead. That way, his ideas were still there, but didn’t interfere with the core concept of the paper. Before handing in his paper, his professor told him to delete all his footnotes.
I think this applies to game ideas. If you think an idea is cool, but it doesn’t make the current game better. Make a footnote (email it to yourself, write it on your whiteboard, or whatever). But don’t let it interfere with your game! If it’s such a good idea, you will come back to it when you make your next project. And if it’s not, you didn’t waste time exploring it and taking time away from your current game.
That’s it really. Nothing earth shattering, really. Just some stuff that I thought I knew to avoid that I did not avoid as well as I thought.