This chapter is from the book
This chapter is from the book
This chapter is from the book
Points to Remember
If you just sit down and start coding a game, designing as you go, you are sure to encounter problems. You need to have a plan!
Your plan should include quantifiable, repeatable steps that could apply to any game—not specific steps that pertain only to the one you're working on.
Make your first game plan a simple one. You have a much better chance of completing it, you'll learn the ropes, and you won't get too frustrated. Avoid role-playing games your first few times out.
Make sure to find out if the kind of people you think will like your game actually will.
Be realistic about what you know how to accomplish and what you don't up front. Find resources to help you in your deficient areas.
The more work you put into specific game features up front, the more likely you are to be frustrated if you find you have to jettison them along the way.
Know where you're going to be able to run a game before you include processor-intensive features that your setup may not be able to support.
Test, test, test! And don't take the critiques personally. They are all going to help make your game better.