Skip to content
Hurshal Patel edited this page Jun 16, 2014 · 1 revision
  1. Game Document
  • Game Design
    • core loop - your game should have a clear core loop that engages the user
    • game components - elaborate on the following components of your game. who/what/where/when/why
      • game state
      • player/avatar
      • mechanics
      • goal
      • theme
  • Artwork and assets
    • some sort of sketch for your players/enemies/items
    • a storyboard which explains what each screen will look like and how you will interact with it
  • Game Development
    • basic architecture - outline the basic structure for your game. You should have enough detail to answer questions like:
      • How do you represent enemies/players/items?
      • How do you keep track of the game state?
      • What kinds of things will you have to do to get user input (taps/swipes/accelerometer)?
  • Production
    • Timeline - how are you going to take on this monumental task? Break the development of the game into small, actionable steps. Keep in mind that group members can work on different tasks in parallel, so someone can be working on the art while someone else is working on the gameplay or fixing bugs.
      • List out action items and time estimates for:
        • Artwork and assets - what images, sounds, maps, etc will you need? What is the most basic version of these which you can use to test your first full game? You can use placeholders until the final versions of these are ready, so these action items should be very low priority in the beginning of your game.
        • Game development - what is the simplest interaction from your core loop that you can code and test? Once that is done, what order will you add extra features, such as power ups, a fancy user interface, more enemies, stats, etc. Keep in mind that most of these tasks are cumulative, so you won't be able to work in parallel on most of this. Some things like swipe detection and getting platforms to work are completely independent and can be done in parallel.
    • You can use something like Trello to keep track of tasks in a group and stay focused. Also, you can use Github's built in issues tracker and wiki to keep track of other details for your game.
Clone this wiki locally