> For the complete documentation index, see [llms.txt](https://steijn.gitbook.io/devlogs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://steijn.gitbook.io/devlogs/blewscreen/rezone/preparation.md).

# Preparation

To start the project I was given a document stating the game rules and a [video ](https://www.youtube.com/watch?v=QQa5J4-SGfE)of the old showcase. After seeing how little we had to work with I started planning the game with my co-intern. We discussed in detail:

* what classes we would require(discussed below)
* dividing the work
* where we would use enums
* naming conventions
* Git branch usage
* Health formulas

{% file src="/files/aikYWZ5Uq0PN5OmKKpD0" %}
The document I was given
{% endfile %}

First, we planned out the following necessary classes.

We required a centralized script for regulating the game and its settings: a "GameManager".

We also needed a "ZoneManager" to regulate the zones themselves.

We needed some way to keep track of the zone health and health UI, which became "Health" and "HealthBar" respectively. We considered how health needed to be calculated as well as what multipliers were needed. Since the rules want the buildings to influence the health gain we've made a formula.&#x20;

We needed the pawns to move and show their pathing. For this we were going to use a "Movement", "Line", "LineRenderer" and "ArrowHead".&#x20;

We later also found out that we needed buildings to be done, which became a "BuildingManager" and "Building" script.&#x20;

This became our planning and schedule to follow.

In the end, we managed to make it look and feel very closely to the old game. To me the project was a success, seeing how we started with next to no previous documentation.&#x20;
