One game. A shared state.

01 / The challenge

The question behind the system.

Keep game rules, user actions, persistent data and client updates consistent across a network boundary.

A networked Othello implementation separates the user interface, game authority and common protocol into Maven modules. The server owns the game state, while clients request actions and render updates.

02 / The approach

From architecture to implementation.

1. 01

   Define a common message contract between client and server.

2. 02

   Keep state changes on the server and send updated game information to clients.

3. 03

   Apply strategy, command and data-access patterns to CPU opponents, undo/redo and persistence.

03 / Outcomes

What the work shows.

• The project includes a JavaFX client, server-side game engine, undo/redo, CPU strategies and stored game data.