Territory Forge

Strategy fans often want the depth of managing resources, characters, and combat, but without overwhelming complexity. 

• Demographic: 10-40 year old retro game lovers. 

• Casual to mid-core strategy players who enjoy management and tactical decision-making without needing to learn overly complex mechanics.  

• Challenge: Managing dynamic territory structures with villagers, buildings, and resources. 

• Solution: Designed an object-oriented backend with modular classes for Territory, Villager, Building, and Resource management. 

• Challenge: Preventing invalid villager assignments (e.g., knights in farms). 

• Solution: Implemented role-based validation logic ensuring only correct villager–building pairings. 

Although there's no DB I mapped out the game's models as a DB schema.

This helped me visualise the back-end structure and ensured each model table contained the correct columns, with the corresponding data-type.

This also enabled me to confirm foreign keys.

Defined the core gameplay loop (manage territories, construct buildings, create villagers, and assign villagers to buildings.

Outlined main entities (Territory, Building, Villager).

Planned object-oriented structure with separation of concerns.

Implemented base classes for Territory, Building, and Villager, with subclasses for specialised roles (e.g., Knight, Farmer, Blacksmith).

Created relationships (e.g., Villagers can be assigned/unassigned to Buildings, Buildings belong to Territories).

Added rules for villager assignments (only specific roles allowed in certain buildings).

This handled validation errors, to stop users entering invalid data by assigning villagers to the incorrect type of building.

Developed resource production system triggered by buildings.

Built validation rules (e.g., knight stats capped at total of 100 points).

Designed menu-driven navigation for all major actions (add, remove, assign, modify, view).

Implemented robust input handling with error messages for invalid inputs.

Enabled dynamic modification of knight stats within balance rules.

Added error handling to stop users entering stats total over 100 points, with explanitory messages to the user.

Ensured villagers automatically unassign when buildings are removed using a for loop.

Included detailed printouts of structures and knight stats for clarity using nested for loops.

Manually tested each feature to confirm correct game logic and error handling.

Refactored functions for clarity and maintainability (e.g., assignment validation, stat updates).