Player sub classes

Player: Contains information and operations of game Player

• Player
  // hint: they should have a different data structure or different operations
  • Human Player
  • AI Player
  • Idle Player (for Gaia or multiple independent Gaias) (or even Gaia Player)
  • Dummy Player (usually provided in many modding environments, eg. used as a bank)

Controller: Takes input from a source (eg. gui, AI) and transforms them into game actions

• Controller
  // hint: they should have a different input source or different generated game actions
  • Human Controller (gui actions to actions)
  • AI Controller (AI algorithms to actions)
    • Scripted Controller (Combines fixed actions and actions from AI algorithms)
  • Empty Controller (do nothing)

Old post

At some point the class Player will become the base class of something like this

• Player
  • Human Player
  • AI Player
    • Scripted Player (for campaign like stuff)
  • Idle Player (for Gaia or multiple independent Gaias)
  • Dummy Player (usually provided in many modding environments)

Any suggestions on the topic? different tree? other sub classes?

No files, tests, or entry points are named. Start by locating the existing Player and Controller definitions and reviewing the unresolved design discussion; done would require an agreed subclass model and its implementation.