Starting to make a game a week
Hi there, I’m Curial, a passionate game designer, quite a bit inevitably entrepreneur, former producer in a small, cofounded, multimedia studio and right now and finally, a want to be indie game developer.
Yet how do someone becomes an indiedev?
I tried that way about having an idea, some friends to work with, no budget at all and that willpower to kill your free time to get this idea done to became a great game. But it didn’t worked, it was an inspiring process with lot of usefull lessons but kind of a failing one I think manly for 3 reasons:
The idea was too much incomplete. It still seems great to me but I learned that an idea is great when you can not only explain but demonstrate it. Ideas are so different in every mind wether players or even its current devs but the game is something specific and this tangible material is what must be great itself not the idea. Users don’t play with geniouses devs ideas, they play with their games.
We weren’t a developer team, we were friends and dev colleagues. Even we respected our opinions and team roles we had different aspirations. I learned that a “garage team” it’s hardly a work team.
No budget and a flexible timing plan is an error. If there is no budget at least it is imperative to have savings so team can really focus part of its time in game dev and achieving milestones. Milestones are essential to control the evolving process of the idea, when you miss milestones your game idea becomes messy and hard to transform in a fun and playable game.
We were like an aspiring music band: It was fun, we loved to be part of it but with no net to save a fall, we were no prepared to be much serious and preferred to look for an stable job.
And I ended up with that feeling: you can only become an indie dev with a successful student project or winning the lottery.
Fortunately to me, there’s Gamasutra. When I’m low in gamedev confidence I always go to gamasutra where I find lot of inspiring articles about all game dev disciplines: production, design, programming, art… and found this Vlambeer’s cofounder Rami Ismail revealing article: Game A Week: Getting Experienced At Failure talks about the importance of demystify the power of the ideas and turn our efforts into the process. Not only learn and improve the process but enjoy it too.
Since this read I followed more people that talked or were conducting this practice and find MsMinotaur’s work who was making a game a week during a whole year and close to end talked about her experience un GDC ‘14. That seemed to me a huge enterprise but absolutely inspiring and I decided to start saving some funds and freeze my multimedia studio association to begin with it following this rules:
Make a game every week. Start the project after Monday 12:00AM and finish it before Sunday 11:59PM. It does not matter whether the game is digital or analog. It does not matter what you use to create the game. The only rule is to make a game.
Release the game every week. Whatever you make, whether it is complete, stable, polished or good, release it to the world through a website you specifically set up for this goal. Spread the link to the page of the game of the week on every social medium you own. Ask people to give you feedback. Wordpress or itch.io are quite capable of handling this.
Do not revisit a game. You can go back and revisit games after you’re done. You cannot work on previous week’s game or idea again the next week. This is not about exploring specific games, this is about gaining experience. If a game is so special it sticks for a while, you can work besides Game A Week or after you’re done. You still have to complete something else each week.
Try and avoid patterns in your work. Try and do something completely different each week. Instead of making digital games, try making an analog game. Instead of making an action game, make a puzzle game. If you find yourself in a pattern, take note of that pattern and break out of it for a week or two before deciding to head back. Make patterns a conscious choice, rather than an accepted and unquestioned reality.
Reflect. Spend each week talking to some people that played your game. Write down your findings in a journal (or in a blogpost). Write down what you made, what went right, what went wrong and what was interesting.
Making a game in a week is an achievable task even for one alone developer with not budget at all. Anyone can do a game in a week if doesn’t expect something great but in only a week, the dev will have thought an idea, design it, programmed, make some art, tested, published and take some postmortem conclusions.
I’ll start with this for 2 months (according science, humans need about 66 days to get a habit) and if my funds permit it, look to length for more time. Each week I’ll post a report from my game in this blog and mybe in a few months I find myself prepared to start an indiedev project again!