Jump to content
  • Advertisement
  • 05/18/13 12:19 AM

    Making it in Indie Games: Starter Guide

    Career Development


    Every now and then someone will ask me for advice on making it as a professional indie game developer. First, it's a huge honor to be asked that. So I want to say "Thank you!" Second... damn, if I really want to help out it's a serious endeavor. Of course, I could always say "Give it your best! Work hard! Be true to yourself!" and it wouldn't be a terrible reply... just not a terribly useful one, either.

    So here it is. Here is what I'm going to link when that rare situation arises again, because it's too much work to write it up more than once! This is advice that I feel may actually be practical to someone who is just starting out as an indie game developer. Hope it helps!


    So yeah, what does being "indie" even mean? Is "indie" short for independent? Is this game "indie"? Is "indie" a genre? IT'S CONFUSING - WHY DO WE NEED THE WORD "INDIE" AT ALL.

    To answer the last question, I offer the following scenarios. Scenario 1: a person is looking to make games, and perhaps start their own studio. They type "game development" into a search engine. The results, to say the least, are underwhelming. Dry. Academic. Programming-centric. (Try it yourself and see.)

    Scenario 2: the person instead types "indie games" into a search engine. Instead of pages upon pages of conferences, bachelor's degrees, and programming tools, that person is met instead with pages upon pages of games to play and vibrant communities filled with people who are doing exactly what he or she wants to be doing. Some of them went to school, but many did not. A wealth of different ideas and tools are used. There are even documentaries about making games! It's not just something where you get a degree and wait in line for a job. You can start making games RIGHT NOW.

    The word "indie" is more than just a way to describe a type of developmental process... like any label, it actually provides an avenue for people to explore that process and then flourish within it. It has a real purpose. It serves real lessons on game creation and entrepreneurialism. It offers real motivation!

    Of course, it can be irritating to see the term misused, or become a vehicle for pretentiousness and arrogance. Like any label, "indie" also breeds a certain amount dogmatism, croneyism, and other -isms. But the net result is really worth something. As someone who once gave up on professional game-making because I thought it meant a 9-to-5, I can tell you that it's genuinely valuable.

    As for what games are "truly" indie, we'll never fully agree, and that's probably for the best. But I can tell you the criteria I've devised for The Independent Gaming Source to determine whether a game is fit for coverage:

    1. "Independent", as in no publisher.

    2. Small studio (roughly 20 members or less).

    I choose that definition because it's the most useful one. Someone who is looking to become an "indie" game developer is interested in what is possible under those constraints and how those types of studios operate. It excludes companies like Valve and Double Fine, which are certainly independent but too large to be "indie". It also excludes "feels indie"-type games that are not self-published.

    Under that definition you still run into gray areas, but hey, just because we don't know when "red" turns into "purple" doesn't mean the words aren't useful. Just think about someone who wants to make a game with a small team and self-publish it... what should they type into Google for inspiration, advice, community, etc.? "Indie" is still as good a word as any, in my opinion.

    So, should I go to school to learn how to make games?

    The most important thing to know about video game development and schooling is that no one, whether it's an indie studio or big company, cares about degrees. How could it, when some of its most prominent members are drop-outs or never-beens? John Carmack, Cliff Bleszinski, Jonathan Blow, and Team Meat are all prominent members of this club.

    A degree is a piece of paper that says you can do something in theory - game developers want to know that you have enough passion to do real work, regardless of whether you're being graded on it. And if you're thinking of going indie, it won't matter what other people think - you'll simply need that passion to succeed or else you won't. You're the only one holding the door open in that case.

    This isn't to dissuade you from going to college, per se (I studied computer science in college, and while it was far from a perfect experience, I also gained a lot from both the curriculum and the friends I made there). The point is make something - games, mods, art, and music. If school helps you with that, great. If it doesn't, then you need to rethink how you're spending your most valuable resources: time and money (both of which can be exorbitant costs for schooling).

    If I go to school, what should I study?

    At a regular university, I would suggest majoring in computer science, even if you "just want to be a designer". The design of games is very much tied to how they are made.

    At an art school, illustration, concept art, and 3d modeling courses are probably the most useful for games.

    At a game school, they will hopefully try to involve you in all aspects of game creation, from programming to design. I would stay far away from design-only schools or curricula - those are either scams or are better suited to academia than actual game-making. Also, it's worth finding out whether or not the school owns what you make while you're a student there.

    See also: Jonathan Blow - How to Program Independent Games (read the comments as well as watch the video)

    Okay, you say make something. How do I start?

    My best advice for those starting out is not to get ahead of themselves. It's easy to start worrying about tools, teams, platforms, deals, marketing, awards, and whatever else before you've even gotten a sprite moving around the screen. Those stars in your eyes will blind you. They'll freeze you up. You need to be actively making games all the time.

    If we were talking about painting, I'd tell you to pick up a painting kit and a sketchpad at your local art store ASAP and just have at it. You'd proceed to put absolute crap down on the pad and get frustrated. But it'd also be kind of fun - so you'd keep doing it. Along the way you'd read some theory and study other people's work. With good taste and under a critical eye, you would keep doing that until the day you painted something good.

    We're talking about games, though. I recommend Game Maker and Unity as two all-purpose game-making suites. They both have a good balance of power versus ease-of-use; they're both affordable or have free demos, and they both have a wealth of tutorials and plug-ins online. Both are used by professional developers (Unity in particular). Grab one of those and start running through the tutorials. When you run into trouble, ask for help. Give help back when you begin figuring things out. Get active in a game-making community.

    But above all else, keep making games. It's the only way to truly answer all of those questions in your head right now.

    Also, watch this:



    1. Finish your games.

    2. Don't skimp on artwork. It's easy to underestimate the importance of artwork to a game. And even if you don't, it's easy to underestimate the importance of having a unique style of artwork. The result is that there are many ugly or generic-looking (i.e. "clip-arty") games failing to capture people's attention.

    If you have no artistic talent, go for style and coherency as many successful indie developers do. And even ugly is probably better than generic, all told. Remember: this is most people's first impression of your game.

    3. Don't blame marketing (too much). In the indie community it's become popular to write "how I failed" articles where the screenshots and comments tell the story of an ugly, boring game and yet the article itself tells the story of bad marketing decisions. Let's face it, no one wants to admit that they lacked any amount of creativity, vision, or talent. It's much easier to put the blame on release dates, trailers, websites, and whatever else.

    This is the internet, though. A good game will make its way out there. Marketing will certainly help, and hype may get you quite far in the short term, but it's not going to make or break you - it's only a multiplier of however good your game is. Saying otherwise is only hurting your ability to self-criticize and therefore improve your craft. It's also encouraging others to do the same.

    4. Indie is not a genre or aesthetic. Make the game you want to make, not what you think an indie game "should be". Recently, the very small and very independent team behind The Legend of Grimrock announced that their very traditional first-person dungeon crawler sold over 600,000 copies. Don't feel pressured to be dishonest about what you'd like to do - after all, what is independence if not freedom from such pressures?

    5. Build yourself a working environment that's healthy for you. Are you introverted and lose energy around other people or are you extroverted and gain energy that way? Or something in-between? What do you want your average working day to be like?

    You'll want to focus all of the energy available to you toward creating, and it's amazing how much of it can be lost to seemingly mundane things. Figuring out your physical working space as well as your personal support system is a key part of the solution to this problem, and its vitally important to you as an independent creator.

    6. Stay independent! To be sure, going indie can be daunting. There is always going to be the temptation of selling yourself or your ideas to someone else for a bit of a feeling of security. But honestly, once you go down that road it's hard to come back - every moment you're simply securing may not be a moment you're progressing. I'm not recommending recklessness, but it's important to stay committed and focused on the task at hand. Life is short.

    Also, don't give up your IP or in any way limit your opportunities long term. Keep exclusivity timed. When Aquaria released we weren't aware of Steam. The Humble Bundle did not yet exist. iPad did not exist. Being on all of those platforms has been great for us. You need to keep your hands untied to take advantage of what future will bring.

    7. Create your own luck. As an artist, I owe a lot to the people around me - my family, friends, peers, and idols. I accept that a lot of my success was simply the luck of being born with these people in my life.

    But it's important to realize that you create many of your own opportunities, too. For example, I met Alec (my friend and Aquaria co-creator) because he offered to help work on I'm O.K. I'm O.K. was a game started on the Pix Fu forums. The Pix Fu forums were part of my personal website and its members were friends of mine I'd made much earlier during my Blackeye Software/Klik n' Play days.

    You could trace a similar path from the XBLA version of Spelunky to the original PC version and the TIGSource forums.

    The point is - put yourself out there. Make things (I can't stress that enough!). You never know when serendipity will strike, but when it does it will likely be related to situations in your past when you chose to actively engage someone or some idea.

    8. Avoid "business as war". As a professional you'll need to do business and make business-related decisions at least occasionally, and as a creative type you might not be that interested in that stuff. Hell, you might even be downright scared of it.

    Well, I'm here to tell you that you don't have to be Gordon Gekko to make it as an indie. And please, don't try to be. In fact, avoid the Gordon Gekkos. Avoid the people who try to confuse you. Avoid the ones who try and nitpick. Avoid the ones who try and rush you.

    If you have a great game, there is no distributor you will absolutely have to work with, platform you have to be on, or person you will have to team up with. Always be willing to walk away from a bad deal, especially if it's to maintain your independence as a creator. In turn, be a direct and generous person yourself.

    People get defensive when they're scared. Don't sit at the table with someone like that or as someone like that and doing business should be fairly pleasant! This isn't Wall Street!

    9. No gimmicks. Simply put, focus on making a good game - a deep, interesting, unique game - rather than devising cheap tricks to grab people's attention. Whether we're talking about clever-sounding-but-ultimately-shallow game systems or off-the-wall marketing ideas, a gimmick is a gimmick. And you should stay away from them because they're short-term, high-risk solutions that ultimately cheapen you as an artist, perhaps literally as well as metaphorically.

    Certainly, one should take risks in game design as well as in life. My point is that they should be honest, worthwhile ones - those tend to be less risky in the long run.

    10. You are your game - understand and develop yourself. As an indie game developer your game will likely be more "you" than a game made by hundreds or thousands of people. You have to understand yourself quite well in order to make a truly successful game. Fortunately, the unraveling of what makes you "you" - your taste, what you care about, your abilities - is one of the great pleasures in life and goes hand in hand with your goal of being an independent creator. Treasure it!

    Reprinted with permission from Derek's blog

      Report Article

    User Feedback

    Create an account or sign in to leave a review

    You need to be a member in order to leave a review

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

    There are no reviews to display.

  • Advertisement
  • Game Developer Survey


    We are looking for qualified game developers to participate in a 10-minute online survey. Qualified participants will be offered a $15 incentive for your time and insights. Click here to start!

    Take me to the survey!

  • Advertisement
  • Latest Featured Articles

  • Featured Blogs

  • Advertisement
  • Popular Now

  • Similar Content

    • By Ryan Sutherland
      I've been studying game development for a little over 2 years now, primarily in Unreal Engine. While I've learned quite a bit regarding the "hard" skills of game development (programming, art, animation, etc.), I've really struggled in finding resources that teach the more abstracts of game design. I was wondering if anyone had any suggestions for resources for such things as level design, enemy design, encounter design, etc? There are some great YouTube channels that I've subscribed to, but I feel that most of them are more geared toward deconstructing existing properties and less on the strategies used to create these experiences in the first place.
      I realize that by its very nature game design is a very subjective subject, but I feel that there's still got to be some sort of "rules of thumb" available. I have a very technical mind, so I struggle with these topics and would really like a baseline for basic exercises that a beginner should start with.
      Thanks in advance!
    • By ToeBeans The Brave
      Okay, this would be for a PC game. It would be a pixel 2D fighting game with heavy story elements.
      General Story:
      A girl is sent to a mysterious medical facility that houses different kinds of "summoners", or people who accidentally end up summoning manifestations of their emotions. It is more of an experimental kind of set up rather than the helpful facade that the caretakers like to put up, and there are a lot of odd rules in place that keep the residents from wandering the hallways or contacting anyone outside of the walls.
      The girl suffers from OCD, and it gives her a lot of anxiety that ends up turning into small, dark creatures that she has to fight off on occasion. Throughout her stay at the facility, she meets and becomes friends with various caretakers, such as the doctors and nurses, and other patients who have their own monsters to deal with.
      Everything is calm, and peaceful. That is, until people at the facility start disappearing. It started with one staff member. Then another. Now even the patients are starting to go missing. The facility tries to play it off as if everything is normal, but even they can't cover up the strange noises at night, and the rumors of something terrible going on within the walls of what was thought to be a safe place.\As tension and anxiety rises, all of the monsters become stronger and more aggressive.
      And so the girl, along with her new friends, decide to investigate what exactly is going on by sneaking around the facility and collecting clues, all the while fighting against their inner demons.
      I am not experienced with making stories, so please judge the crap out of this so I know what to improve on. If I made something too ambiguous, I'd be happy to clarify what I mean, or give a more detailed description.
    • By Brad B
      I have always loved video games and in the last few years I've been trying to learn how to make them. While I'm learning and practicing and growing in many areas, my real strength has always been in story telling. I've been imaging stories, worlds and characters all my life. So far, the only way I've shared them is word of mouth. Explaining them to friends about them when hanging out. Telling them to girlfriends when cuddling for a sort of "story time". I've gotten a reputation for being rather good at "Story Telling". Problem is, I'm not good at writing.
      I've often thought that I could really make something great within the medium of video games though. So, in the business world of game design, is there a place for Story Tellers? Where I could build a world and the story of the characters in it, and work with the team of developers to make it into a product? And how would I find a position like that?
      Because, I truly think I could be great at that. I've thought before that If I could find the right person to show it to, I could put together a sort of portfolio, showcasing a selection of, lets say, 3 concepts. With summaries of the World, characters, plot, etc. I really feel I have a gift for this, and many other people have recognized the same. I just need to know where to take this gift to use it.
    • By ToeBeans The Brave
      I spent a lot of time making this unfinished animation, but afterwards I realized I had no idea what the heck I was going to do with it. I'm making a 2d pixel game and I wasn't sure how I would go about implementing this. When you look at it, what do you imagine would be there after the balloons float away? A loading screen? An achievement? The start of a new chapter? Credits??

    • By Danzabarr
      My question is about OOP, and best practice writing in C# for Unity.
      Say I'm writing components for an item system.
      Consumables have quantity.
      Weapons have durability, damage, block and stats.
      Armour has durability, armour and stats.
      Shield has durability, block, armour and stats.
      In this situation, should I...
      write a Consumable component, Weapon component, Shield component and Armour component that each extend an Item class? write a Quantity component, Durability component, Damage component, Block component, Armour component and Stats component, then add as required? write an Item component with all the possible fields plus an enum that decides which ones go unused? I like 1) because it defines the items by what they do, but there's repetition of fields horizontally in the inheritance tree.
      I like 2) because there's no repetition, but it allows for the creation of items that don't make sense. There's no strict definition going on, just the existence or non-existence of components, and some might need to be mutually exclusive.
      I like 3) because it's the solution to the problem with 1), and the enum is kind of a solution to the problem with 2), but it seems wasteful to deal with a larger data structure than required for every item.
      Any thoughts?

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!