In Java they are also called POJOs (plain old java objects). What this all means is, that the models (robots) don’t know anything about how to draw themselves, or how to change their state (position, hit points).

4 – The renderer ( view) gets notified about the state changes and renders the world’s current state.

If the move action was created, then it changes the position, if the attack, then it fires.

3 – The controller updates the robot‘s ( model‘s) state accordingly.

For example if the terrain is occupied by an enemy, an attack action is created, if it is empty terrain, then a move action is created and finally if the place where the user tapped is occupied by an obstacle, do nothing.

2 – The controller handles the click/tap and converts the event into an appropriate action.

1 – User clicks/taps somewhere on the screen.

In an example game where the player controls a robot the following can happen: The following diagram is the simplest logical representation of the model view controller concept. The usefulness is quickly noticeable in the early stages of any game development project because it allows to change things quickly without too much rework of code in all layers of the application. It helps separate the input logic, the game logic and the UI (rendering). One useful architecture pattern in game development is the MVC (model-view-controller) pattern.

Java game engine