This document will guide you through creating a small indie game from idea to release.
The goal is not to create a perfect game, but to learn the process of designing, building, testing, and finishing a game.
A finished small game is better than an unfinished big game.
You will research games, decide on your idea, and create a project plan.
Deliverables:
- Research sheet
- Game pitch
- Game Design Document
- Storyboard
Create a simple playable version of your game that demonstrates:
- Core mechanics
- Player controls
- Basic gameplay loop
This version does not need art or sound.
Deliverables:
- Working prototype
- Core mechanics working
- Player controls working
- Basic gameplay loop working
- Link to prototype on itch.io
Add the main features and content to your game.
Examples:
- Levels
- Art assets
- Sound effects
- UI elements
Deliverables:
- Playable game with
- Game length: 2-3 minutes
- 1-2 core mechanics working
- 1-2 levels or challenges
- Reasonable amount of art and sound assets
- No major bugs or crashes
Improve the game experience and release it.
Deliverables:
- Finished playable game
- Game length: 3-5 minutes
- 3 core mechanics working
- 3 levels or challenges
- All bugs fixed
- Improved visuals and sound
- Balanced gameplay (difficulty, pacing, upgrades, etc.)
- Published itch.io page
- Single player only
- No cloud saves or online features
Before starting development, describe your game idea.
-
Game Name:
-
One Sentence Pitch:
- Describe your game in one sentence.
- Examples:
- "A fast-paced puzzle game where players match falling blocks to clear lines and survive as long as possible."
- "A stealth-based platformer where players must avoid detection to complete levels."
-
Target audience:
- Who is your game for?
- Examples:
- "Casual mobile gamers looking for quick, addictive gameplay."
- "Indie game enthusiasts who enjoy challenging platformers."
Research 3-5 games similar to what you want to make. Populate the table below with your findings. Circle features you might want to include in your game.
| Game | Genre | Core Mechanics | Fun/Unique Features |
|---|---|---|---|
| Celeste | Platformer | Dash, wall jump | Tight controls, storytelling |
| - | - | - | - |
| - | - | - | - |
| - | - | - | - |
| - | - | - | - |
| - | - | - | - |
| - | - | - | - |
| - | - | - | - |
| - | - | - | - |
| - | - | - | - |
-
Game Name:
-
Genre:
-
Main Game Elements (List the main features you intend to make for your project. This should include what key elements your players will be doing in your game):
-
1.
-
2.
-
3.
-
4.
-
5.
-
-
The Number of intended Players:
Use this section to write a descriptive paragraph of how your game is played. You should be able to imagine the game from this paragraph alone.
Make sure to include the following:
- Player Objective: Example: reach the goal flag at the end of the level
- Win Condition: Example: reach the goal flag
- Loss Condition: Example: fall off the level
- Core Gameplay Loop: Repeated actions the player performs. Example: Player jumps → avoids enemies → collects coins → reaches exit → next level
List the most important mechanics.
Example: Jump, Run, Collect
-
1.
-
2.
-
3.
What makes your game interesting?
Examples:
- Collectibles
- Difficulty progression
- Specific mechanics (e.g. double jump, wall climb)
- Time-based score
Describe what the player character can do.
Example:
Movement
- Run
- Jump
Player Stats
- Health
- Lives
Abilities
- Powerups
- Special abilities
Draw or sketch the major screens in your game.
Examples
- Title Screen
- Game Screen
- Pause Screen
- Game Over Screen
These can be simple drawings.
Break your game into systems.
Examples:
-
Player System: Movement and player controls.
-
Enemy System: Enemy movement and behavior.
-
Level System: Platforms, obstacles, and layout.
-
UI System: Score, health, menus.
- Provide a link to your project here
-
Art Style (Circle)
- Pixel / Cartoon / Minimal
-
Asset Sources (Circle)
- Self-made / Free Assets / Asset Store
-
Assets Needed
- Player sprite
- Enemy sprite
- Background
- Tiles
- UI icons
- [ ]
- [ ]
This is the Weekly Reports page. Document what you will work on each week during development to keep yourself on track for creating and planning when you will finish tasks.
- During weekly meetings with the instructor, document all tasks you will work on during the week.
- After the meeting, update this page throughout the week to track progress. Mark tasks as complete when you finish them.
| Week # | Date | Planned Tasks |
|---|---|---|
This is the Bug Tracker page. Document any bugs that you or your playtester (e.g., your instructor) encounters during development to keep track of what needs to be fixed.