7 For simple technology, so I could focus on gameplay. Braid is a 2D game.I chose 2D:For simple technology, so I could focus on gameplay.To enable a human-feeling art style.We will come back to these points!
8 My Interests Games that are meaningful to people (not just “fun”). Creating mind-expanding experiences.Pushing the boundaries of what a “game” is.
14 Programming, Design, and Art are “surface skills”. There are also crucial“guiding skills”that they don’t teach in schoolor publish employment notices for.Without these guiding skills,the surface skills will be misdirectedand the game will miss its potential.
15 Focusing on problems we see all the timein work from indiesand academia.
35 There’s a little trinket outside, but it’s just there to distract you from the giant treasure chest behind the secret door.
36 PushingDon’t accept something just because it is a successful implementation of what you set out to do.Reject it because it doesn’t feel as compelling as you had imagined.Pushing really is a skill to be learned and practiced,not just a thing you decide to do one day.
37 “The First One Sucks.”If it’s all you can do to barely get a game finished...that game is not very good.If you think it is good, your Inverse Conveyance is probably broken.Students and indies fall into this trap all the time.Braid was fully playable from end-to-end in December but it’s not done yet!
38 Your first playable version is not your game. It’s just the starting pointfor you to Push and Conveyto a much better place.
39 Side-Effects of Pushing in Design, Art, Programming
40 Pushing DesignBe prepared to change your idea of what the core gameplay is.Listen to what the game is telling you. It knows itself better than you do.Be prepared for a lot of detail-oriented special-case design.
41 Pushing Art Lots of preproduction, trying many alternative directions. Be prepared to throw away and re-do many things you thought were done.This is important because of theinteractions between programming, art, anddesign that we saw before.
42 Pushing Programming Be prepared to rewrite subsystems 5 times! You have to be very productive.For Example: Don’t spend time debugging!Make code without bugs.Know the cause of a problem before looking in the debugger.For Example: Don’t fall in love with complicated code!
43 If you are a renaissance indie developer, programming needs to be extremely easy.A non-thoughtful, low-energy taskor else it will eat all your time and effort.(and will dominate the mixing process mentioned earlier.)
45 My game Braid was 2D and it still took 3 years to make! Too Much 3D!Bogs down all of Programming, Art, and Design!Very few games must be 3D. And the 3D of a student or low- budget indie project tends to be ugly and clumsy.The 3D eats all the effort for your project, and there is no effort left for the actual game.Yet schools seem to encourage 3D. It’s unfortunate.My game Braid was 2D and it still took 3 years to make!
46 Ludological Hermeneutics Sometimes you need a big word to describe something nuanced.But you never need to string many of them into an impenetrable sentence.If you’re too busy shouting big words, you’re not listening to the quiet, subtle reality of your game.
47 Overengineered Program Structure Deep and wide class hierarchies, excessive abstraction.Slow compile and link times.If you need a class diagram, It’s Too Complicated.
Your consent to our cookies if you continue to use this website.