The Player

There is a distinction between the player, and the representation of the player called an avatar. The avatar only knows enough about the player state to show an accurate representation of the player in the game, which could be items that become visible if worn. The player is the person playing the game, and information regarding that.

To represent this distinction there will be two separate class called Player and Avatar, and the following UML diagram illustrates the initial idea of how they should be placed.

The map knows the position of the Avatar, and the tile on which the avatar is placed also holds a reference to get any state modifiers for the tile. The player holds a reference to the map, to which the player can inform and changes to its representation.

I remember the distinction between Avatar and Player from some of my university work, and would like to try to use it.