I recently ready a blog post called The Slow Application Development Methodology that got me thinking about what I enjoy about hobby roguelike development, but also some frustrating parts of dealing with my own limited productivity.
Here are some brief
design development principles for my current project, in the hopes stating them publicly will help me stick to them. These principles come from experience over the course of many 7-Day Roguelike Challenges (both successes and failures) and most importantly, learning my own weaknesses.
- Make a game YOU want to play
- You are not building a roguelike engine
- Don’t reinvent the wheel (ROT.js is your friend)
- Work on small chunks at a time – no grandiose leaps into refactoring hell
- You really, really, really aren’t building a roguelike engine
- Aim for a solid ‘coffee break’ game worth of content.
- When you have something that’s not embarrassing to play, get some feedback from real users
- Expand core gameplay only after #6 is done