RiskGame

Problem

Many student projects work until you add one more feature. For this project, the goal was to build a Risk-style game that stayed maintainable as gameplay rules evolved.

What I built

A desktop strategy game in Java, structured around MVC so UI concerns, domain rules, and data flow stayed separate.

How I designed it

I used the State pattern to model game phases and the Command pattern to represent player actions as objects, making actions easier to validate, queue, and log.

Outcome

A feature-rich game that was easier to extend because the patterns and boundaries made change safer.

Highlights

• MVC architecture separating UI, domain rules, and data flow
• State pattern for modelling game phases
• Command pattern for player actions (validate, queue, log)