Avatar

Model

An avatar is an entity with one or many body structures. An avatar can have extra modules registered. Variables of this model are described bellow:

Body structure

• Bodies: List of possible different armatures (not representations) that represent a same user.

• Body: First item of the list of bodies. Handy for avatars with one body (most common case).

State

• Ready: AvatarController.ControllerStart() has been called and completed.

Extensibility

• Registry: List of controllers (HPTKControllers) of registered extra modules.

View

Events

• OnStarted: Invoked after starting/validating each sub-model and after calling ControllerStart() of each of the HPTKControllerpreviously self-registered in AvatarModel or any of its sub-models.

Some modules can be registered on the fly, after OnStarted is called. Using OnStarted to ensure that modules are ready is valid for modules that are self-registered beforeAvatarController.ControllerStart() is called.

Controller

Buttons

• Awake This: Call HPTKController.ControllerStart()

• Awake Children Models: Call HPTKModel.Awake() for this model and any other HPTKModel under this. HPTKModels will try to fix missing references in their Awake() function.

• Awake Children Views: Call HPTKView.Awake() for this view and any other HPTKView under this.

• Awake Children Controllers: Call HPTKController.Awake() for this controller and any other HPTKController under this. HPTKController of modules will perform self-registry in their Awake() function.

• Start This And Registered: Call HPTKController.ControllerStart() which internally will call ControllerStart() for any of the controllers registered in AvatarModel or any of its sub-models, recursively.