Emily Horton
Alexa Amoriello
Emily Zeh
Destiny Treptau
Brandon Service
The primary goals of this project are the following:
- Practice with the development of a larger project over the course of a semester
- To gain experience working as a part of a small team
- To implement a variety of game-related algorithms
- To implement data structures for a game
- To have fun making a game
The goal of Base23 is to create a game that is fun and enjoyable for gamers of all ages and skill levels. Our game Shiro will feature a unique battle mechanic that involves rythm that anyone can understand and play with.
We feel as though our game will be a success as long as people enjoy playing it. We understand that because it is a first-year student project, it will be fairly limited in scope and overall polish. However, we have believed from day one that with our combined creativity, we will make a fun game to play.
This group will use the private Discord channel in the IGME 106 Discord Server.
Weekly meetings will be held Friday in GOL 2000 between 4-6PM.
Instructions about the required documentation/activities for each milestone can be found in [instructions/](instructions/Milestone Instructions.md).
| File/Directory | Contents |
|---|---|
| EmLevelEditor | The folder containing our level editor for Shiro. Includes its own documentation. |
| KeyPressEditor | Contains our external tool for creating enemy attack patterns. Includes its own documentation. |
| Shiro | Contains the project files for the game Shiro. Includes the solution file, class files, and assets, including level and attack patterns |
| doc/mtgLog.md | A log of team meetings and general progress. Update this with each team meeting. |
| doc/milestones.md | Milestone overviews and lessons learned. Update this with each milestone. |
| doc/GameDesign.md | Game concept and game play design. Write this in milestone 1, but keep it up to date throughout the project. |
| doc/Art.md | How the game will look and feel. Includes verbal descriptions, stories, mock-ups and concept art. Write this in milestone 1, but keep it up to date throughout the project. |
| doc/Architecture.md | Technical documentation describing the classes required to implement the game (and how these classes will interact) Write this in milestones 1&2, but keep it up to date throughout the project. |
| doc/Production.md | Project scope, planning, and task management information. Write this in milestone 1, but keep it up to date throughout the project. |
| doc/Presentations.md | Presentation instructions and materials for each milestone Update this with each milestone. |
| src/ | Implementation artifacts. |
| src/ReleaseNotes.md | Summary of the implementation progress made during each milestone. Update this with each milestone. |
| README.md | This document. A general project overview and artifact guide. Update this as needed with extra references, etc. |
- MonoGame Documentation
- Course schedule
- This UML class diagram reference probably has more than you'll need, but it's a good starting point.
- Markdown is a convenient method of documentation because it can have nice formatting while still being a plain text file (which allows multiple team members to edit sections and view/merge differences). (I'm requiring it for this project because it also allows me to easily see changes over time and who worked on different sections of a document.)