Component

Defines a component that can be added to a host object.

Component<THost> is the structural primitive — the lowest-level shape the engine recognises. For most game code you'll reach for one of the named specialisations instead:

• WorldComponent — a component attached to the World itself (input samplers, physics broadphases, rendering systems, audio mixers).
• WorldObjectComponent — a component attached to a WorldObject (controllers, graphics, colliders, behaviour logic).

Those specialisations layer on a typed resolveDependencies method and a richer dependency-aware lifecycle on top of this primitive.

Update phases

Each world tick runs three update phases in order, and every component on every host is offered each phase before any host advances to the next:

1. onPreUpdate — sample/prepare state that downstream components will consume. Good places for input polling, per-frame buffer clears, or interpolation snapshots.
2. onUpdate — the main per-frame work: behaviour logic, movement, simulation. This is the phase that the majority of components will implement.
3. onPostUpdate — react to the result of everyone else's onUpdate. Canonical use case: a camera reading the player's already-moved position, or a graphics component syncing its transform from the host position one final time so it never lags by a frame.

Within a single phase, world-scoped components run before object-scoped components — see World.update for the full schedule. All three update hooks are skipped on components whose Component.enabled field is explicitly false.

onPreUpdate and onPostUpdate are optional — a component that only needs the main phase can omit them and the engine will skip them at zero cost. onUpdate, onAdded, and onDestroy are required so the engine can rely on them being callable.

Dependencies

Every lifecycle hook receives a deps argument carrying the dependencies declared by the component's optional resolveDependencies method. Components with no dependencies see an empty object and almost always omit the parameter at their hook signatures — TypeScript allows dropping trailing parameters when implementing the interface. Components that do declare dependencies should reach for WorldComponent or WorldObjectComponent so the deps parameter is properly typed everywhere it appears.