script-components

Create a .ts file under assets/scripts/ exporting a single class whose constructor starts with public src: string and public entity: Entity, followed by your configurable params. Add optional start() and update(dt) methods for load-time and per-frame logic.

Script files must live inside assets/, typically assets/scripts/. The scene tsconfig only includes src/**/* and assets/**/*, so a root-level scripts/ folder is excluded from type checking and the Script component path will not resolve.

The most common cause is using decorator syntax like @action() above a method. The Creator Hub parser has no decorators plugin, so parsing fails and all params and actions silently vanish. Use only the @action JSDoc tag inside a comment block.

Declare the param as Slider<Min, Max, Step>, for example public speed: Slider<0, 10, 0.5> = 1. The runtime value is a plain number; the type only tells the editor to render a slider. Copy the local type alias into your script since scenes cannot import it yet.

Do not pass child entities as Entity params because entity IDs are not stable across scenes. Instead, iterate the hierarchy at runtime and match the child Name component with a substring check like startsWith, so duplicated items with auto-numbered names still work.

Do not use Script components for regular scene index.ts code or global engine systems. Script components are for self-contained per-entity behavior; global systems and scene-wide state belong in the scene runtime instead.