This class will be instanciated for each entity of the scenario.
Another solution than using this class would be to create either Components or DataModels and attach them to the Entity catalog.
It is faster and more convenient to directly add members and methods to the Entity class and the choice to use one way or the other is let to the programmer.
Using this class is lower lever than using a Model (Component or a DataModel) but simpler. The main drawback is that members (variables) will not be dynamically modifiable by the user like using a Model.
Player
The Player class is similar to the Entity class except that it will have no dynamic nor export component nor position.
Only one Player will be instanciated and attached to the scenario.
Inheritance
For both Entity and Player classes, user can specialize children classes and set any Entity (from the Scenario or the Catalog) to be linked with the children class.
Different classes can then be defined including their own data members and methods.
Because these child classes have their own Initialization phases (called after parent ones), specific values (or methods with specific parameters) can directly be called from there. Also, it is possible to set some Entity virtual methods to specialize them.
