(you can find the original article here)
You've done it. You made the jump. You've gone from "just working on a project," to identifying yourself as a real-life game designer. You've got a solid game design document, a (mostly) working prototype, and have even started to deal with the incredulous looks of bewilderment and disbelief when you tell people you're "making a game".
As you consider your wild fantasy of a design, the gravity of what you've signed yourself up for BEGINS TO DAWN ON YOU:
"What have am I doing?" "Is this even possible?" "Am I crazy?"
These are among the frantic questions that race around your mind. Every time you find yourself thinking about letting your hopes of making your game die, you remember: You are a game designer, and this game deserves to exist.
I put together this list to share how I've coped with the affliction of being a game designer. As Renaissance Man Kanye West put it, "this shit was hard to do, man!". Everyone has a unique environment, circumstance, and perspective when it comes to creating art--video games are no different.
Even though these suggestions won't work for everyone, I've tried to think of things that can apply to every indie designer, regardless of who they are and what game they are designing. You should also know that I've broken every one of these rules at some point during development myself. So, don't beat yourself up -- with these suggestions, starting late is much better than never!
1) Keep going
It seems insurmountable.
First, there's thinking of a way to craft your game that doesn't feel the same as everything else in the genre. That's before coding billions of mirco-conductors to manifest the wild fantasy of you've envisioned.
After that, you have to make sure it's good--even something as simple as moving a character around a 2D plane may need dozens of iterations to be balanced properly. As a designer, you don't ship with your game. Early in the process, you have to consider if the player can actually figure out what they're doing without you hawking over their shoulder. This issue is addressed through the use of designer-player communication tools like the GUI, prompts, and message windows.
The fact is, as an indie designer there will always be a million things to do. A lot of times at least half of them are going to seem impossible. A great game design professor once told my class that the "design never ends," despite the fact that the game has to ship at some point. What defines an indie game designer is the willingness to face these odds through failure, disappointment, and ridicule.
Just remember: keep going! In my experience, indie development works great in combination with "tunnel vision," or the ability to ignore and look past distractions and other exterior actors and concentrate on the goal or task at hand. Remember why you chose to do what you do in the first place. Remember how you've already come as far as you have, and consider why the world needs your game.
2) Make lists
During my university career, I was once told that "humans are monkey-minded". The notion has stuck with me. I remember the lecturer explaining how our mind naturally skips from thoughts, to memories, images, and everything in-between. A primary role of our self-conscious is in mediating and ordering this "monkey-mind" so that we can do things like have conversations and file our taxes.
Not to too get super Dalai-Lama here, but both creativity and the path to a state of peace and contentment are empowered by giving freedom to the monkey-mind. Of course, there are times where the monkey really should be paying attention, but even if you have to wrangle it in, it's only kind to be gentle, right?
To get to the point--lists are a great way of allowing yourself to be creative. And remember, the lists don't have to be exhaustive--you can always make another one! Make a list for your tasks for the next month, the next day, the next build, or the current character you're making.
As I stated before, there's a lot going on when you are developing games--especially on a small team or by yourself. It creates a lot of baggage -- you can be constantly trying to recall details of bugs you need to fix, or details of an art asset that needs to be changed. Committing the things you need to do to paper allows you to release those thoughts so that they don't have to take up space in your mind. That way you've got much more room for your monkey to wander and gather the fruits of creativity!
Also, give yourself the satisfaction of checking, crossing off, making a blood oath, or whatever it is you want to do to the list to communicate to yourself that a task is done. No matter how big or small of a task, use it as an opportunity to celebrate. It was on list, and now it's done. You fucking did it! You are a little bit closer to bringing your game into reality.
(Please don't actually do a blood oath, it's unsanitary.)
Remember the "fun meter" from the Sims? It's a real thing! Respect your fun meter.
Sometimes that might mean giving yourself a night off to decompress after banging your head against a wall for hours trying to fix that collision bug--maybe by switching to something like writing blog posts or by watching "Indie Game: The Movie" or an episode of Double-Fine Adventure. Do what you can to get yourself back into the zone. If you can work in a positive state of mind, both your work and efficiency will benefit as a result!
Good games take sacrifices of relationships, money, and perhaps most importantly--your time! So make sure you are managing your energy and putting some time into maintaining your physical and mental well-being. After all, if you're unwell it's harder to make a game!
4) Use Naming Conventions
Anyone who’s been hundreds of files deep into development and managed to lose that crucial asset that they've worked on for hours will stress how important this point is.
Proper use of naming conventions will save you a world of time and frustration. Your method doesn’t have to be too elaborate as far as “professional” conventions" go, but your main considerations should be consistency, clarity, and convenience. Whatever system you decide to use, make sure it’s logical and predictive for you. If someone else were to make an asset for your game using your naming conventions, you should be able to tell what kind of asset it is in your game, and where it belongs.
It can be very simple, but must be enough to make your assets distinguishable. It’s also important to carry this relationship with naming conventions across your whole project! For me, this includes art assets, scripts, and even the images I use for blogging. They might change from subject to subject, but the main thing is to make sure you know, and understand it, while finding your system efficient.
5) Talk to people
Developing Class Rules has been one of the most isolating experiences of my life. Making a game is itself a profession that is already at odds with society's "norms" and expectations of what constitutes wage labour and otherwise normative ways of life. Further, the actual day-to-day process of developing games is alien to the vast majority of people. Attempting to explain the minutia of "the awesome new script" you're working on, current hiccups in the coding process, or the labours of trying to balance a level often results in a glazed expression of confusion and apathy.
But, it's not their fault! What did you expect? You're a game developer! How long have you listened to the minor details of what other people do during their day at work? And really, why should you care so much? There is no way to know everything, and most people will not have the tools or to communicate with you about the in-depth details of your work.
The point I'm trying to make is: don't let game development's complexity discourage you from trying to talk to people about your game. Yes, a lot times you'll get friends and loved ones putting you down, disbelief in game mechanics you think are awesome, Han Solo shaking his head, and blunt disinterest in what you dedicate much of your time to. But at the same time, you can be faced with the exact opposite: great new ideas spawned from situations and conversations , songs to listen to, movies to watch, renewed fervour and faith in your project, or in short -- creativity.
Take criticism as an opportunity to review your reasons for doing what you do the way do. Take yourself through the uncomfortable process of challenging your assumptions. Make the reasons why your target market deserves your game evident within your work.
6) Set Deadlines
Setting deadlines is huge! It's a little related to making lists, but I think it deserves some more attention. When working by/for yourself it becomes very easy to let things slide. Pressure -- even if it's completely of your own fabrication -- is a great motivator. But, be realistic when setting deadlines for your schedule. This is especially true for the pre-design and prototyping phases of the project. In my experience, development times start to become a little more predictable as you become more attuned to the specific systems of producing parts of your game.
Deadlines can be set for a lot of reasons -- contest or festival entries, grant submissions, presentations, and your aunt's wedding are all valid reasons to make a stable build for your game. This is also something you can at the end of every week or two weeks to make sure you have a current and accessible version of the game ready to go just in case.
7) Show your game
Take the opportunities that you can to show your game to your peers and public. I think the most important thing going into any environment where you will have the chance to playtest and learn about your game is to know what it is you hope to answer during the playtest. Watch how your new section plays, or how players react to the dialogue. Try to have an idea of what you want to learn and take away from the play test! That way you can optimize the structure the session to get the most out of the feedback.
Also, be mindful about where you enter your game and make sure you're ready!
8) Make it count
Game design is an art. Your work has meaning. The power that the messages behind your game can mean for other people should not be underestimated. You have the opportunity to do something that matters for others, so do it!
I touched on the importance of making the effort to consider why your game deserves to exist earlier in this piece. Ask yourself why your game deserves to be made. Perhaps more importantly, why does it matter? As a designer, I think you should be repeatedly asking yourself these questions throughout the entire development process.
In 1809 when Napoleon led his armies to victory over the Prussians in Jena, German philosopher Georg Wilhelm Frederick Hegel claimed it was the "end of history". It ensured that the ideal "liberté, égalité, fraternité" would be pursued by all peoples of the world. The marriage between Napoleon's actions, and Hegel's thoughts are an example of a powerful dialectic representing the real political action that comes as part of some great artistic or literary works.
Videogames, as with all other forms of art, can be used as an agent of political change. If your game contributes to a message, or was designed to communicate something about a particular topic, you will have a much easier time motivating yourself to see your project through. And as indie, aren't you here to make unique games that wouldn't be considered by AAA studios anyways?