This README contains basic information about the project and its artifacts. If kept up to date, it will act as a primary dashboard for the project.
- Benjamin Lincourt
- Neville Lewis
- Jonathan Coyne
- Nick Pels
- Sky Barg
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 this project is to learn about game design and development in a team based environment while producing a quality project for use in our personal portfolios
Discord is used to communicate team meeting information, to allow team members to attend group meetings through the voice chat, and to alert members whenever changes have been made to the git repository
Meetings from 4-5 tuesday and friday
Repository so far mostly unchanged as far as structure, But the documentation has been updated
Instructions about the required documentation/activities for each milestone can be found in [instructions/](instructions/Milestone Instructions.md).
| File/Directory | Contents |
|---|---|
| doc/mtgLog.md | A log of team meetings and general progress. Update this with each team meeting. |
| README.md | This document. A general project overview and artifact guide. Update this as needed with extra references, etc. |
| 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. |
- 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.)
You can incorporate images into this document by adding them to the folder and then linking them using the markdown syntax .
For example  results in:
