The do’s and don’ts of Game Development.

Ok StarField Battle 4 months ago would have never passed peer review, or would have never been allowed on XBLIG.  I am going to tell you from memory when was wrong with the game.  I am glad that the reviewers and play testers helped me find all the bugs that were in the game.  First I will tell you what not to do when making a game.

What not to do:

1. Do not submit a game to peer review before testing (I didn’t do this but it had to be said)
2. Do not submit a game to play test and have the play testers look for the bugs for you.
3. Don’t just think that if you get all good feedback in play test that it is OK to go straight to peer review.
4. DON’T RELEASE YOUR DAMN GAME THE SAME TIME A CALL OF DUTY GAME COMES OUT.

What to do:

1. Play test your own game and try to break it as much as possible.  If you can’t find any bugs, code errors,  or glitches in the game then submit to play test and ask the play testers to help out.
2. Try to market your game as much as you can.
3. Try to get your friends to give you feedback on your current version of the game.  Maybe they will give you ideas on features or game play mechanics that can better the game.
4. Give yourself lots of time to work on the game.  I originally started the game in April and had until August to finish.  I didn’t finish, and well here we are.  If I could I would go back in time, and submit my current version of the game to DBP.

These are just a few thinks that I could think of, but there are probably more.  Stanfield Battle If far from perfect, but I am proud of my work and hopefully the game does well.  I am planning on making another game but don’t know when I will release it.  Maybe before December or maybe I will just wait and put more work into it.  I had a lot of fun working on my game and can’t wait to make another one.