Class StateMachine

Hierarchy (view full)

Constructors

constructor

Properties

change$ destroy$ gameObject label state state$ update$ validators

Methods

destroy getValidators setState setValidators update validateStateChange

Constructors

constructor

Properties

Readonly change$

change$: Subject<string[]> = ...

Before his state changes, it emits this subject.

Readonly destroy$

destroy$: Subject<void> = ...

When Lifecycle Object is destroyed, it emits and closes this subject. Along with destroying his children, which in turn behave the same.

Readonly gameObject

gameObject: GameObject

Parent GameObject is assigned at creation.

label

label: string = 'StateMachine'

Each Lifecycle Object has label for pixi debugging.

state

state: string = ''

Current state of the State Machine.

Readonly state$

state$: Subject<string> = ...

After his state changes, it emits this subject.

Readonly update$

update$: Subject<number> = ...

When Lifecycle Object is updated, it emits this subject. Along with updating his children, which in turn behave the same.

Protected validators

validators: Record<string, TStateValidator[]> = {}

Validators for state changes.

Methods

destroy

getValidators

setState

setValidators

update

  • update(deltaTime): void

  • Updates the Lifecycle Object with actual deltaTime ~60fps

    Parameters

    • deltaTime: number

    Returns void

Protected validateStateChange

Settings

Member Visibility

Theme

On This Page

constructor change$ destroy$ gameObject label state state$ update$ validators destroy getValidators setState setValidators update validateStateChange