Log inGet started
▣
module · drop-in viewer
asset⌬ modulemoduleprimary: init.luau·part ofpackage characterController.package·originates fromworld 07158574-5…

characterController

Physics-based character controller — capsule movement with ground / wall / ceiling detection. A kinematic controller using raycasts for collision; handles gravity, jumping, slope traversal, step climbing, wall sliding, coyote time, and moving platforms. The module owns a per-enti…

byzero-proxy @ DESKTOP-DB3UJOJ·posted 4mo ago
What it does

characterController

Physics-based character controller — capsule movement with ground / wall / ceiling detection. A kinematic controller using raycasts for collision; handles gravity, jumping, slope traversal, step climbing, wall sliding, coyote time, and moving platforms. The module owns a per-entity registry; attach once, call move / jump each frame, then drive a per-frame update(dt). The install / uninstall / preset surface wires up the standard set of components (CharacterController + Locomotion + MovementState + optional WASDInput and third-person camera child) in one call.

Require it to use the surface:

local CharacterController = require("@builtin::systems.characterController.characterController")

Exports

  • CC.attach(entityId: string, userConfig: Config?) — register an entity, merge user overrides over Defaults.standard.
  • CC.detach(entityId: string) — drop the registry entry.
  • CC.move(entityId: string, direction: Vec3) — set per-frame world-space movement input (y is ignored).
  • CC.jump(entityId: string) — request a jump; honours coyote time and jump buffer.
  • CC.getState(entityId: string) -> State — snapshot copy of grounded / falling / velocity / etc.
  • CC.getVelocity(entityId: string) -> (number, number, number) — current vx, vy, vz.
  • CC.setGravity(entityId: string, gravity: number) — update gravity at runtime.
  • CC.setMaxSlope(entityId: string, degrees: number) — update max walkable slope angle.
  • CC.setConfig(entityId: string, key: string, value: any) — update a single config key.
  • CC.getConfig(entityId: string) -> Config — config copy.
  • CC.update(entityId: string, dt: number) — advance one frame (resolve movement, write position, tick state machine). dt is clamped to 0.1.
  • CC.isAttached(entityId: string) -> boolean — whether the entity has a registration.
  • CC.install(entityId: string, opts: InstallOpts?) -> InstallResult — high-level wire-up (components + optional camera / mesh / WASDInput).
  • CC.uninstall(entityId: string) -> UninstallResult — remove everything install added.
  • CC.preset(entityId: string, presetName: string) -> PresetResult — apply a preset to an already-installed character in place.

Types:

  • Vec3 = { x: number, y: number, z: number }
  • Config = { height?, radius?, maxSlopeAngle?, stepHeight?, gravity?, jumpForce?, coyoteTime?, jumpBuffer?, maxJumps?, airControlFactor?, groundSnapDistance?, skinWidth?, moveSpeed? }
  • State = { grounded, falling, sliding, wallContact, wallNormal, velocity, groundNormal, slopeAngle, jumpCount, timeSinceGrounded, timeSinceWallContact, onMovingPlatform, platformEntity? }
  • BundleRef = { guid?, __ref?, identity?, path?, name? }
  • InstallOpts = { preset?, camera?, input?, mesh?, overrides? }
  • InstallResult = { entityId, cameraId?, meshHostId? }
  • UninstallResult = { entityId, despawned }
  • PresetResult = { entityId, preset, applied }

Usage

local CharacterController = require("@builtin::systems.characterController.characterController")

-- Low-level: manual attach + per-frame drive.
CharacterController.attach(entityId, { gravity = -15, jumpForce = 7 })
CharacterController.move(entityId, { x = 1, y = 0, z = 0 })
CharacterController.update(entityId, dt)

-- High-level: one-call wire-up.
CharacterController.install(entityId, {
    preset = "humanoid_default",
    camera = true,
    overrides = { jumpForce = 8 },
})

Notes

  • attach merges user config over Defaults.standard; passing unknown keys is allowed (they survive into the config table).
  • update clamps dt to 0.1s to prevent capsule tunnelling on lag spikes.
  • getState and getConfig return shallow copies — mutating the result does not affect the controller. The returned velocity / wallNormal / groundNormal are also shallow copies.
  • install is idempotent per component — re-running on an already wired entity adds nothing new. uninstall removes the components and any third-person-camera child that targets this entity.
  • preset mutates fields in place and never adds or removes components — call install first.

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

conforms to

zero/source-extract/v2

CharacterController Module Physics-based character controller — capsule movement with ground/wall/ceiling detection. Kinematic controller using raycasts for collision. Handles gravity, jumping, slope traversal, step climbing, wall sliding, coyote time, and moving platforms. Attach to any entity, then call `move()` each frame with the desired direction. Query state via `getState()` for grounded / falling / velocity / etc. `install` / `uninstall` / `preset` are the higher-level surface that wires up CharacterController + Locomotion + (optional) third-person camera child in one call. Consumers: local CharacterController = require("@builtin::systems.characterController.characterController") CharacterController.install(entityId, { preset = "humanoid", camera = true }) CharacterController.move(entityId, { x = 1, y = 0, z = 0 })

CharacterControllerWASDInputLocomotionMovementStateCameraorbital_follow

mergeConfig(userConfig: ?) → void

Internal: merge user config over Defaults.standard. Returns a new table.

argtypedescription
userConfig?

attach(entityId: string, userConfig: Config?) → void

Attach a character controller to an entity. Creates a state machine and zero-velocity registry entry; subsequent calls to `move` / `jump` / `update` target this registration. Warns and no-ops on an empty `entityId`.

argtypedescription
entityIdstringThe entity to control.
userConfigConfig?Optional config overrides — see `Defaults.standard` for keys (height, radius, gravity, jumpForce, …).

examples

CharacterController.attach(entityId, { gravity = -15, jumpForce = 7 })

detach(entityId: string) → void

Remove the character controller registration for an entity. No-op when the entity is not registered.

argtypedescription
entityIdstringThe entity to detach.

examples

CharacterController.detach(entityId)

move(entityId: string, direction: Vec3) → void

Set the desired movement direction for this frame. Direction is world-space; magnitude determines speed. The Y component is ignored. Call once per frame before the controller updates.

argtypedescription
entityIdstringTarget entity.
directionVec3`{ x, y, z }` world-space movement vector.

examples

CharacterController.move(entityId, { x = 1, y = 0, z = 0 })

jump(entityId: string) → void

Request a jump on the next update. Respects the controller's coyote-time and jump-buffer windows.

argtypedescription
entityIdstringTarget entity.

examples

CharacterController.jump(entityId)

getState(entityId: string) → any

Snapshot the full state of a controller — grounded, falling, sliding, wall contact, velocity, slope angle, jump count, moving platform info, etc. Returned table is a copy; mutating it does NOT affect the controller.

argtypedescription
entityIdstringTarget entity.

examples

local s = CharacterController.getState(entityId); print(s.grounded)

getVelocity(entityId: string) →

Read the current velocity as three return values.

argtypedescription
entityIdstringTarget entity.

examples

local vx, vy, vz = CharacterController.getVelocity(entityId)

setGravity(entityId: string, gravity: number) → void

Update the gravity acceleration for a specific controller.

argtypedescription
entityIdstringTarget entity.
gravitynumberGravity acceleration (negative = down).

examples

CharacterController.setGravity(entityId, -20)

setMaxSlope(entityId: string, degrees: number) → void

Update the maximum walkable slope angle (degrees). Slopes steeper than this register as `sliding` ground instead of walkable.

argtypedescription
entityIdstringTarget entity.
degreesnumberNew maximum walkable angle.

examples

CharacterController.setMaxSlope(entityId, 50)

setConfig(entityId: string, key: string, value: any) → void

Update a single config value at runtime.

argtypedescription
entityIdstringTarget entity.
keystringConfig key name (see `Defaults.standard`).
valueanyNew value.

examples

CharacterController.setConfig(entityId, "jumpForce", 8.0)

getConfig(entityId: string) → any

Read a copy of the current config for a controller. Mutating the returned table does NOT affect the controller.

argtypedescription
entityIdstringTarget entity.

examples

local cfg = CharacterController.getConfig(entityId)

update(entityId: string, dt: number) → void

Update a character controller for one frame. Applies the pending jump request (if any), resolves movement against ground / wall / ceiling, writes the new position back via `localPosition.set`, and ticks the state machine. `dt` is clamped to 0.1 to prevent tunneling on lag spikes.

argtypedescription
entityIdstringTarget entity.
dtnumberFrame delta time in seconds.

examples

CharacterController.update(entityId, dt)

isAttached(entityId: string) → boolean

Check whether an entity has a character controller attached.

argtypedescription
entityIdstringTarget entity.

examples

if CharacterController.isAttached(entityId) then ... end

splitProps(props: ?, presetName: ?) → void

Internal: split a flat preset table into `{ ccProps, locoProps }`. Emits a warn for keys that don't belong to either component.

argtypedescription
props?
presetName?

merge(dst: ?, src: ?) → void

Internal: shallow-merge `src` on top of `dst` (both tables); returns dst.

argtypedescription
dst?
src?

install(entityId: string, opts: InstallOpts?) → InstallResult

Install CharacterController + Locomotion (+ MovementState + optional WASDInput + optional third-person camera child + optional skinned mesh bundle) on an entity. Idempotent — re-running on a wired entity is a no-op per component. Errors when `entityId` is missing or unknown. The character answers the player's controls once it is bound as the local player's body (`layers.active.players.localPlayer.avatar = entity(entityId)`); any other character moves on what writes its `CharacterController` input bus. name), `camera` (spawn a third-person camera child, default true), `input` (add WASDInput over the controller, default false), `mesh` (bundle ref to instantiate as a child), `overrides` (config overrides applied on top of preset). the corresponding feature was disabled / not requested.

argtypedescription
entityIdstringTarget entity (must already exist).
optsInstallOpts?Optional install options — `preset` (locomotion preset

examples

CharacterController.install(entityId, { preset = "humanoid" })

uninstall(entityId: string) → UninstallResult

Remove everything `install` added: AnimDebug / Locomotion / MovementState / CharacterController components, plus any child camera entity carrying an `orbital_follow` controller targeted at this entity. Errors when `entityId` is missing or unknown. child cameras removed.

argtypedescription
entityIdstringTarget entity.

examples

CharacterController.uninstall(entityId)

preset(entityId: string, presetName: string) → PresetResult

Apply a preset's properties to an already-installed character. Both CharacterController and Locomotion must be present. Mutates the matching fields in place; does NOT add/remove components or cameras. Errors when the entity is missing, not installed, or the preset is unknown. fields written across both components.

argtypedescription
entityIdstringTarget entity.
presetNamestringName of the locomotion preset whose values are applied.

examples

CharacterController.preset(entityId, "humanoid")
⌬ Types
Vec3 = { x: number, y: number, z: number }Config = {State = {BundleRef = {InstallOpts = {InstallResult = {UninstallResult = {PresetResult = {

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

Showing up to 3 levels deep. Open a part to see what it holds further down.

119+items
▣
module · born here
❒asset
▲ 0↑ born
▣
module · born here
❒asset
▲ 0↑ born
▣
module · born here
❒asset
▲ 0↑ born
▣
module · born here
❒asset
▲ 0↑ born
·
assettype · born here
❒asset
# Module (asset type) A module is a reusable, stateless (or globally-stateful) Luau library that other code pulls in with `require()`. Modules are the unit of factored-out logic in a world: helpers, math libraries, format parsers, registries, shared algorithms. ## When to use one - You have logic you want to share across multiple components, services, scenes, or tools. - You have a registry, lookup table, or shared cache that callers all read from / write to. - You want a stable API surface (`M.fn`) other code can depend on. If the logic is bound to one entity, use a `.component`. If you want a named UI of fields rather than functions, use a `.preset`. ## Where it lives - Source: `/zero/source/.../<name>.module/` - Identity: the source path with `/` written as `.` and each segment's type suffix dropped — `/zero/source/demo/beats.module` is `demo.beats`, and `/zero/source/kit.package/beats.module` is `kit.beats`, the container's name kept and its `.package` suffix gone. `asset.create` returns this string, `asset.resolve(...).identity` reads it back, and the `require` forms below write it as `<identity>`. - Folder shape: - `init.luau` (or `init.lua`) — module body. **Required.** Returns a table (conventionally named `M`). - `README.md` — instance-level documentation. **Required.** - `.metadata` — agent-editable tags + free-form fields. **Required.** ## How to create one ```luau asset.create("module", "<name>") -- Creates: /zero/source/<name>.module/ -- init.luau (canonical `local M = {} … return M`) -- README.md (instance README template) -- `folder` places it in a subfolder of /source, and that subfolder -- leads the identity: `{ folder = "lib" }` produces `lib.<name>`. -- `into` authors it inside a resolved container (a package, a toolbox), -- whose own identity leads the same way: asset.create("module", "<name>", { folder = "lib" }) asset.create("module", "<name>", { into = asset.resolve("myPkg.package") }) ``` ## How it operates 1. **Registration.** Writing `init.luau` into a `.module/` folder indexes the asset and registers the module path with the resolver. 2. **Loading.** The first `require("<identity>")` runs the file's body and caches the returned table. Subsequent requires from anywhere return the **same table** — this is the shared-state lever for "module-local" registries. The body runs in an environment of the module's own: a name it declares without `local` is readable by the module's own functions and by no other script, so an export reaches its callers through the returned table and nothing else. Requiring a component's folder runs its chunk the same way, once, and its `update`, `start` and `public` stay in that environment; a component runs on an entity through `entity(id).component.add(name)`. 3. **Hot reload.** Editing the file re-runs the module body and folds what it returns into the table already loaded, so that table keeps its identity: a caller that captured it with `require` reads the new source's functions and values through the reference it already holds, and a later `require` returns that same table. A key the new source drops goes away; a key something set at runtime stays. The body's own `local`s start again from their initial values, so state that must outlive an edit lives in `modules.state()` (`guides { path: "core/scripting-and-tasks" }`). 4. **Identity resolution.** A module is reached by its `<identity>`, and where the caller lives decides which spelling of it resolves. For a module in a **world**, from a caller in that same world — another module, a component, a scene entrypoint, or an `execute` chunk: - `require("<identity>")` — the identity on its own, resolved against the caller's own root. It carries every folder segment, so a module created with `{ folder = "demo" }` is `require("demo.beats")`. - `require("@root::<identity>")` — the same root-relative resolution, written out. - `require(".sibling")` — a module in the same folder, by its bare name; `..name` steps up one folder, `...name` two. Logs, stack traces and hot-reload notices name that same module `@local.source.<identity>` — its key under the world source root. The `<identity>` tail of that key is the form above, so a trace reading `@local.source.demo.beats` is `require("demo.beats")`. For a module in a **library** — content under `/zero/source/libs/@<lib>/` — `@<lib>::` addresses that library's root from anywhere: `require("@builtin::modules.transform")`. Mounting a world as a library moves its files under such a root and flips the caller root to `@<lib>::`, which is what keeps the root-relative forms above resolving across the move. ## Discovery - `asset.list("module")` — every registered module. - `asset.inspect("<name>")` — public functions, source path, this type README. - `ls /zero/source/<name>.module` lists the files the folder holds. ## Authoring conventions - Return a single `M` table from `init.luau`. Top-level statements with side effects run on first require — useful for one-time initialization, dangerous if they touch the engine before it's ready. - Write exported functions as `typed function`, not `function`: the argument types are enforced at the call and the checker knows the signature, so a caller's mistake is reported where they made it. - Annotate exported functions with `--!desc` / `--!arg` / `--!return` / `--!example` so the LSP, `tools.list`, and `asset.inspect` surface them. A function with no `--!desc` is reachable only by someone already reading this file. - Declare a VALUE with `Field.<kind>(default, mode, description)`, and a table whose members are reached through a metatable with `--!members <TypeName>` — the latter gives the surface its accepted member set, its type, and its documentation from one table. See `guides { path: "core/authoring" }` for all four rules and `modules/api/engine/entity.module/members.module` for a worked member table. - Keep module state in module-local upvalues or in `modules.state()`. A name the body declares without `local` lives in the module's environment, which every run of the module shares: a function the previous run left in place reads what the reload assigned. Module-locals start again from their initial values with each hot reload; the table `modules.state()` returns is the same table on both sides of every reload. - Prefer focused modules over kitchen-sink modules. If two halves of a module have no shared state, split them. ## Common pitfalls - **Cyclic requires.** A `require` chain that loops will return the partial table (the half built before the cycle was detected). Design for one-way dependencies. - **Engine-time side effects.** Don't `entity.spawn` at module top-level — the engine may not be ready. Expose an `M.init` and call it from a scene entrypoint. - **Hot-reload + module-local cache.** A module that caches expensive computation in upvalues loses that cache on reload — fine for dev, but be aware in performance work. - **`init.lua` vs `init.luau`.** Either works, `.luau` is canonical. - **Writing one while play runs.** A `/source` write made while play is running lands on the play shadow, and a guarded play-exit discards it unless it is kept. One `.module` write shadows `init.luau`, the `README.md` and the `.metadata` together. `vfs.write(path, bytes, { durable = true })` skips the shadow, and `vfs.promotePlayShadow` keeps what is already on it — the `core/vfs` guide has the model and what each route costs. ## Related types - `.component` — for entity-bound state + lifecycle hooks. - `.service` — generates content you don't have yet (a mesh, sound, texture, …) via a metered provider. - `.tool` — for a single agent-callable function with a YAML schema. - `.package` — to group several modules + components + scenes into one shippable folder. ## In the Inspector Exports: what the module exports (name, kind, signature), parsed from its source without running it, with **Check** (the LSP's diagnostics for its entry file) and **Open**.
▲ 0↑ born
▣
module · born here
❒asset
# defaults Default configuration presets for the character controller. Each preset is a flat `Config` table that `CharacterController.attach` / `install` merges over with user overrides. No behaviour, no state — just constants. ## Exports - `M.standard: Config` — baseline humanoid tuning. Used when no user config is supplied to `attach`. - `M.platformer: Config` — higher gravity, stronger jump, double jump, generous coyote time, high air control. - `M.heavy: Config` — taller capsule, lower max slope, weaker jump, minimal air control. Types: - `Config = { height, radius, maxSlopeAngle, stepHeight, gravity, jumpForce, coyoteTime, jumpBuffer, maxJumps, airControlFactor, groundSnapDistance, skinWidth }` ## Usage ```luau local Defaults = require("@builtin::systems.characterController.characterController.data.defaults") -- Use a preset directly: CharacterController.attach(entityId, Defaults.platformer) -- Or merge selective overrides: local cfg = {} for k, v in pairs(Defaults.standard) do cfg[k] = v end cfg.jumpForce = 8.0 CharacterController.attach(entityId, cfg) ``` ## Notes - Pure data, no engine calls. Safe to require at module load time. - These tables are shared singletons — mutating `Defaults.standard` in place will affect every later `attach` that uses it. Copy before mutating.
▲ 0↑ born
▣
module · born here
❒asset
# feel The rules that give a character its feel, shared by the `CharacterController` component and the package's character module (`Velocity.resolve` and the state machine), so both answer the same settings the same way. ## Exports - `Feel.DEFAULTS`: the feel a character has when nothing states another (`acceleration` 20, `braking` 30, `jumpForce` 5, `jumpHeight` 0, `jumpApexTime` 0, `minJumpHeight` 0, `fallGravityMultiplier` 1, `maxFallSpeed` 0). - `Feel.walk(vx, vz, wantX, wantZ, acceleration, braking, dt) -> (vx, vz, dx, dz)`: the ground velocity after `dt` seconds of walking toward the request, and the distance covered across the ground over them, exact for that motion. It speeds up along the request at `acceleration`, slows at `braking`, sheds the part across the request at `braking`, and brakes to a stop before a reversal speeds up the other way. 0 for either reaches the request at once. - `Feel.launch(settings, pull, held) -> (speed, rise)`: the take-off speed of a jump and how it rises, from `jumpForce`, `jumpHeight`, `jumpApexTime` and `minJumpHeight`, against the gravity `pull` (m/s², positive pulling down). `held` says the jump was asked for with the jump control held, which makes it one a release cuts. - `Feel.release(vy, rise, held) -> (vy, rise)`: a jump asked for held, once the control reads let go during its rise (on the step it takes off, for a request let go before then), is cut to the speed that tops it out `minJumpHeight` above where it was. - `Feel.vertical(vy, dt, rise, pull, settings) -> (dy, vy, rise)`: one step along up off the ground, integrated exactly: a rising jump against its own gravity, a fall at `pull * fallGravityMultiplier`, no faster than `maxFallSpeed`. A step crossing the top switches gravity there, so the stated height and apex time hold at any frame rate. - `Feel.jumpsAfter(jumpCount, maxJumps, footing) -> number?`: the jump count a granted request leaves, or nil. On its feet or within coyote time (`footing`) a character takes its first jump; past it the jump from the ground counts as spent and a request takes the next jump `maxJumps` leaves. ## Usage ```luau local Feel = require("@builtin::systems.characterController.characterController.movement.feel") local dx, dz vx, vz, dx, dz = Feel.walk(vx, vz, wantX, wantZ, 20, 30, dt) local vy, rise = Feel.launch({ jumpHeight = 1.2, jumpApexTime = 0.4, minJumpHeight = 0.4 }, 9.81, true) vy, rise = Feel.release(vy, rise, jumpHeld) local dy dy, vy, rise = Feel.vertical(vy, dt, rise, 9.81, { fallGravityMultiplier = 1.5, maxFallSpeed = 20 }) ```
▲ 0↑ born
◇
component · born here
❒asset
# Locomotion Blend-space-driven locomotion for entities running the characterController package. Reads horizontal velocity from a sibling `MovementState` (or, as a fallback, `CharacterController`) component on the parent and feeds a single 2D blend space (strafe-angle on X, speed on Y) with idle / walk-{F,L,R,B} / run-{F,L,R,B} / sprintF clips. Each clip's point sits at the speed the clip carries this body at: its retarget bake measures how fast the ground passes under the stance foot on this body's legs, so the feet move with the ground at whatever speed the body moves. A clip that plays without a measured speed sits at its gait's `walkSpeed` / `runSpeed` / `sprintSpeed`. Pair on the same entity (or a parent of) a `SkinnedModel`. The component creates the AnimGraph, polls for the SkinnedModel child once start() has run, registers the clips as blend-space points and plays the graph. `update()` damps speed + angle and writes them to the active blend space each frame. This supersedes the older FSM-based Locomotion controllers (crouch / jump / fall / land / turn-in-place state machine). Those behaviours can be added back as separate layered graphs once the blend-space driver has settled.
▲ 0↑ born
▣
module · born here
❒asset
# preset A preset holds typed values for one declarer's settings schema: an assetType's, an importer's, a component's, or any asset that declares its own settings. `preset.capture` saves the settings something has now, `preset.apply` writes a preset's values into something its target governs, `preset.values` reads them checked against the target's current schema, and `preset.setValues` replaces them, checked first. Exposed as the `preset` global via `--!global preset`. A preset's `preset.yaml` names its target as a guid envelope, `target: { __ref: <guid>, type: <type>, name: <name> }`, which the preset's `.refs` pins by guid with the target's checksum. A target written as an identity string is accepted on read, resolves by identity, reads as unpinned, and is rewritten as the envelope on the preset's next local edit. ## Exports - `preset.values(source: AssetRef<preset>) -> ({ [string]: any }, Report)` — the values that pass the target's current schema, and a report naming every one that does not. - `preset.apply(source: AssetRef<preset>, into: AssetRef | ComponentTarget) -> ApplyResult` — write the valid values into an asset the target governs, or into a component on an entity whose component is the target. Struct groups merge field by field. Raises when another declarer governs `into`. - `preset.capture(from: AssetRef | ComponentTarget, name: string, opts?: CaptureOpts) -> AssetRef<preset>` — save an asset's settings, or a component's live values on an entity, as a new preset targeting the declarer that governs them. A bare name lands in `/source/presets/`; an absolute `.preset` path lands where it says. - `preset.setValues(source: AssetRef<preset>, values: { [string]: any })` — replace the whole values table; any violation refuses the write, naming every one. - `preset.defaults() -> { DefaultRow }` — the world's Preset Manager rows, in order, each resolved with its problems. - `preset.setDefaults(rows: { DefaultRowInput })` — replace every row; every row is checked first and any problem refuses the write, naming every one. - `preset.addDefault(source: AssetRef<preset>, opts?: { filter: string?, at: number? }) -> number` — add a row for the declarer the preset targets; returns its index. - `preset.removeDefault(index: number)` — remove one row, keeping every other row as written. - `preset.defaultFor(declarer: AssetRef | string, path: string) -> ({ [string]: any }?, Match?)` — the values a new thing at `path` would take from the rows, and the row that gives them. Types: - `ComponentTarget = { entity: string, component: string }` — a component on an entity. - `Report = { format: string, target: string, targetGuid: string?, pinned: boolean, targetChanged: boolean, rejected: { Violation } }` — `target` is the target's identity; `pinned` is true when `.refs` pins the target's guid; `targetChanged` is true while the pinned checksum differs from the target's current one. - `Violation = { path: string, message: string }` - `ApplyResult = { applied: { string }, rejected: { Violation }, targetChanged: boolean }` - `CaptureOpts = { overwrite: boolean? }` — `overwrite = true` re-authors an existing preset, keeping its guid. - `DefaultRowInput = { preset: any, target: any?, filter: string? }` — a preset, its declarer (the preset's own target when omitted) and a filter (empty matches everything). - `DefaultRow = { index, target, preset, filter, targetGuid, presetGuid, targetName, presetName, problems }` - `Match = { index, target, preset, path, rejected, problem? }` — the row a creation took and the path it read. ## Usage ```luau -- Capture a texture's settings, then apply them to another texture local p = preset.capture("hero_sprite", "pixel_art") preset.apply(p, "enemy_sprite") -- Apply a component preset to a component on an entity preset.apply("synty", { entity = id, component = "Locomotion" }) -- Capture a component's live values local tint = preset.capture({ entity = id, component = "Model" }, "red_tint") -- Read the values and what the target rejects local values, report = preset.values("pixel_art") for _, v in ipairs(report.rejected) do print(v.path, v.message) end -- Replace the values preset.setValues("pixel_art", { filter = "nearest", generateMipmaps = false }) ``` ## Notes - Every read re-checks the values against the target's current schema, so a value a later schema drops or retypes is reported by path rather than applied. - `asset.create("preset", name, { target = <identity or guid>, values = { ... } })` authors a preset directly, with the same checks as `preset.capture`. - The Preset Manager rows are documented in `preset.defaults`; the filter grammar in `preset.glob`. - Submodules: `preset.document` (the `preset.yaml` format), `preset.target` (target resolution and checking), `preset.heal` (rewriting an older preset document in the current form on a local edit).
▲ 0↑ born
▣
module · born here
❒asset
# velocity Velocity integration and per-frame movement resolution for the character controller. Owns no state — every call takes the current position / velocity / config / state and returns the new position delta plus the updated velocity. Internally uses the `Ground`, `Walls`, and `Ceiling` raycasting helpers. ## Exports - `M.resolve(pos: Vec3, vel: Vec3, moveInput: MoveInput, config: Config, state, dt: number, selfId: string) -> (dx, dy, dz, vx, vy, vz, groundHit, wallHit, ceilHit)` — apply gravity + air control, resolve wall slide / corner pin / ceiling bonk / ground snap / slope projection / steep-slope slide / step climbing in that order. Types: - `Vec3 = { x: number, y: number, z: number }` - `MoveInput = { x: number, z: number }` — world-space horizontal input. - `Config = { height?, radius?, maxSlopeAngle?, stepHeight?, gravity?, airControlFactor?, groundSnapDistance?, skinWidth? }` ## Usage ```luau local Velocity = require("@builtin::systems.characterController.characterController.movement.velocity") local dx, dy, dz, vx, vy, vz, groundHit, wallHit, ceilHit = Velocity.resolve(pos, vel, moveInput, config, state, dt, selfId) ``` ## Notes - The function is pure: it returns nine values but mutates nothing. The caller is responsible for writing the position delta back via `entity.localPosition.set` and updating its velocity field. - Air control blends horizontal velocity toward the input with `airLerp = min(1, airControlFactor * 10 * dt)`. Grounded mode uses direct assignment for responsive feel. - Ground cast distance is `groundSnapDistance` when grounded and `100` when airborne (so a fast fall doesn't tunnel past the floor). Snap commit threshold is tight (the frame's own vertical travel), so airborne ground hits don't snap unless they are within that travel window. - A grounded frame looks for ground above the feet as well, by the rise its own travel covers on ground of `maxSlopeAngle` — that is the ground a walking character climbs into. The seat takes it up to the rise the surface it found covers over that travel, plus a step; a surface further up stands across the path, and the character keeps the ground it already has. - Steep-slope (above `maxSlopeAngle`) hits set `groundHit._sliding = true` so the state machine treats the frame as `sliding` rather than `grounded`. - A frame whose horizontal movement the wall pass cancels outright — pressed straight into a wall, or wedged where two surfaces meet — sets `wallHit._blocked = true`, so a refused walk reads as refused instead of as a walk that happened to cover no ground. - Step climbing only fires when `state.grounded`, horizontal motion exists, and no wall hit was registered.
▲ 0↑ born
▣
module · born here
❒asset
# walls Wall-detection and slide helpers for the character controller. Runs the horizontal pass of a character's step, sweeps the character's own capsule along the movement direction, puts a body that overlaps a wall back outside it, probes a single height with a horizontal ray, and slides a movement vector along a wall normal. No state. ## Exports - `M.move(x: number, y: number, z: number, dx: number, dz: number, height: number, radius: number, skinWidth: number, maxSlopeAngle: number, selfId: string) -> Step`: the horizontal pass of one step. Puts a body that overlaps a wall back outside it (`pushOut`), then carries it along `(dx, dz)`: the body stops `skinWidth` short of the first wall the step runs into, and the rest of the step slides along that wall and along the next one the slide meets. Returns `{ dx, dz, pushX, pushZ, blocked, hit }`: where the body goes (push included), the push itself, whether the step met a wall and gained no ground towards where it asked to go, and the first wall it met. - `M.pushOut(x: number, y: number, z: number, height: number, radius: number, skinWidth: number, maxSlopeAngle: number, selfId: string) -> (number, number)`: the horizontal push that puts a body overlapping a wall back outside it, `skinWidth` clear of the surface, along the overlap's shortest way out. `0, 0` for a body that overlaps no wall. - `M.castBody(x: number, y: number, z: number, dirX: number, dirZ: number, height: number, radius: number, skinWidth: number, maxSlopeAngle: number, selfId: string, distance: number?) -> hit?`: sweep the capsule spanning the character from the top of the ground band above `(x, y, z)` (its feet) up to `y + height`, reaching `distance + skinWidth` past its own surface (`skinWidth` alone when `distance` is omitted). Returns the wall standing across the path, or `nil` when the path is clear. - `M.castDirection(x: number, y: number, z: number, dirX: number, dirZ: number, radius: number, skinWidth: number, selfId: string) -> hit?` — single horizontal ray of length `radius + skinWidth`, from whichever sample height the caller passes. The ray passes through the colliders the body carries (`selfId` and every entity parented under it). - `M.slideAlongWall(moveX: number, moveZ: number, normalX: number, normalZ: number) -> (number, number)` — strip the component of `move` going into the wall (`v - (v . n) * n`, XZ only). Returns input unchanged when `dot >= 0` or the XZ-normal is effectively zero. ## Usage ```luau local Walls = require("@builtin::systems.characterController.characterController.physics.walls") local step = Walls.move(px, py, pz, vx * dt, vz * dt, 1.8, 0.3, 0.01, 45, selfId) px, pz = px + step.dx, pz + step.dz local hit = Walls.castBody(px, py, pz, dirX, dirZ, 1.8, 0.3, 0.01, 45, selfId) if hit then local slideX, slideZ = Walls.slideAlongWall(dx, dz, hit.normal.x, hit.normal.z) end ``` ## Notes - `move` sweeps the whole step, so however long a frame's step is, the body ends outside every wall it walks at, and the next step it asks for starts clear of them, away from a wall it rests against as much as along it. - A sweep begun inside a wall answers about the overlap in whichever direction it points. `pushOut` measures how deep the overlap goes by sweeping the same body back in from outside the wall, so a body placed inside a wall, or shoved into one, walks again on the next step. - A collider the body carries, on `selfId` or on an entity parented under it (a held prop, a trigger volume that travels with the character), is no wall: `castBody` sweeps through it and `pushOut` pushes nothing out of it, so a character carrying one stands where it is put and walks. - `castBody` sweeps the whole body, so an opening narrower than `2 * radius` stops the character even when nothing stands on the centre line — two cabinets 6 cm apart are a wall, not a doorway. - A contact whose surface faces up or down — the ramps the character walks up, to `maxSlopeAngle`, and anything directly overhead — belongs to the ground and ceiling passes. `castBody` sweeps on past those, so a body on a ramp still reports the wall ahead of it. - `castBody` starts its sweep above the ground band: a cap of `radius` resting on ground of angle `a` reaches `radius * (1 / cos(a) - 1)` below the surface uphill of it, and a sweep begun inside a surface describes the shortest way out of that overlap instead of the surface standing across the path. The band is measured at `maxSlopeAngle`, the steepest ground the character walks, and the ground and step passes own everything under it. - `slideAlongWall` normalises the wall normal in XZ; callers don't need to pre-normalise. The Y component of the normal is ignored because slide-along is a horizontal operation. - The slide helper returns the input movement unchanged whenever the movement isn't pressing into the wall — there's no "stick to wall" behaviour, only "don't pass through".
▲ 0↑ born
▣
module · born here
❒asset
# machine State machine helper for the builtin character controller. Owns the state table shape (grounded / falling / sliding / wall contact / blocked / jump counts / moving-platform tracking) and the timing rules (coyote time, jump buffering, multi-jump cap) that the controller consumes each tick. Pure logic — no engine globals beyond `entity()` for platform position lookups. ## Exports - `M.new() -> State` — allocate a fresh state with default values. - `M.update(state: State, groundHit, wallHit, ceilHit, vel, config, dt, now)` — run ground/wall sensors and update grounding, timing, and moving-platform fields. - `M.shouldJump(state: State, config: Config, now: number) -> boolean` — decide whether a queued jump should fire this tick. - `M.executeJump(state: State, config: Config) -> number` — mutate state for a jump and return the Y velocity to apply. - `M.requestJump(state: State, now: number)` — register a jump press (may be deferred via jump buffer). - `M.clearJumpRequest(state: State)` — drop any pending jump request. Types: - `Vec3 = { x: number, y: number, z: number }` - `RaycastHit = { point?, normal: Vec3, entityId?, _sliding?, _blocked? }` — shape of `Physics.raycast`-style hits the controller produces. - `State = { grounded, falling, sliding, wallContact, blocked, wallNormal, velocity, groundNormal, slopeAngle, jumpCount, timeSinceGrounded, timeSinceWallContact, onMovingPlatform, platformEntity, ...internal timing fields }` - `Config = { maxJumps?, coyoteTime?, jumpBuffer?, jumpForce? }` — character tuning fields read each tick. ## Usage ```luau local State = require("@builtin::systems.characterController.characterController.state.machine") local s = State.new() State.update(s, groundHit, wallHit, ceilHit, vel, config, dt, now) if State.shouldJump(s, config, now) then local jumpY = State.executeJump(s, config) end ``` ## Notes - `update` is destructive — it mutates `state` in place. The state table is the single source of truth; callers should not rebuild it each tick. - The jump-buffer window persists across frames; `shouldJump` consumes it via the `_jumpBufferTime`/`_jumpRequested` pair. - Moving-platform detection relies on the platform entity's `localPosition` — non-entity hits leave `onMovingPlatform = false`. - `blocked` is true on a frame the wall pass left the character with none of the horizontal movement it asked for — `wallHit._blocked`, which `Velocity.resolve` marks. It is what tells a character standing still apart from one whose walk is being refused. - `ceilHit` is accepted for API symmetry but currently unused; future ceiling-bump handling will read it without changing the signature.
▲ 0↑ born
◇
component · born here
❒asset
# WASDInput Action-to-input-bus driver. Reads the `move` axis and `jump` action each frame, remaps `move` to the active viewport camera's forward/right basis (via `camera.main()` + `entity(camId).transform.forward`), and writes the resulting world-space horizontal velocity to a target component's input fields: - `target.inputX`, `target.inputZ` — world-space velocity × speed - `target.inputJump` — boolean, true while the jump action is held Defaults to writing to `CharacterController` on the same entity, but the field names are the contract — any component that exposes `inputX/inputZ/inputJump` is a valid sink (vehicles, hovercraft, custom CCs). ## Why generic Independent of which camera is active and independent of the visual layer: - Works with any camera (third-person, top-down, FPS, fixed, vehicle). - Works with no camera (falls back to world-axis WASD). - Works without `Locomotion` or any animation system — CC moves, visualization is opt-in. - Works without a follow rig — `camera.main()` is the seam, not a specific camera component. ## Public fields | Field | Default | Purpose | |---|---|---| | `speed` | `5.0` | Multiplier on the unit-length input vector | | `targetComponent` | `"CharacterController"` | Component to write `inputX/inputZ/inputJump` onto | A custom control scheme is authored as an inputMap that rebinds the `move` axis and `jump` action — not per-instance key fields on this component. ## Example ```lua -- Player with CC + WASDInput + any camera entity(playerId).component.add("CharacterController") entity(playerId).component.add("WASDInput") -- Active viewport camera (any kind) local cam = entity.spawn("cam", { parent = playerId }) cam.component.add("Camera", { fov = 60, priority = 0 }) cam.component.add("orbital_follow", { follow = playerId }) -- Press W → CC.inputX/inputZ are written camera-relative each frame -- → CC translates the body → MovementState reports velocity → -- (optional) Locomotion rotates the visible mesh + plays anims. ```
▲ 0↑ born
◇
component · born here
❒asset
# MovementState Component that exposes movement state for controller-driven animation and gameplay consumers.
▲ 0↑ born
▣
module · born here
❒asset
# bodyFacing Which way a skinned body bundle visibly faces, measured from its skeleton, and the turn that stands it facing -Z, the forward every entity states. An entity's forward is its local -Z: `transform.forward`, `entity:lookAt`, a `PlayerSpawn`'s heading, `capture`'s local `front` and `Locomotion`'s default `forward` all read it. A body file faces whichever way its art pipeline authored it (+Z for a Synty or Rocketbox FBX, a VRM 1.0 or a Khronos-convention glTF, -Z for a VRM 0.x, sideways or lying down under the nodes of some exports). A body composed under a `front` entity turned by `alignment(front(parts(bundle)))` faces the -Z of `front`'s parent whatever its file did. `Locomotion.forward` is stated in the frame of the child of its entity that it turns, so `front` sits under that child: ``` character (placed, turned by lookAt / a spawn) body (Locomotion turns this one about up) front (alignment(front(parts(bundle)))) <bundle nodes> ``` ```luau local bodyFacing = require("@builtin::modules.bodyFacing") local body = entity.spawn("body", { parent = character.id }) local front = entity.spawn("front", { parent = body.id }) front.localRotation = bodyFacing.alignment(bodyFacing.front(bodyFacing.parts(bundle))) bundle:instantiate(front) ``` The avatar asset type composes every body this way, and `characterController.install` composes the mesh it is given this way under its `character_mesh` child. ## Exports - `parts(body) -> parts?` — what a body bundle is made of: `{ bundle, meshes, rig, unit, up, template }`, the bundle, the skinned meshes its template's SkinnedModels name, the `.rig` of the first, metres per rig unit and the body's vertical in the rig's space. Nil for a body with no skinned mesh or source rig. - `front(parts) -> { x, 0, z }?` — the way the body visibly faces at rest in the frame its bundle is composed into: the rig's facing (the hip line crossed with the stand axis) turned by the rotations of the skinned mesh's record and every record above it, so a Z-up skeleton stood upright by a node is measured as it is drawn. Nil for a body whose rig names no hips, neck and legs. - `frontInTopRecord(parts, front) -> { x, y, z }?` — that front in the frame of the record holding the skinned mesh among the children of the entity the bundle is composed onto, the record a `Locomotion` on that entity turns. - `alignment(front) -> { x, y, z, w }` — the turn about +Y that stands `front` on -Z; the identity for a nil front.
▲ 0↑ born
▣
module · born here
❒asset
# platform The body a character stands on, and how that body moves the character. A character standing on a body that moves or turns (a lift, a moving platform, a turntable, a raft, a ship's deck) is carried with it: the point under its feet goes where the body takes it, and it turns with the body's turn about up. Kinematic bodies a script moves, dynamic bodies the simulation moves and transforms something animates carry it alike. Pure helpers. Poses are read where the frame draws them (`Physics.drawnPose`), so a character carried by them stays in step with the platform on screen at any frame rate and physics tick rate. A ride keeps how fast its body moved the feet on each frame of its last tenth of a second, and of at least its last six frames (`trail`): averaged, that is how fast a kinematic body or an animated transform was carrying the character when it leaves. ## Exports - `M.pose(entityId) -> (x, y, z, rotation)?` — where an entity is drawn this frame and how it is turned, in world space. - `M.hold(entityId, from?, carry?, dt?) -> Ride?` — the body a character stands on with the pose it is drawn at now. Hold it after the character is placed each frame; passing the ride the frame began on (`from`), its `carry` and the frame's `dt` keeps the ride's trail going on the same body. - `M.carry(ride, x, y, z, up, dt?) -> Carry?` — how that body moved the point `(x, y, z)` since the ride was held, and how fast it moves it this frame: `{ entityId, dx, dy, dz, turn, moved, vx, vy, vz }`, `turn` the body's turn about `up` as a quaternion, `v` the simulation's velocity for the body at the point (linear plus spin), or the displacement over `dt` for an entity under no body. nil with no ride or when its body is gone. - `M.velocityAt(ride, carry, dt) -> (vx, vy, vz)` — how fast the body moves the feet: a dynamic body's velocity there this frame, else the velocity averaged over the ride's trail, this frame's `carry` included. What a character keeps as momentum when it leaves the body. - `M.steer(vx, vz, walkX, walkZ, lerp, keptX, keptZ) -> (vx, vz)` — air control for a character carrying the motion it kept from a body it left: the velocity steers toward that motion plus the walk asked for, so with no walk asked it goes on moving with the body it left. - `M.keptPast(keptX, keptZ, vx, vz) -> (keptX, keptZ)` — the part of a kept motion a wall leaves once it cut the step to the velocity `(vx, vz)`: none for a wall met head on, the part along a wall slid along. - `M.drawnRise(hit, up) -> number` — how far along `up` the surface a cast met stands drawn above the point the cast met it at; `Ground.cast` measures the ground's distance to the drawn surface with it. - `M.turned(turn, r) -> Quat` — the rotation `r` turned by `turn` in world space. ## Usage ```luau local Platform = require("@builtin::systems.characterController.characterController.physics.platform") -- each frame, before moving the character local carry = Platform.carry(ride, px, py, pz, up, dt) if carry then px, py, pz = px + carry.dx, py + carry.dy, pz + carry.dz end -- ... walk, cast for ground, place the character ... ride = if grounded then Platform.hold(groundHit.entityId, ride, carry, dt) else nil ```
▲ 0↑ born
◇
component · born here
❒asset
# Camera Manages viewport priority, render-to-texture, and capture. State is stored in the native `Camera` ECS component; the Rust camera system handles render scheduling and render targets. Public fields: `fov`, `near`, `far`, `priority`, `textureHandle` (the guid of the texture the camera renders into; empty = main viewport), `renderLayers` (which render layers this camera draws — a space-separated spec of names, e.g. `"all"`, `"all !ui"`, or `"default sky"`; `ui`/`sky`/`debug`/`EditorUI` are built-in layers), `postProcessing` (whether this camera runs the post-process chain), `debugChannel`, plus the behavior slot below. Methods: `:lookAt(target)` (entity id string OR `{x, y, z}` table), `:render()`, `:capture()`, `:setTargetTexture(tex?)` (a `renderer.texture.create` handle to render into, or nil for the viewport). ```luau entity(id).component.add("Camera", { fov = 90, priority = 10 }) entity(id).component.get("Camera"):capture() ``` The scene's play-mode camera is reached as `layers.active.camera`, a handle that reads and writes the fields above on whichever entity currently carries them. `layers.active.camera.entity` is the entity ref for that camera and `layers.active.camera.entityId` its id string, so a script that needs to attach something to the camera — an `AudioListener`, a child entity — goes through the ref: ```luau local cam = layers.active.camera cam.fov = 70 -- the camera's settings cam.entity.component.add("AudioListener") -- the entity carrying them ``` ## How the camera moves: `behavior` and `follow` A `Camera` does not move itself. `behavior` names a component that does, and setting it attaches that component to this entity. Clearing it detaches whatever was attached. ```luau local cam = entity(id).component.get("Camera") cam.behavior = asset.ref("@builtin::controller.orbital_follow", "component") cam.follow = playerBody ``` The attached behavior is an ordinary component on the camera's entity, so it is tuned the way any component is: read it with `component.get` and set its fields there. A `component.add` of the same type configures the instance the slot attached instead of adding a second one: the values it passes are written onto that instance and its proxy is returned. That add is the form a scene `build.luau` tunes the behavior with, because its values are saved with the scene and the loaded Camera's behavior takes them back. A key the component reads only as it is created (one of its `initKeys`, a private field) refuses the add and names the key. ```luau cam.behavior = asset.ref("@builtin::controller.third_person_follow", "component") local rig = entity(id).component.get("third_person_follow") rig.cameraDistance = 6 -- the same, as an add of the type the slot attached entity(id).component.add("third_person_follow", { cameraDistance = 6 }) ``` `follow` is the standard slot every shipped behavior reads. Set the follow target on the **Camera**, not on the behavior, so swapping behaviors keeps it. A behavior that finds its own `follow` field empty falls back to this one, which is what lets a rig keep tracking the player across a behavior swap. `followResolves` answers whether that slot names an entity that is live — `true` while it names a live one or names nothing at all, `false` once the target is despawned or the id names no entity. A rig whose target does not resolve holds its last pose, and this is the field that tells it from a rig posed correctly on a subject that has not moved. `camera.get` carries the same value beside `follow`, and a write naming an id with no entity behind it draws a warning where it lands. ```luau cam.followResolves -- false once the followed entity is gone tools.use("camera", "get", id).followResolves -- the same answer off the tool ``` The shipped behaviors live under `@builtin::controller.*`: `orbital_follow`, `third_person_follow`, `first_person`, `free`, `orbit`, `chase`, `isometric`, `rts`, `birds_eye`, `side_scroller`, `cinematic`, `menu`. ## Writing your own Any component can be a camera behavior. Write one that moves its own entity and attach it the same way: ```luau cam.behavior = asset.ref("MyChaseCam", "component") ``` `follow` lives on the Camera, so a behavior gets no property notification of its own when the target changes. Declare `onFollowChanged(newFollow, oldFollow)` to be told the moment it does — the Camera calls it on the component it attached, which is what lets a rig re-pose on the new subject at once. A behavior that reads `Camera.follow` on its own schedule declares nothing and is attached the same way. ```luau typed function public:onFollowChanged(newFollow: any, oldFollow: any) -- pose this entity against the new target end ``` To make it appear in the discovery catalog alongside the shipped ones, declare the `cameraBehavior` tag in the component's `.metadata`: ```json { "tags": ["cameraBehavior"] } ``` The tag governs **discovery**, not attachment. A tagged component is listed by `layers.active.camera.behaviors` and is what tooling offers when something asks "which camera behaviors exist"; an untagged component attaches just as well and simply stays out of that list. Tag the ones you want other people (and agents) to find. ```luau for name, ref in pairs(layers.active.camera.behaviors) do print(name, ref.identity) end ``` ## Texture colour space `textureColorSpace = "display"` applies the display transform when rendering into a texture. `"linear"` writes scene-linear values instead. `postProcessing` independently controls the effects chain in either mode. Floating-point targets retain values above one; normalized targets clamp to their representable range. The main viewport uses display encoding.
▲ 0↑ born
◇
component · born here
❒asset
# CharacterController Kinematic mover. Integrates velocity against gravity, walls, ceilings and ground, and writes the result to the entity's position every frame. ## Driving it The character moves on a public input bus: `inputX`, `inputZ` and `inputJump`. Each frame the controller reads the bus, moves on what it found, and then refills it for the next frame. **Only the local player's body answers the player's controls.** The character the local player is bound to (`layers.active.players.localPlayer.avatar`) refills its bus from the `move` axis and the `sprint` / `jump` actions of its input map, so the map drives it whenever nothing else does. Every other character holds no map and refills its bus with no movement: an NPC, a mannequin, a preview or another player's body stands where it is until something writes its bus. The player's spawn binds the body for you; to hand the controls to a character you made, bind it: ```luau layers.active.players.localPlayer.avatar = entity(bodyId) ``` The character takes the map up on the frame after the bind and gives it back when the binding moves to another body. Anything else takes the character over by writing those three fields from its own `update()` — an AI brain, a networked peer, a replay, or gameplay code that wants the character committed during an attack. The write works from **any** `executionOrder`, because the refill happens after the read: whatever is in the bus when the controller next reads it is what the character does. - A writer ahead of the controller (`executionOrder` below `-100`) is acted on the same frame. - A writer behind it is acted on the next frame. - Stop writing, and the character stops one frame later; on the local player's body the map has it back instead. - Pausing gameplay empties the bus, so a character frozen mid-stride stands where it was paused and a writer that had it committed says so again. `inputX` / `inputZ` are a world-space velocity in units per second — the controller applies them as they are, so scale them yourself rather than expecting `moveSpeed` to. `inputJump` asks for one jump and the next update consumes it. A component that walks the character due north, whatever the input map says: ```lua -- Northbound.component/init.luau declare { executionOrder = 50 } -- anywhere works; 50 runs after the controller public = { speed = Field.number(4.0, Sync), } function update(_dt: number) local cc = public.entity.component.get("CharacterController") if cc == nil then return end cc.inputX = 0 cc.inputZ = -public.speed end ``` `WASDInput` is the same pattern shipped as a component: it reads an input map of its own and writes the bus of whatever component `targetComponent` names, which is how a mover that reads no controls of its own gets driven. On a CharacterController — which reads `move`, `sprint` and `jump` from its own `inputMap` — a WASDInput writes the bus every frame at its own `speed`, and that is the speed the character walks at. `CharacterController.install` adds one when `input = true` asks for it. ## The control scheme `inputMap` is the scheme the character answers to. It reads three controls from it, each on its own: - `move` — an axis2, projected against the active viewport camera so "forward" is into the screen. - `sprint` — held, multiplies `moveSpeed` by `sprintMultiplier`. - `jump` — pressed, asks for one jump. A map declaring only some of the three drives the character with those: a scheme with no `sprint` holds one gait, a scheme with no `jump` stays on the ground. The character logs which controls the map left out and names the map, so a game with three verbs ships a three-control scheme. A field naming no map leaves the character answering nothing, and logs that too. **Repointing it on a live character takes on the next frame.** The map the character was holding is stood down — its controls leave the live set and its touch buttons leave the screen — and the map named here is taken up in its place: ```luau entity(bodyId).component.get("CharacterController").inputMap = asset.resolve("mygame.input.run", "inputMap") ``` Assigning the map the character already holds changes nothing, so re-stating the scheme leaves the live set where it is. While gameplay is paused the character holds no map at all (the editor's camera has the controls), and it takes whatever `inputMap` names when play resumes. A character that is not the local player's body holds no map either, and takes whatever `inputMap` names when it is bound as that body. ## Platforms, belts and the contact filter The character meets the surfaces content declares on colliders the way a rigid body does. Its ground, wall and ceiling queries are cast for the character's own entity as their mover (`Physics.raycast(..., { mover = id })` and the same option on the shape casts), so the contact rules the physics step applies to bodies apply to it too: - **One-way platforms.** A collider whose `oneWay` points up holds the character from above only: it jumps up through the platform from below and lands on top of it, and walks through its sides. - **Dropping through.** `Physics.passThrough(character)` drops it through the one-way colliders it stands on (or, with a second argument, only those that entity owns). It falls through under its own gravity and meets each again once it is clear of it. ```luau Physics.passThrough(player) -- drop through what it stands on Physics.passThrough(player, platform) -- drop through this platform alone ``` - **Moving surfaces.** Standing on a collider whose `surfaceVelocity` moves (a conveyor belt, a treadmill, an escalator) carries the character at that velocity on top of its own walk. It keeps the carry as momentum when it jumps or walks off, and air control (`airControlFactor`) takes it back toward the walk it asks for. - **Moving bodies.** Standing on a body that itself moves or turns (a lift, a moving platform, a turntable, a raft, a ship's deck, a train car) carries the character with it: each frame the point under its feet goes where the body took it, and the character turns with the body's turn about up, with its own walk on top. It rises and descends with a lift without leaving the ground, and keeps the body's motion at its feet as momentum when it jumps or walks off. In the air it goes on moving with that motion until it lands, the way a crate thrown off the deck does: air control (`airControlFactor`) steers its walk relative to it, so a jump in place on a moving deck comes down on the spot it left, and a wall it meets in the air stops the part of it the wall is in the way of. A kinematic body a script moves (`localPosition` writes, `Physics.setVelocity`), a dynamic body the simulation moves and a transform something animates all carry it alike. The body is read where the frame draws it (`Physics.drawnPose`), and the character is seated on the ground as drawn, so the two stay in step on screen at any frame rate and physics tick rate. A body a script moves after this component's `update` (an `executionOrder` above -100, or a task) carries the character on the next frame. The momentum a kinematic body or an animated transform leaves the character with is how fast it carried the feet over the last tenth of a second (and at least the last six frames), however the frames fell against the physics ticks, and a body that vanishes from under the character leaves it the same. A character something else moves (a teleport, a respawn, a script writing its position) stands where it was put and rides nothing until it stands on a body again. ```luau local lift = entity.spawn("lift") lift.component.add("BoxCollider", { half = { 1.5, 0.1, 1.5 } }) lift.component.add("Physics", { kind = "kinematic" }) Physics.setVelocity(lift.id, 0, 1, 0) -- the character on it rides up Physics.setAngularVelocity(lift.id, 0, 1, 0) -- and turns with it ``` - **The contact filter.** Give the character a collider with a `contactTag` (a trigger capsule is enough) and `Physics.setContactFilter` answers its pairs: a collider whose tag the filter answers `"ignore"` or `"sensor"` with the character's tag is one the character walks through. ```luau player.component.add("CapsuleCollider", { isTrigger = true, contactTag = "player" }) Physics.setContactFilter("player", "ghostWall", "ignore") ``` ## Other characters Characters meet one another as solid bodies. Every entity carrying a `CharacterController` is an upright capsule of its `radius` and `height` to every other character's wall pass (`physics.characters`), so two characters walking into each other stop a skin apart, a character meeting another off centre slides around it, and `blocked` reads true while a walk presses into another character. The same holds for the local player, an NPC and another player's body. A character is a body while its entity is active and its controller enabled: one set inactive (`entity(id):setActive(false)`) or with its controller disabled (`enabled = false`) lets the others walk through it until it is switched back on. The push rule: - A walk never moves another character. Each peer moves only the characters it owns, against where it sees the others, so two players' bodies meet on both peers' screens. - Two characters that overlap (placed into one another, two spawned at one point, a body the network shows a frame late) move apart at up to 2 m/s each, each taking half of the overlap, and never through a wall. A pair pressed together stands still a skin apart. - A character gives way to no body moving into it: the one walking in is the one stopped, on the peer that moves it, so a player walking into a standing one never drives it along, however late each peer sees the other. - Only bodies sharing some height meet: a character jumping over another passes above it, and one coming down onto another's head is moved off it to the side. Which characters pass through which is the contact filter's to say, by each character's `contactTag` (`"character"` unless content names another): ```luau Physics.setContactFilter("character", "character", "ignore") -- nobody blocks anybody ghost.component.get("CharacterController").contactTag = "ghost" Physics.setContactFilter("ghost", "character", "ignore") -- the ghost walks through people Physics.setContactFilter("redTeam", "redTeam", "ignore") -- teammates pass, foes block ``` ## Triggers, pickups and the bodies it walks into The character holds no rigid body: it states its capsule (`Physics.setWaterVolume`), `height` tall and `radius` round, standing on its feet. That capsule is how the rest of the world meets it: - **Triggers and pickups.** A trigger collider hears the character enter and leave it as it hears a body (`Physics.onTrigger(zone, fn)`, with `other` the character's entity), and a listener on the character (`Physics.onTrigger(character, fn)`) hears every trigger it goes through. Every engine the character exists in hears it, the remote players' bodies included, so a zone counted on each peer counts every player. A trigger on an entity beneath the character (a sensor it carries) rides with it and does not hear it. - **Water.** `Physics.onWater` hears it go in and out of the water and `Physics.immersion` reads how deep it stands. - **Pushing.** A dynamic body the walk runs into is pushed along the walk: the walk stops at it as at a wall, and the body is given the impulse that brings its speed along the walk up to the walk's, with at most `pushForce` newtons (400 by default) behind it. On level ground a body moves once `pushForce` passes its friction coefficient times its weight, so at the default a 5 kg crate goes along at the walk with the character behind it and a 500 kg one stands like a wall. `pushForce = 0` makes every body a wall. - **Bodies moving into it.** A body that moves into the character puts it back outside, as a wall that moved into it does. ```luau local player = layers.active.players.localPlayer.avatar Physics.onTrigger(coin, function(e) if e.kind == "enter" and e.other == player.id then collect(coin) end end) player.component.get("CharacterController").pushForce = 150 -- a weaker shove ``` ## Telemetry These read back what the mover did on the frame just simulated: - `grounded` — standing on ground no steeper than `maxSlopeAngle`. - `falling` — in the air and descending. - `sliding` — on ground too steep to stand on, being carried down it. - `blocked` — the character asked to move horizontally and the wall pass left it with none of that movement: pressed into a wall, or wedged where two surfaces meet. This is what tells a character standing still apart from one whose walk is being refused. - `slopeAngle` — the angle, in degrees, of the ground under it. - `velocityX` / `velocityY` / `velocityZ` / `horizontalSpeed` — its velocity. - `jumpCount` — jumps used since it last landed.
▲ 0↑ born
◇
component · born here
❒asset
# orbital_follow Three-ring orbit camera. Framing is authored as three rings around the follow target — a bottom, a centre and a top, each with a `height` above the target's origin and a `radius` out from its axis. Vertical look slides the camera along the spline through those rings; horizontal look orbits around them. The shape of the orbit is geometry you can see and edit rather than a pair of pitch limits you cannot. Public fields: `follow`, `ringBottom` / `ringCenter` / `ringTop` (each `{ height, radius }`), `verticalAxis` (0 at the bottom ring, 1 at the top), `horizontalAxis` (the world heading the camera looks along, in radians about +Y from world +Z), `radiusScale`, `aimHeight` (the aim point above the target's origin), `damping` (per-axis time constants in seconds of the camera's offset from its subject: they soften a change of framing, a look, a zoom or a pull-in, and the subject's own motion carries the camera at any speed), `cameraRadius` (radius of the pull-in sweep; `0` turns the pull-in off), `cameraIgnore` (entities whose colliders the pull-in passes through), `sensitivity`, `invertY` (off by default: pushing the mouse forward looks UP, drawing the camera toward the bottom ring; on pitches the other way), `zoomSpeed`, `minRadiusScale`, `maxRadiusScale`. The rig owns that heading. Binding a follow target aims it along the subject's facing, so the shot opens from behind whoever the camera is told to follow, and look input turns it from there — the subject's facing is never read again. That is what makes the camera steerable for a character who turns to face where it is walking: hold "forward" and the character walks the line the camera looks down, instead of chasing a heading that moves as it turns. The default rings frame a roughly 1.8 m humanoid standing at its origin: the centre ring sits above head height at the widest radius for a resting shot from behind and slightly above, the bottom ring drops to knee height and pulls in to look up, and the top ring climbs and tightens for a near-overhead look down. Writing any framing field re-poses the rig immediately with damping bypassed, so editing a ring moves the camera to the shot that ring describes. `follow` falls back to the `Camera.follow` slot when it is empty, so a rig selected through `Camera.behavior` tracks whatever that camera already follows. Controls: mouse to orbit and to slide along the rings (play mode requests pointer lock, so no button is held), scroll to scale the ring radii. ```luau local cam = entity(id).component.get("Camera") cam.behavior = asset.ref("@builtin::controller.orbital_follow", "component") entity(id).component.get("controller.orbital_follow").ringCenter = { height = 2.6, radius = 6 } ``` ## The camera pulls in when a collider is in the way Each frame the rig sweeps a sphere of `cameraRadius` from the point it aims at out to where its framing puts the camera, and stands the camera where the sphere first meets a collider. Every collider in the world stops that sweep, whether or not anything draws it: an invisible walk bound (a `BoxCollider` with no `Model`), a trigger volume and a solid wall all pull the camera in alike. The follow subject is the one entity the sweep passes by default. So a camera that snaps in close to the player, or collapses onto it, while nothing visible stands behind the player is meeting a collider nobody can see. Two fields settle it: - `cameraIgnore` lists the entities whose colliders the camera sees through. Name the walk bounds and gameplay volumes there and the sweep passes them as it passes the subject, while walls the player can see still pull the camera in. Each entry is an entity (or its id), and it is the collider's own entity that is listed. - `cameraRadius = 0` turns the pull-in off: the camera stands where its framing puts it, through every collider. ```luau local rig = entity(camId).component.get("controller.orbital_follow") rig.cameraIgnore = { entity.find("NorthBound"), entity.find("SouthBound") } -- or drop the pull-in entirely rig.cameraRadius = 0 ``` ## Attach through `Camera.behavior` The Camera owns the behavior slot, so assigning the rig there is what lets the Camera tell it when `follow` changes. A rig added straight onto the entity with `component.add` still poses, but the Camera does not know about it and a `follow` assigned afterwards will not reach it. ## Player cameras: leave `follow` unset Entering play drops and respawns `PlayerPrototype` subtrees, so the body is recreated with a NEW entity id. A `follow` authored on the rig keeps pointing at the original, which is no longer live, and the camera freezes at its last pose instead of tracking the player. For a player camera, set the target on the **Camera** and leave the rig's own `follow` empty: ```luau entity(rigId).component.get("Camera").follow = body -- PlayerPrototype rebinds this on every spawn ``` `PlayerPrototype` refreshes `Camera.follow` to the live body each time it clones, and the rig reads that slot whenever its own `follow` is empty. Set the rig's `follow` only for a camera that watches a fixed, non-respawning subject.
▲ 0↑ born
▣
module · born here
❒asset
# carry The colliders a character carries: the one on its own entity and the ones on every entity parented under it, such as a held prop, a weapon or a trigger volume that travels with the character. A carried collider moves with the body, so it is never ground the body stands on, a ceiling it bumps, or a wall it walks into. The ground, ceiling and wall passes of the character controller all ask their questions through this module. No state. ## Exports - `M.carriedBy(entityId: string, selfId: string) -> boolean`: whether the collider on `entityId` is one the body `selfId` carries: `selfId` itself or an entity parented under it at any depth. An empty `selfId` carries nothing. - `M.raycast(origin: Vec3, dir: Vec3, maxDist: number, selfId: string) -> hit?`: cast a ray and return the first surface it meets that the body does not carry, passing through every carried collider on the way. Returns the raycast hit table `{ entityId, point, normal, distance, startedInside }` or `nil`. ## Usage ```luau local Carry = require("@builtin::systems.characterController.characterController.physics.carry") -- The ground under a character, whatever it holds at its feet. local hit = Carry.raycast({ x = px, y = py + 0.3, z = pz }, { x = 0, y = -1, z = 0 }, 0.5, selfId) -- A sweep that skips what the body carries. if not Carry.carriedBy(sweepHit.entityId, selfId) then -- a wall end ```
▲ 0↑ born
▣
module · born here
❒asset
# ceiling Single-ray ceiling-detection helper for the character controller. Casts upward from the character's head to detect overhead obstacles (head bonk, low clearance). No state. ## Exports - `M.cast(x: number, y: number, z: number, height: number, skinWidth: number, selfId: string) -> hit?` — cast a ray from `(x, y + height - skinWidth, z)` upward for `skinWidth * 2`. Returns the raycast hit table or `nil`. The ray passes through the colliders the body carries (`selfId` and every entity parented under it), so a prop held overhead is never a ceiling. ## Usage ```luau local Ceiling = require("@builtin::systems.characterController.characterController.physics.ceiling") local hit = Ceiling.cast(px, py, pz, 1.8, 0.01, selfId) if hit then -- head bonk: zero out upward velocity end ``` ## Notes - Pure function — no module state, no side effects beyond the engine raycast itself. - The ray is intentionally short (`skinWidth * 2`) so a head-bonk check only fires when the character is actively pressing up against a ceiling, not when there is ambient overhead geometry far above.
▲ 0↑ born
▣
module · born here
❒asset
# characters The bodies characters meet one another as. A `CharacterController` moves by sweeping its capsule against colliders, and this module stands every other character in those sweeps' way. Every entity carrying a `CharacterController` is an upright capsule standing on its feet, `radius` round and `height` tall, where its entity stands, and the wall pass (`physics.walls`) sweeps against those capsules beside the colliders: a character walking into another stops a skin short of it, slides the rest of its walk around it, and reads `blocked` when the other refuses the walk. ## The push rule - A walk never moves another character. Each character moves itself alone, so the bodies meet the same way on every peer: each peer moves the characters it owns against where it sees the others, a remote player's body among them. - Two characters that overlap (placed into one another, a body the network shows a frame late, two spawned at one point) move apart at no more than the speed the controller gives (`apart`), each taking half the overlap. A pair pressed together rests a skin apart; an overlapped pair comes apart over a few frames without either being thrown, and never through a wall. - A character gives way to no body moving into it. That body is the one to stop, by its own sweep on the peer that moves it, so a player walking into a standing one never drives it along, however late each peer sees the other. - Two characters at the very same point come apart along the frame's X, the one whose entity id sorts first towards +X, which every peer reads alike. - Only bodies that share some height meet: a character jumping over another passes above it, and a character coming down onto another's head is moved off it to the side. ## Who meets whom Each character carries a `contactTag` (`"character"` by default). Two characters whose tags the world's contact filter answers `"ignore"` or `"sensor"` pass through each other: ```luau Physics.setContactFilter("character", "character", "ignore") -- nobody blocks anybody entity(ghostId).component.get("CharacterController").contactTag = "ghost" Physics.setContactFilter("ghost", "character", "ignore") -- the ghost walks through people Physics.setContactFilter("redTeam", "redTeam", "ignore") -- teammates pass, foes block ``` A character never meets itself, a character parented under it, or one it is parented under. A character is a body while its entity is active and its `CharacterController` enabled: one whose entity is set inactive (`entity(id):setActive(false)`) or whose controller is disabled (`controller.enabled = false`) stands in nobody's way until it is switched back on. ## Exports - `M.DEFAULT_TAG`: `"character"`, the tag a character meets others by when content names no other. - `M.passes(tagA: string, tagB: string) -> boolean`: whether the contact filter lets two characters with those tags pass through each other. - `M.near(x, y, z, reach, radius, selfId, frame?) -> { Body }`: the other characters within `reach` of touching the character `selfId`, with their feet, capsule and tag, as one read a step's sweeps share. Every character's body is read from its entity once a frame. - `M.placed(selfId, x, y, z)`: states where a character put its feet once it has moved itself. The bodies are read once a frame; the characters moving after it in the same frame meet it where it now stands. - `M.sweep(near, x, y, z, dirX, dirZ, distance, height, radius, frame?, bottom?) -> hit?`: the first character in `near` the body's sweep along `(dirX, dirZ)` reaches within `distance`, as a hit table `{ entityId, point, normal, distance, startedInside, character = true }`. A character the body overlaps already stands in the way only of a walk further into it. - `M.apart(x, y, z, height, radius, selfId, maxStep, frame?, near?) -> (stepX, stepZ)`: the step across the frame, at most `maxStep` long, that moves the character half of each overlap away from the characters it overlaps. ## Usage ```luau local Characters = require("@builtin::systems.characterController.characterController.physics.characters") local near = Characters.near(px, py, pz, 0.5, 0.3, selfId) local hit = Characters.sweep(near, px, py, pz, 1, 0, 0.5, 1.8, 0.3) if hit then print("walks into", hit.entityId, "after", hit.distance) end ```
▲ 0↑ born
▣
module · born here
❒asset
# ground Ground-probing and slope-math helpers for the character controller. A downward raycast helper plus two pure vector helpers (slope angle, plane projection). No state. ## Exports - `M.cast(x: number, y: number, z: number, skinWidth: number, maxDist: number, selfId: string, riseDist: number?) -> hit?` — cast a ray downward from `(x, y + riseDist + skinWidth, z)`, reaching `maxDist` below the feet. The returned hit's `distance` is adjusted to be relative to the feet, not the ray origin, and is negative for ground standing above them. The ray passes through the colliders the body carries (`selfId` and every entity parented under it), so a prop held at the feet is never the ground. - `M.slopeAngle(nx: number, ny: number, nz: number) -> number` — degrees between the supplied normal and world up. Returns 0 on a zero-length normal. - `M.projectOnSlope(moveX, moveY, moveZ, normalX, normalY, normalZ) -> (number, number, number)` — project a movement vector onto the plane perpendicular to a normal: `v - (v . n) * n`. ## Usage ```luau local Ground = require("@builtin::systems.characterController.characterController.physics.ground") local hit = Ground.cast(px, py, pz, 0.01, 0.2, selfId) if hit then local angle = Ground.slopeAngle(hit.normal.x, hit.normal.y, hit.normal.z) if angle <= 45 then -- walkable end end local px, py, pz = Ground.projectOnSlope(dx, 0, dz, nx, ny, nz) ``` ## Notes - `cast` shifts the origin up by `skinWidth` to avoid starting the ray inside the ground when the character is sitting on a contact, then subtracts `skinWidth` back off `hit.distance` so callers see the true distance from the feet. - `riseDist` raises the origin further, so the ray also covers ground that stands above the feet — the ground a walking character climbs into. A hit up there reports a negative `distance`: how far the character rises to stand on it. - `slopeAngle` clamps `cos(angle)` into `[-1, 1]` before `acos` — callers don't need to normalise the input. - `projectOnSlope` does not normalise the surface normal; callers should pass a unit normal (raycast normals already are).
▲ 0↑ born
▣
module · born here
❒asset
# push How a character moved by casts pushes the dynamic bodies it walks into. The wall pass stops the character at a body as at a wall; this gives the body the push a walker gives it. No state. ## Exports - `M.into(hit, walkX: number, walkZ: number, pushForce: number, dt: number, frame?) -> number` — push the dynamic body the walk met (`hit`, a cast hit naming the collider's entity; `Physics.bodyOf` names the body it rides). Along the way into the surface the walk met, laid flat across the frame, the push brings the body's speed up to the part of the walk going into it and no further, with at most `pushForce * dt` newton-seconds, through the body's centre of mass, so a crate slides along rather than tipping. Returns the impulse given: 0 for a hit on no dynamic body, a walk that does not go into it, or a body already moving away at that speed. ## The model A body moves when the push is more than what holds it: on level ground a box of mass `m` sliding with friction coefficient `mu` needs `mu * m * 9.81` newtons. At the `CharacterController` default of 400 N, a 5 kg crate (about 34 N with the default box friction) and a 40 kg one (about 275 N) are carried along at the walk, the heavier one taking longer to come up to speed, and a 500 kg one (about 3400 N) does not move: the character stands against it as against a wall. ## Usage ```luau local Push = require("@builtin::systems.characterController.characterController.physics.push") local step = Walls.move(px, py, pz, vx * dt, vz * dt, 1.8, 0.3, 0.01, 45, selfId, frame) if step.hit then Push.into(step.hit, vx, vz, 400, dt, frame) end ```
▲ 0↑ born
·
assettype · born here
❒asset
# assetType (asset type) An asset type says what a kind of asset is: the files an asset of the kind is made of, the code that gives it behaviour, the interface a person uses to work with it, and how it is found, pictured and checked. A `<typename>.assetType/` folder declares a type called `<typename>`, and every `<name>.<typename>/` folder is an asset of it. `assetType` is itself a type, so a type is an asset like any other: it is created, versioned, installed and contributed the same way. ## Making a type `asset.create("assetType", "<typename>")` scaffolds a type. The type registers the moment its folder is written, anywhere under `/zero/source/`, and from then on `<name>.<typename>/` folders are its assets. An asset of a type that is not registered yet is not an asset, so make the type first. A type folder is a root: `~.x` in any file inside it names the type's own `x`, wherever the type is installed. Keep the type's whole implementation inside its folder and reach it that way. What a type folder must hold is set by this type's own `type.yaml`, the same way every type's `type.yaml` sets what its assets hold. `asset.validate` on a type reports anything missing, and the scaffold produces a folder that passes. ## What sets your type's schema (`type.yaml`) `type.yaml` is the structural contract every asset of the type is checked against. The keys below are the ones the engine reads; a key not listed here is ignored. | Key | What it controls | |---|---| | `suffix` | The folder suffix of the type's assets. Defaults to `.<typename>`. | | `primary` | The file or files that are the asset's content: what the asset resolves to when it is used. | | `entry_files`, `primary_aliases` | Further files that load as the asset or share its identity. | | `is_container` | Whether the suffix stays in the identities of what the asset holds. | | `is_opaque_walker` | Whether a walk of the tree stops at the asset and registers only its primary. | | `plural_dir`, `classify_exts` | Loose files in a folder of this name, or with these extensions, are assets of the type. | | `is_text_default` | Whether the asset's files are text unless stated otherwise. | | `broadcasts_subassets` | Whether assets nested inside an asset of the type are found by their own short name. | | `root` | `true` makes every asset of the type a root, so `~.x` inside one names that asset's own `x`. | | `contract_ref: { field, category }` | A key of the primary file that names another asset the asset is built on. | | `files: { required, optional }` | The files an asset holds (below). | | `allow_unlisted` | `false` reports every file the type does not declare. | | `aliases_from: [{ file, key }]` | Further names an asset answers to, read from its own files. | | `settings:` | Typed per-asset settings (below). | | `inspector:` | The interface people use for the type and its assets (below). | | `preview:` | How an asset is pictured (below). | | `references:` | Names of other assets the type's files carry (below). | | `indexing:` | What search reads for each asset (below). | | `describe:` | How a missing description is generated (below). | ### The files an asset holds Each entry under `files.required` or `files.optional` is `{ path, kind: file | folder, one_of_group?, content? }`. `*` in a path matches within one segment. Entries that share a `one_of_group` are satisfied by any one of them. `content` lists checks on the file's bytes: | Check | Passes when | |---|---| | `non_empty` | the file has content | | `json_field { key, type?, non_empty?, accept? }` | the JSON holds the key (a dotted path) with that shape | | `yaml_field { key, type?, non_empty?, accept? }` | the same for YAML | | `described { keys?, headings?, message? }` | the file says what the asset is (see "Ask your assets to say what they are") | Each check takes a `message`, which is what the author is told when it fails. ### Settings `settings: { values, schema: { type | instance, export? } }` gives every asset typed settings. `values` names the file an asset's values live in; `schema.type` declares one schema for the whole type, and `schema.instance` names a file each asset declares its own in. `asset.create` writes the resolved values, and a write to the values file reaches `onChange` with what changed. ## The human side (`inspector.luau`) A type is used by people through its Inspector, and without one the type is usable only from code. The Inspector is the type's interface for a person: for a procedural graph it is the graph editor, for a kit it is the tracking view of what the kit holds and what is still missing. Writing it is part of writing the type. `inspector: { type, instance? }` in `type.yaml` names the files. `type` is the interface for the type itself and for its assets; `instance` names a file an asset may ship to add its own. Each returns: ```luau return { sections = { { id = "graph", title = "Graph", build = function(ctx) ... end } }, replace = { contents = { ... } }, -- replace a default section by id order = { "graph", "contents" }, -- section order } ``` `build(ctx)` receives the asset and builds the section. A section's `title`, and the text its rows carry, is a string or an `i18n.text` value read from a catalog (`i18n.text("inspectors.mesh.title")`), which follows the editor's language. `asset.create("assetType", ...)` scaffolds a working `inspector.luau` to start from. `asset.validate` on a type that names no inspector, or names one that does not load, reports it. ## Say what your type is for (`about.yaml`) Every type carries an `about.yaml` that says what the type is for, in three plain-language texts: ```yaml intent: "Sets the typeface of the text in your game: UI, labels, signs and 3D lettering." function: "A font, from a TTF, OTF or WOFF file, made available to all of Zero's text, including 3D text." usage: "You choose it by name for your UI or your text, and the text appears in that typeface." ``` - **`intent`** is what the type is for in someone's game, in the words a game maker uses. Up to 800 bytes. - **`function`** is how it works today: what an asset of it is made of and what the engine does with it. Up to 1500 bytes. - **`usage`** is what a person or an agent does with one. Up to 1200 bytes. Write about the type as a whole, not one asset of it, and say what it does now. Agents read these texts to learn when to reach for the type and how; people searching find the type by them. The scaffold starts each text with `[[describe]]` and a note on what to write; a text that still starts that way counts as not written. `services describe` can write them. They show up in `asset.inspect` as `detail.about`, in `assetTypeRef:getAbout()`, at the end of the type's `types/<typename>` guide, and at the top of the type's Inspector. ## Ask your assets to say what they are A type can require each asset to carry a description: a file, written by the author or generated, saying what the asset is and what it is for. Declare it with a `described` check: ```yaml files: required: - path: "README.md" kind: "file" content: - { check: "described", message: "Say what this widget is for and where it goes." } ``` A file that is missing, empty or still has a line starting with `[[describe]]` fails the check, and so does a YAML file whose named `keys` are missing or over their `max_bytes`, or a Markdown file missing a named heading. `asset.validate` names the asset, and a push that carries it is refused with `message`. `services describe` finds such assets and writes their descriptions. `describe:` steers what is generated: ```yaml describe: guidance: "Say what the widget shows, what input it reacts to, and where it fits in a UI." examples: - "<identity of an asset of this type whose description reads well>" ``` An example is an asset of your type whose description is a true, written one, never a placeholder and never the asset being described; with none, leave `examples` empty. A type whose assets the model cannot perceive (a sound, a motion) says so in `guidance`, and the description is drawn only from what the asset's own files state. Start the file unwritten in your `template/`: a heading and one line starting with `[[describe]]`, never example content, which every new asset would carry verbatim. A type whose assets say what they are through their own content (a mesh, a texture) declares no check. ## The type's code (`behavior.luau`) `behavior.luau` returns one table. These are the keys the engine reads from it; anything else on the table is the type's own. ### What the type's assets can do | Key | Shape | What the engine does with it | |---|---|---| | `ref` | `{ [name] = function(self, ...) }` | Every function becomes a method on every asset of the type: `ref:name(...)`. | | `modules` | `{ [name] = require(".x") }` | Code the type's assets reach with `asset.containing(__FILE__).modules.<name>`. | | `events` | an events schema | Events an asset fires. Readers subscribe through `ref.events.<name>:connect(...)`; the type fires them. | | `refShapes` | `{ [method] = function(self) -> (typeExpr, source?) }` | The result type of a `ref` method for one particular asset (below). | | `namePattern` | a Lua pattern | The names `asset.create` accepts for the type's assets. Default `^[A-Za-z][A-Za-z0-9_]*$`. | | `derive` | `{ output, module, compute, fingerprint, matches?, required?, timeout? }` | A file computed from the asset when it is committed; a `required` one holds the commit until it lands. | Some `ref` names mean the same for every type, and the engine calls them: - **`instantiate(self, target?, opts?) -> (root, idMap)`**: puts the asset in a scene. Defining it is what makes the type scene-instantiable. Its return is a contract (below). - **`inspect(self) -> detail`**: what `asset.inspect` reports for the asset beyond the common record (below). - **`preview(self, opts)`**: renders the asset's picture; it wins over the type's `preview:` recipe. - **`previewMaterial(self) -> { material }`**: the material a `surface` preview paints. - **`saveDefinition(self)`**: writes the asset's in-memory edits back to its files in edit mode. Some names are answered for every asset before the type is asked, so a `ref` entry of the same name is never reached: `getSource`, `getBytes`, `getText`, `exists`, `deps`, `canInstantiate`, `canPreview`, `preview` (which calls yours when you define one), `meta`, `runtime`, `events`, `typeRef`, `modules`, and the residency flags `has_backing_asset`, `has_runtime_changes`, `cpu_resident`, `gpu_resident`. ### When the engine calls the type | Hook | Signature | When it runs | |---|---|---| | `onCreate` | `(name, opts) -> { [path] = contents }` | On `asset.create`. Returns the files of the new asset, laid over the type's `template/`. Annotate `opts`: its type is the schema `asset.create` checks the caller's arguments against. A `""` key writes a single loose file. | | `onReplace` | `(dest, files) -> files` | On an `asset.create` over an asset already at `dest`, after `onCreate`, so what the author added can be carried into the replacement. | | `onRegister` | `(self)` | Once per asset, when it first registers: when the world loads, on a live `asset.create`, and when an asset arrives later (installed, pulled, synced). This is what makes an asset take effect the moment it is written. | | `onChange` | `(ref, change)` | On every write to a file inside an asset of the type. `change` is `{ path, asset, type, kind, origin }`, plus `settings` and `settingsChanged` for a write to the settings values file; `kind` is `edited` or `seeded`, `origin` is `local` or `remote`. Filter on `change.path`. Writes to one asset arrive in order, each after the hook for the one before has finished, and the hook may wait on what it reads. A write the hook makes inside its own asset arrives later like any other, so keep the hook convergent. | | `onDependencyChange` | `(ref, change)` | When a module the asset's code requires is re-run, or a name the asset carries starts resolving. `change.kind` is `dependency`. | | `onDelete` | `(ref)` | When an asset of the type leaves the world: deleted, or the world it is in is swapped away. | | `validate` | `(ref) -> { { code, message, severity?, path? } }` | On `asset.validate`, after the `type.yaml` checks, for the type's own rules. `severity` defaults to `error`. Runs on every push, so a type's rules hold at publish. A hook that fails reports `validate.hook_failed`. | ### Settings hooks | Hook | When it runs | |---|---| | `settingsDefaults(name, opts, asked) -> table` | Once per `asset.create`, for values the schema's defaults do not give. | | `settingsCorrections(values, name, opts) -> (corrections?, reasons?)` | On every settings write. A correction to a field the writer named refuses the write, giving the reason. | | `settingsDerivedDefaults(values, explicit, changed)` | On a settings write, for fields derived from others. | | `normalizeSettings(values, stored?)` | On every read and write, to map an earlier spelling of a field to the current one. | | `settingsHealed(values, stored)` | On a read, to repair stored values. | | `settingsSchemaProblem(schema, ref) -> string?` | When an asset's own schema is read; a returned string refuses the schema. | `creationInputs` (`{ [opt] = true | selectorOpt }`) names `asset.create` options that are inputs to the type rather than settings. ### Reloading An edit to `behavior.luau` reaches existing assets with no restart. ## How an asset is pictured (`preview:`) | `kind` | The picture is | The type provides | |---|---|---| | `instantiate` | the asset placed in the preview studio through its `instantiate` | `ref.instantiate` | | `image` | a file the asset holds, fitted to the frame | `source: { files }`, the candidate files in order | | `surface` | the asset painted on a mesh | `mesh`, and `ref.previewMaterial` | | `custom` | whatever `ref.preview` returns | `ref.preview` | ```yaml preview: kind: surface mesh: sphere ``` `angle: [yaw, pitch]` turns the camera. The studio owns the light, the backdrop and the framing, so an asset pictures the same in every world. A type with no `preview:` that defines `instantiate` still answers `ref:preview()`. A picture is rendered when something asks to view it (the editor showing the asset, `ref:preview()`), when previews are generated on request (`assets.generatePreviews`), and when the asset is staged. An edit alone renders nothing. The picture records what it was made from, so a stale one is told from a current one. ## The names your type's assets hold (`references:`) Where your type's own format or API carries the name of another asset, declare it here: ```yaml references: keys: # a top-level key of the type's files that holds a name, or a table of them - { key: "shader", type: "shader" } args: # an argument of a call, counting from 1 - { call: "g:node", position: 2, type: "procNode" } fields: # a field of the options table a call takes - { call: "fx.beam", field: "material", type: "material" } ``` `type` is the category the name resolves in. `asset.declareReferenceKey`, `asset.declareReferenceArg` and `asset.declareReferenceField` declare the same from a script. ## What search reads (`indexing:`) `indexing:` is how assets are found. Search reaches an asset only through what its type's `indexing:` names, and adds nothing of its own. That includes you: an asset indexed badly is one you cannot find later, when you are making something else and need it. A type whose assets are never looked for says `indexing: none`. ```yaml indexing: data: # text, read from the asset's files - role: identity extractor: verbatim source: { file: "README.md" } - role: interface extractor: symbols source: { files: ["init.luau"] } - role: implementation extractor: verbatim source: { files: ["init.luau"] } content: # the picture - role: identity modality: image source: { file: "preview.png" } facets: # what a query filters and re-ranks by file: ".metadata" rigged: { type: bool, from: { components: { contains: SkinnedModel } } } roughness: { type: number, filter: range, from: { file: "mat.yaml", field: "floats.roughness" } } ``` **Roles.** Each `data` and `content` entry has a `role`, and a query matches in two slots: - **`identity`**: what an asset is. For anything you look at, the picture; for anything else, the text that says what it is. - **`capability`**: what it does and how it is made. `interface` (the signatures or shape a caller uses) and `implementation` (the body) both count as capability, and a type with code usually declares both. Ask what a person would recognise an asset of the type by, and what it does, and point each role at the file that says it. For text, that is the asset's description: the file your template starts with a `[[describe]]` block, which the author writes or `services describe` fills in (see "Ask your assets to say what they are"). **`data`.** `extractor: verbatim` embeds a file's text as it is; `symbols` embeds the declared signatures of code. `source` is `{ file }` or `{ files: [...] }`. Never index a file name (`source: { field: name }`): one or two words carry nothing to match. **`content`.** `modality: image` embeds the picture itself, so a text query matches what the asset looks like. A type whose assets are looked at makes the picture its identity. **`facets`.** What a query narrows and re-ranks the matches by. `file` is embedded whole, so keys nobody declared in it are still found. Each further key is computed for every asset and states a value for every one, including `false`: a file can imply "not rigged" but never say it, and a query separates rigged from unrigged only because the unrigged ones say `rigged: false`. A key is `{ type: bool | number | enum, filter?: range, from }`, where `from` is `{ file, field }` (a field of one of the asset's files, dotted for nesting), `{ metadata: key }`, or `{ components: { contains | any_outside } }` (what the asset's entities carry). ## What blocks a push A push checks every asset it carries against its type. These refuse it: - a required file that is missing, a `content` check that fails, a `described` file not written yet; - an error from the type's `validate`. Unlisted files and warnings do not. A `described` file blocks only a push that changes the asset. When a push is refused, the message names each asset and what it lacks. `world.publishBlockers()` and `zm status` read the same list without pushing. ## Typing a result from the asset (`refShapes`) A `ref` method whose result depends on the asset (one entry per child folder, per row of a config, per control a map declares) can only be annotated as `{ [string]: Thing }`, which accepts any key. `refShapes` states the result for each asset instead: a function returning a Luau type expression for that asset, and the module whose types the expression uses. Read the asset; never run it. ```lua -- inputMap.assetType/behavior.luau M.refShapes = { activate = function(self): (string, string) local names = {} for _, control in ipairs(M.ref.controls(self)) do table.insert(names, control.name .. ": Handle") end if #names == 0 then return "", "" end return "{ " .. table.concat(names, ", ") .. " }", "@builtin::modules.zinput.scheme" end, } ``` With it, `map.jump:onPressed(fn)` is checked and `map.noexisting` is reported. A per-asset type applies where the call site names which asset: a component field whose default names it, or an annotation `AssetRef<"inputMap", "<identity>">`. `asset.resolve(name, category)` carries only the category, and a name computed at runtime carries nothing, so calls on those keep the declared return. The type belongs to the call's result: index it there, or bind what you need from it there, and the names stay checked. `require("@builtin::assetTypes.assetType.shared.refShapes").published()` shows what was published: `categories` (each type's method surface) and `returns` (per-asset results by identity, then method). An identity missing from `returns` was never published. Results are recomputed when an asset is written; at most 64 assets of one type are read. ## Putting an asset in a scene (`ref.instantiate`) A caller writes one piece of code against every instantiable type, so what `instantiate` returns is fixed: ```lua local Instantiable = require("@builtin::assetTypes.assetType.shared.instantiable") M.ref = { instantiate = function(self, target, opts) local root = Instantiable.root(self, target, opts) -- compose the asset under `root`, now return Instantiable.result(self, root, idMap) end, } ``` **In.** `target` is the entity the asset lands under, or onto for a hierarchy type; with none, the type spawns a new root. `position`, `rotation` (three numbers in degrees, or a quaternion), `scale`, `name` and `temporary` mean the same for every type: `Instantiable.root` applies them to a root you make, `Instantiable.place` to one you adopt. Document any options of your own in the hook's `--!arg` docs. **Out.** `(root, idMap)`. `root` is the composed root, live when you return: build synchronously, never defer to a component's `awake`. `idMap` maps each original id to the spawned one, so a component that composes the asset again on every load can pass it back in and keep references into the composition. Every call goes through `Instantiable.result`, which refuses a root that is not live and turns a missing `idMap` into `{}`. ## Inspecting an asset (`ref.inspect`) `asset.inspect(ref)` builds a record every asset shares (`identity`, `name`, `guid`, `source`, `typeName`, `typeDefinitionPath`, `scope`, `origin`, `description`, `tags`), then calls `ref.inspect(self)` for the type's own `detail`: ```lua M.ref = { inspect = function(self) -- read the asset's own files, never runtime state: inspect works on an asset -- that has not been compiled, uploaded or registered return { --[[ what makes this asset what it is ]] } end, } ``` Without it, the record is the shared part alone, and an agent inspecting the asset learns nothing of what it is. A hook that raises leaves `detail` empty and sets `record.warning`. ## Discovery - `asset.list("assetType")`: every registered type. - `asset.inspect("<typename>")`: the type, its README and its `about.yaml` texts. - `asset.resolve("<typename>", "assetType")`: the type itself.
▲ 0↑ born
·
assettype · born here
❒asset
# Component (asset type) A component is a reusable behavior + data unit attached to an entity. The component file declares public fields, methods, and lifecycle callbacks; the engine instantiates one per attachment and drives its hooks every frame. Components are the primary unit of gameplay code — movement, AI, animations, UI panels, network sync, and per-entity state all live here. ## When to use one - You need per-entity state that survives across frames. - You need per-entity behavior driven by engine lifecycle hooks (`start`, `update`, `onDestroy`). - You want to expose configurable fields to designers / `entity.spawn` callers / scenes without code changes. If you need a stateless pure-function library, use a `.module`. If you need to generate content declaratively, use a `.service`; compute work belongs in a `.computeShader`. ## Where it lives - Source: `/zero/source/.../<Name>.component/` - Identity: `<Name>` (the `.component` suffix strips from the identity, but the folder retains the suffix on disk). - Folder shape: - `init.luau` (or `init.lua`) — declares the component. **Required.** - `README.md` — instance-level documentation. **Required.** - `.metadata` — agent-editable tags + free-form fields. **Required.** The structural contract is enforced by `asset.validate` against this type's `type.yaml`. ## How to create one Always start with the scaffold — it guarantees the folder shape matches `type.yaml` from the moment it's on disk: ```luau asset.create("component", "<Name>") -- Creates: /zero/source/<Name>.component/ -- init.luau (canonical declare + public block + hooks stubbed) -- README.md (instance README template) ``` After scaffolding, edit `init.luau` to fill in the actual fields and behaviour. The component registers as soon as the file is written — hot-reload is automatic; no engine restart required. ## How it operates 1. **Registration.** Writing `init.luau` into a `.component/` folder indexes the asset, mints a guid (in the `.meta` sidecar), and surfaces the type to the engine's component registry. Same-frame visible to `entity.component.add`. 2. **Attachment.** `entity(id).component.add(name, data)` (or the batch form `tools.use("entityOps", "addComponents", targets, { [name] = data })`) attaches an instance. The `data` table's fields override the component's declared defaults; omitted fields take the declared default. The `data` values are copied into `public.*` BEFORE `awake()` runs. 3. **Lifecycle.** The hooks run in this order: - `awake()` — same frame as attach, immediately after the data copy. Initialise state, set up native bridges, register with other systems. Other components on the same entity may not have awoken yet. - `start()` — the next frame. Every component on the entity has completed `awake()` by then, so cross-component setup is safe here. - `update(dt)` — same frame as `start()`, then every frame after, for as long as the gameplay clock is running. `fixedUpdate(dt)` runs once per physics step, straight after it, with the step's `dt`, so a frame can run it several times or not at all; `editorUpdate(dt)` runs while the clock is held. Which of them ticks is decided by `engine.mode` AND `engine.paused` together — see **Per-frame hooks and the two axes** below, and `man modes`. - `onDestroy()` — when the component is removed via `component.remove` or when the owning entity is despawned. Release resources, drop native ECS components. For the full list (`onEnable`, `onDisable`, `fixedUpdate`, `editorUpdate`, `onPropertyChanged`, `onAssetReload`, `onModuleReload`, `onBeforeSave`, …) and the timing details, **read `man components` — that is the canonical lifecycle reference. Generic component patterns (declare blocks, public fields, sync, ECS bindings, typed methods) all live there.** 4. **Public surface.** Fields declared in `public` are inspectable, editable in the inspector, and persist with the entity. Methods are declared on that same table with a colon — `typed function public:method(args)` — and every one of them takes the component ref as `self`, so a caller invokes it with a colon too: `entity(id).component.get(name):method(args)`. That is the one calling convention a component ref answers to: the reflection methods `ref:fields()` / `ref:getField(name)` / `ref:setField(name, value)` take the same spelling. A function the chunk declares at file scope (`function helper()`) is the component's own, reachable from its hooks under its bare name; `public` is what the ref carries. 5. **Settings and the Inspector card.** `type.yaml` names the component's settings schema as `settings: { schema: { instance: "init.luau", export: "public" } }`: the `public` table IS the schema, and its values live on each entity the component is on, so `asset.schema(componentRef)` answers the Field descriptors and no values file exists. On an entity the Inspector shows the component as a card whose generic `settings` section edits those fields as typed controls, each edit checked against the schema and written to the live component as one undoable operation. `type.yaml` also names `inspector: { instance: "inspector.luau" }`: a component that ships an `inspector.luau` beside its `init.luau` shapes its card — the file returns `{ sections, replace, order }` (see `assetTypes/README.md`, "`inspector:`"), each section's `build(ctx)` reading `ctx.component` (the live component) and `ctx.selection.id` (the entity). `SceneModule.component/inspector.luau` replaces `settings` with the bound module's declared inputs. 6. **Events.** An `events` block declares typed moments the component fires from inside — `events = { onHit = Event({ dmg = Field.number(0, NoSync) }) }`. The owner fires with `events.onHit:fire({ dmg = 10 })`; outside code subscribes through the proxy's subscribe-only facade, `entity(id).component.get(name).events.onHit:connect(fn)` (`:once` / `:wait` too). Pass `Sync` as the event's second argument to replicate a fire to other peers. Events let one component react to another's moments without polling. Full reference: **`man components`**, Events section. 7. **Hot reload.** Editing `init.luau` reloads the component definition; live instances are reconciled with the new declaration in-place, and each crosses one lifecycle boundary: `onDestroy()` ends the running life, then `awake()` and `start()` construct the one that replaces it, and `update()` resumes on the next frame. `public` and `private` values carry across; module-level `local`s belong to the chunk, so the new life starts with them at their initial values and its `awake`/`start` are what fill them in. Whatever the old life handed elsewhere — a subscription, a shared registration, a spawned entity — is released in `onDestroy`, the call that pairs with the construction about to run. An edit that leaves the source byte-identical crosses no boundary at all. A field carries its value across when something stated it: a key of the `data` table the instance was attached with (a scene record's data is that table), or a write made since. Every other field takes the edited source's declared default, so changing a default reaches every instance that left the field to it. An instance that states its own value for a field whose default the edit changed keeps that value, and the reload logs a `[HotReload]` warning naming the field, the entity, the value kept and both defaults. ## Discovery - `asset.list("component")` — every registered component (engine + world + libraries). - `asset.inspect("<name>")` — identity, scope, public fields, lifecycle methods, source path, and this type README. `detail` carries the component's declared `fields`, `methods`, and `events`, parsed from its source — `tools.use("assets","describe", "<name>")` renders it as markdown, so a component's events are visible without opening its source. - `ls /zero/source/<Name>.component` lists the files the folder holds. - `entity(id).component.list()` — components attached to an entity. ## Per-frame hooks and the two axes `engine.mode` (`"edit"` / `"play"`) and `engine.paused` (the gameplay clock) are independent, and the per-frame hooks read them separately: - `update(dt)` / `fixedUpdate(dt)` tick while **the gameplay clock is running** — whichever mode the engine is in. - `editorUpdate(dt)` ticks while **the clock is held** — because the mode is `edit`, or because play is paused — and also alongside `update` whenever edit is running. Which gives four states, and this table is the contract: | `engine.mode` | `engine.paused` | hooks that tick | |---|---|---| | `edit` | `true` | `editorUpdate` | | `edit` | `false` | `update`, `fixedUpdate`, `editorUpdate` | | `play` | `false` | `update`, `fixedUpdate` | | `play` | `true` | `editorUpdate` | Entering edit sets `paused = true` and entering play sets it back to `false`, so a session that never writes `engine.paused` only ever sees rows 1 and 3 — which is where the shorthand "`update` is the play tick, `editorUpdate` is the edit tick" comes from. It is the two default rows of a four-row table, not the rule. **Row 2 is the one that surprises.** With `engine.paused = false` in edit — set by hand, or by a tool that advances the gameplay clock to sample it, such as a `capture.collage` given a `duration` — `update` and `editorUpdate` both fire, once each, every frame. A component that declares both and routes them to one body therefore runs that body **twice per frame**: ```luau local function drive(dt) ... end function update(dt) drive(dt) end function editorUpdate(dt) drive(dt) end -- twice per frame in row 2 ``` Nothing reports the doubling; it reads as an animation running at twice its intended speed. To get exactly one tick per frame in every row, ask which axis you meant and answer it in the body: ```luau function update(dt) drive(dt) end function editorUpdate(dt) if engine.paused then drive(dt) end end ``` A scene `entrypoint.luau` declaring the same two hook names is dispatched by the scene loader, not by this table: there `update` needs play AND running, `editorUpdate` needs edit, and play-paused ticks neither. Read `man scenes` before carrying a component's rule to an entrypoint. ## Authoring conventions - Annotate public fields with `--!desc` so the inspector + LSP show documentation alongside the field name. - Declare lifecycle hooks (`start`, `update`, `onDestroy`) explicitly rather than relying on engine defaults — readers can see at a glance what runs when. - Keep `update(dt)` cheap — it runs every frame per instance. Move heavy work to `start`, to a `.computeShader`, or behind a job (`man jobs`). - For multi-entity batching, prefer `tools.use("entityOps", "addComponents", targets, components)` over a loop of `entity(id).component.add` — it takes many targets and many components in one call. ## Common pitfalls - **Naming.** The component identity is the folder stem with `.component` stripped (e.g. `<Spinner>.component/` → identity `Spinner`). Don't repeat the suffix in the identity passed to `component.add`. - **`init.lua` vs `init.luau`.** Either is accepted (it's a `one_of_group: "entrypoint"`), but `.luau` is canonical. Mixing both in one folder is invalid. - **`update` in edit mode.** It runs whenever the gameplay clock is running, and entering edit stops that clock — so `update` is idle in a freshly-entered edit session and ticks again the moment anything sets `engine.paused = false`. Use `tools.use("wld", "play")` to test update logic under the mode it ships in; `tools.use("wld", "edit")` to return. See **Per-frame hooks and the two axes** above. - **Renaming.** Renaming the folder changes the identity. References to the component are recorded against the component itself, so renaming or moving it does not break them. ## Related types - `.module` — pure-function library, no per-entity state. - `.service`: a declarative content generator, no per-entity state. - `.preset` — a captured component configuration, replayable into `component.add` without re-typing fields. - `.bundle` — entity hierarchies that may carry component attachments as part of the bundle. ## In the Inspector Fields: its execution order, hooks, and how many methods and events it declares, then the fields its `public` table declares as read-only typed controls holding their defaults, with **Check** and **Open** for its entry file. Instances: a link to every entity carrying it. What its card shows on an entity comes from the component's own `inspector.luau`.
▲ 0↑ born
❒
package · born here
❒asset
▲ 0↑ born
▣
module · born here
❒asset
# defaults The Preset Manager: the world's ordered `[[presets]]` rows in `/zero/source/.world_settings`. A row names one declarer (`target`), one preset for that declarer (`preset`) and a path glob (`filter`). When something a declarer governs is created — an asset of an assetType, an import an importer runs, a component added to an entity — the first row naming that declarer whose filter matches the new thing's path gives a layer of its settings. Rows are read only at creation. A component row's filter reads the entity's hierarchy path (names from the root down, joined with `/`). What a scene build's capture scope adds takes the rows in any mode, whoever runs the build; outside a build, a component takes a row when it is added in edit mode. A component put back from existing content takes none: one added inside `materializing` (a saved scene, a peer's record, a template clone, a bundle's hierarchy, a build's records), and one a component's own code adds outside a build, on any coroutine that code runs. A scene build records which fields the rows gave each component, and a rebuild restates a component only when the code states it differently, so a row edit alone changes nothing a build already placed. Rows are written as guid envelopes and checked as a whole. A row is refused when its target does not resolve, is consulted at no creation, or declares no settings; when its preset does not resolve, is not a preset, or targets another declarer; or when its filter is not a string. A write replaces the `[[presets]]` block and keeps the rest of the file byte for byte. ## The row format ```toml [[presets]] target = { __ref = "8cc28fc8-ed63-48ee-83a6-15f4192e27e1", type = "importer", name = "texture" } preset = { __ref = "0b6c1f0e-5d0c-4d5e-9d64-3c1b7f2a9e11", type = "preset", name = "pixel_art" } filter = "sprites/**" ``` `target` and `preset` are guid envelopes: `__ref` is the guid, and `type` and `name` tell a person reading the file what it names. A row written by hand may name either by identity or guid; the next write rewrites it as envelopes. `.world_settings`'s `.refs` pins each row's target and preset by guid. ## Matching For a new thing a declarer governs, the rows are read in order and the first naming that declarer whose filter matches the thing's path applies; the rest are not consulted. A filter is a glob (`preset.glob`) over the path relative to `/source` with forward slashes, or an entity's hierarchy path for a component row; the empty filter matches everything, and a filter that is not a string matches nothing. A matching row whose preset does not resolve, or targets another declarer, is the match and contributes nothing, with one warning. A preset value the declarer's schema rejects is left out and the rest apply. ## Sync The rows are part of `.world_settings`, so they sync with the world like any other file and every peer reads the same rows. A row applies where the creation happens, when it happens: a peer's edit reaches only what is created after it arrives, and what was created before keeps the settings it was stamped with. A runtime asset lives for the engine process; a peer that started before a row edit keeps its old settings on a re-created runtime identity until it restarts. ## Exports - `Defaults.PATH`, `Defaults.BLOCK` — the file and the array-of-tables name. - `Defaults.SCHEMA` — the block's Field schema, `{ presets = Field.list(row) }`. - `Defaults.rows() -> { Row }` — every row, resolved, with its problems. - `Defaults.write(rows)` — normalise, check, and replace the rows. - `Defaults.normalize(input) -> StoredRow` - `Defaults.rowProblems(row) -> (problems, targetRef, presetRef)` - `Defaults.consultedAt(declarer) -> "asset.create" | "import" | "component.add" | nil` - `Defaults.relativePathOf(path) -> string?` — the path a filter reads. - `Defaults.match(declarerGuid, relPath) -> (Row?, index?)` - `Defaults.layerFor(declarerGuid, relPath) -> (values?, Match?)` - `Defaults.check(value, constraint) -> (ok, reason)` — the `presetDefaultRow` constraint. - `Defaults.removeAt(index)` — remove one row, writing every other row back as the file holds it. - `Defaults.importerSettings(importerRef, sourcePath) -> (settings, Match?)` - `Defaults.materializing(fn, ...) -> ...` — run `fn` with no row reaching a component add. - `Defaults.entityPath(id) -> string` — the hierarchy path a component row's filter reads. - `Defaults.forComponent(entityId, typeName, data?) -> data?` — the data a component add takes. - `Defaults.batchLayers(targets, typeName, data?) -> { { targets, data } }` — a batch add split into runs. - `Defaults.resolveValue(v) -> AssetRef?` — a row value as the asset it names. - `Defaults.recordingStamps(fn, ...) -> (stamps, ...)` — run `fn` and return what the rows gave the components a capture scope added meanwhile, per `stampKey`. - `Defaults.stampKey(entityId, componentGuid, instanceName?) -> string` The `preset` global exposes the rows as `preset.defaults`, `preset.setDefaults`, `preset.addDefault`, `preset.removeDefault` and `preset.defaultFor`.
▲ 0↑ born
▣
module · born here
❒asset
# document A preset's `preset.yaml`: decoding it, reading it and writing it. The typed form names the declarer the values are for and the values: ```yaml target: { __ref: "<guid>", type: assetType, name: texture } values: filter: nearest ``` `target` is written as a guid envelope, which the preset's `.refs` pins by guid; `type` and the target's plain `name` say what it points at to a person reading the file, and `name` is never an identity, so the guid is the one link. A `target` written as an identity string (`"@builtin::assetTypes.texture"`, or a world asset's identity) is accepted on read. The component-only form, `component:` + `properties:`, reads as authored. ## Exports - `Document.pathOf(ref) -> string` - `Document.decode(body: string) -> Doc` - `Document.read(ref) -> Doc` - `Document.encode(envelope: Envelope, values) -> string` - `Document.write(ref, envelope: Envelope, values)` Types: - `Envelope = { __ref: string, type: string?, name: string? }` - `Doc = { format: "typed" | "legacy", target: string?, envelope: Envelope?, component: string?, title: string?, values: { [string]: any } }` ## Usage ```luau local Document = require("@builtin::modules.preset.document") local doc = Document.read(presetRef) ```
▲ 0↑ born
▣
module · born here
❒asset
# glob Path globs for Preset Manager rows. A row's `filter` is matched against the path of the new thing it would apply to. - `*` matches any run of characters inside one path segment. - `**` matches any run of characters across segments. - `**/` matches zero or more whole segments, so `a/**/b` matches `a/b`. - `?` matches one character other than `/`. - Every other character matches itself. A glob matches a whole path, anchored at both ends. The empty glob matches every path. ## Exports - `Glob.match(glob: string, path: string) -> boolean`
▲ 0↑ born
▣
module · born here
❒asset
# heal Rewrites a preset's `preset.yaml` into the form presets are written in, on a local edit of this world's own content: a target written as an identity string that resolves becomes the guid envelope, and a component-only document whose component accepts every property it holds becomes the typed form, its target the component and its legacy `name` moved to the `.metadata` `title`. Every value is kept as decoded. A remote-origin edit and library-installed content are left as they are. A component-only document that cannot heal stays as it is, and the reason is warned once. ## Exports - `Heal.ifNeeded(ref, origin: string?) -> boolean` — true when the document was rewritten. - `Heal.writeTyped(ref, doc, declarer, values)` — write `values` in the typed form targeting `declarer`, moving a component-only document's `name` to the `.metadata` `title`. `preset.setValues` writes through it too. - `Heal.forget(ref)` — drop what the module remembers about a removed preset. ## Usage ```luau local Heal = require("@builtin::modules.preset.heal") Heal.ifNeeded(presetRef, change.origin) ```
▲ 0↑ born
▣
module · born here
❒asset
# target The declarer a preset's values are for: resolved by the guid its target envelope names (pinned in the preset's `.refs`) or by the identity string a hand-written target names, checked against that declarer's current schema, and compared with the checksum the pin recorded. ## Exports - `Target.literalFor(ref) -> string` — the guid a preset pins for `ref`. - `Target.describe(ref) -> string` — `ref`'s identity. - `Target.envelopeFor(ref) -> Envelope` — `{ __ref, type, name }` for `ref`. - `Target.resolve(presetRef, doc) -> Resolved` - `Target.resolveLiteral(literal: string) -> Resolved` - `Target.declarerOfAsset(ref) -> (declarer, schema)` - `Target.isComponentTarget(v) -> boolean` — true for `{ entity = <id>, component = <name> }`. - `Target.declarerOfComponent(t) -> (component, schema, proxy)` — the component asset governing a component on an entity, its schema, and the live component. - `Target.check(schema, values) -> (valid, rejected)` - `Target.valuesOf(presetRef, doc) -> (values, report, resolved?)` — what `preset.values` answers, from a document already read. - `Target.merge(schema, current, patch) -> values` - `Target.refuse(prefix: string, violations)` — raises. Types: - `Resolved = { literal: string, name: string, ref: any?, guid: string?, schema: any?, pinned: boolean, changed: boolean }` - `Violation = { path: string, message: string }` - `Report = { format, target, targetGuid?, pinned, targetChanged, rejected }` ## Usage ```luau local Target = require("@builtin::modules.preset.target") local declarer, schema = Target.declarerOfAsset(texRef) ```
▲ 0↑ born
▣
module · born here
❒asset
# luau_introspect (module) Parses Luau/asset source TEXT into structured declarations. Pure string/pattern parsing (`string.find` / `string.match` / `string.gmatch`) over the literal source — no compiling, no VM spawn, no runtime state, no engine FFI. Given source text, it extracts what is written in the file. This is the shared parser every per-assetType `M.ref.inspect` hook uses to turn a component/module/tool's own source into the structured record `asset.inspect` returns. ## Exports - `docstrings(src) -> DocMap` — scans `--!desc` / `--!arg` / `--!return` / `--!example` comment runs and binds each run to the name of the declaration on the next non-comment line (the identifier after `function`, `public:`, `local function`, or `M.`). - `publicFields(src) -> { FieldEntry }` — parses `public = { name = Field.<kind>(default, mode), ... }` table-literal entries and module-scope `public.<name> = Field.<kind>(...)` assignments. - `events(src) -> { EventEntry }` — parses `events = { name = Event(payloadSchema?, syncMode?), ... }` table-literal entries. - `methods(src) -> { MethodEntry }` — parses `function public:<name>(...)` / `typed function public:<name>(...)` declarations (params + optional return type). - `lifecycleHooks(src, catalog) -> { string }` — top-level `function <name>(` declarations whose name is in the caller-supplied `catalog` array. - `moduleExports(src) -> { ExportEntry }` — parses `M.<name> = function` assignments, `function M.<name>(...)` declarations, and a trailing `return { foo = foo, ... }` export table. - `forSource(src, computeFn) -> any` — memoises `computeFn(src)` keyed on `src` itself in a module-local table. The same source text returns the cached result without re-running `computeFn`; different source text recomputes. Keyed on the source content (not an asset checksum) because composite/container assets (component folders, scene folders, etc.) all hash to the empty-string checksum — a checksum-keyed cache collapses every such asset's detail onto whichever one was inspected first. ## Usage ```luau local Introspect = require("modules.luau_introspect") local src = self:getInitScript() local detail = Introspect.forSource(src, function(s) return { fields = Introspect.publicFields(s), events = Introspect.events(s), methods = Introspect.methods(s), hooks = Introspect.lifecycleHooks(s, lifecycleCatalog), } end) ``` ## Notes - Every function is a pure string→table transform: same source text in, same structured table out, every time. No reads of live component state, no entity/world queries. - Structural scanning runs over a comment- and string-aware **mask** of the source (a same-length copy where comment bodies and string-literal contents are blanked to spaces, delimiters and newlines preserved). Pattern matches and brace/paren balancing run on the mask — so a brace, `Field.`, `Event(`, or a whole entry that appears inside a comment or a string literal never registers — while captured values are sliced from the original source at the same (aligned) indices. This makes the parser robust to apostrophes in comments, commented-out entries, string defaults containing `}` / `Field.` / `Event(`, and `[[ ]]` long strings. - `default` / `category` are raw trimmed source-text slices (with any trailing comment stripped), not evaluated values. - For a **ref constructor** (`Field.assetRef` / `dataRef` / `resource` / `componentRef`) the FIRST positional argument is the category / contract / componentType selector, captured under `category`; the SECOND argument is captured under `default`. - For every **other** Field kind the first argument is the `default` and `category` is nil. - A trailing `Sync` / `NoSync` identifier is captured as `sync`, tolerating a trailing comma or a trailing comment after the last argument. - Field/Event entries whose key is a computed or indirect expression (`[expr] = Field.number(...)`) are omitted — only literal identifier keys are recognised. - `methods` captures a `...` variadic parameter (as `name = "..."`), with its `: <type>` annotation when present. - A `--!desc` written above a field/event declaration (`<name> = Field.<kind>(...)` / `<name> = Event(...)`) or a `public.<name> =` assignment binds to that name in `docstrings`, and is folded into the corresponding `publicFields` / `events` entry's `desc`. - `lifecycleHooks` never hardcodes the lifecycle-callback catalog; the caller passes the list of names to match against. - `forSource`'s memo is bounded (oldest-key eviction) so a long session touching many distinct asset versions can't grow it without limit.
▲ 0↑ born
▣
module · born here
❒asset
# assetType.shared.ref Builds the metatable every `AssetRef` (the `{ __ref, type, name, guid, identity, path }` envelope returned by `asset.resolve` / `asset.ref`) carries. Replaces the per-call C metatable that used to live in `crates/zero_scripting/src/ffi/bindings/asset.rs::attach_asset_ref_metatable`. ## Public API ```lua local assetRef = require("@builtin::assetTypes.assetType.shared.ref") -- Called by the Rust factory (push_asset_ref_handle) via -- _G.__build_asset_ref_proxy after the envelope fields are set. assetRef.build(envelope) -- attaches AssetRefMT, returns the table ``` The module exposes no invalidation surface — discovery is registry-driven and hot-reload is transparent (see "Discovery and hot-reload" below). ## Method dispatch order `ref.foo` is resolved in this order: 1. **Default methods** — `getSource` / `getBytes` / `getText` / `exists` / `inspect` and the lazy `meta` property. Per-type definitions cannot override these (engine contract from gh#1889). 2. **Per-type `ref` table** — discovered through `asset.resolve(<typename>, "assetType")` + `require(<identity>.behavior)`. The lookup resolves to whichever `<typename>.assetType/` folder is currently registered for the typename (built-in, user, or library-vendored) and pulls its `ref` methods. 3. **Nil** — unknown key, same shape as the original C metatable. ## Adding methods for a new asset type Drop a `behavior.luau` into the type folder: ``` src/lua/lib/assetTypes/<typename>.assetType/ ├── type.yaml -- structural spec (existing) ├── behavior.luau -- ref + global behaviour (new) └── template/ -- placeholder body (existing) ``` `behavior.luau` returns: ```lua return { ref = { --!desc Per-instance method on every `<typename>` AssetRef. myMethod = function(self, ...) ... end, }, global = { -- Reserved for the asset.<typename>.* surface — not consumed -- yet; included so the contract from gh#1889 lands cleanly. }, } ``` Within `ref` methods, `self` is the AssetRef envelope: `self.path`, `self.identity`, `self.guid`, `self.type`, `self.name` are available. Engine-required fields (`guid`, `path`, `identity`, `type`) must not be redefined. ## Discovery and hot-reload Type discovery uses the asset registry, so it doesn't matter where a `<typename>.assetType/` folder lives — engine built-ins under `@builtin::assetTypes.<X>`, user types dropped under `/zero/source/<X>.assetType/`, or types vendored inside an imported library all resolve identically. The dispatcher walks `asset.resolve(<typename>, "assetType")` → canonical identity → `require <identity>.behavior` on every miss; the asset registry is the cache for the resolve half and Luau's `_LOADED` is the cache for the require half. Hot-reload is transparent. When a `<typename>.assetType/behavior.luau` is rewritten through VFS, the engine's `invalidate_require_cache_for_state` re-runs the module and mutates the cached `_LOADED[<identity>.behavior]` table in place. Dispatch reads `mod.ref` on every access (rather than caching a sub-pointer), so existing AssetRefs see the new methods on the very next access — no Rust-side hook into this module is needed, and no invalidation API is exposed for callers to call. The same registry-driven path also handles type **registration** correctness: dropping a new `<typename>.assetType/behavior.luau` updates the asset registry, the next `asset.resolve(<typename>, "assetType")` returns the new ref, and AssetRefs of that type immediately gain the new methods. ## Why Luau, not Rust The asset surface needed per-category behaviour (`material:getProperties()`, `bundle:instantiate(entityId)`, `tool:run(args)`) and the old shape couldn't grow without an FFI change per method. Owning the proxy in Luau means: - Type-specific methods ship as content (the `<typename>.assetType/` folder), not engine code. - Adding a new asset type drops in a new folder; no Rust rebuild. - Methods can call any other Luau global (`vfs`, `asset`, `Material`, `entity`, etc.) directly, instead of going through narrow FFI primitives. ## Consumers - `crates/zero_scripting/src/ffi/bindings/asset.rs::attach_asset_ref_metatable` — the Rust factory that pushes envelopes invokes `_G.__build_asset_ref_proxy` once per push. - Every Luau call site of `asset.resolve` / `asset.ref` / `entity(id).component.X.material` / any binding declared `AssetRef<...>` — they all receive envelopes built through this module.
▲ 0↑ born
▣
module · born here
❒asset
# yaml.module YAML decode + encode for authored engine content. Pure Luau, no engine dependencies — a general parsing library, not data-system plumbing. ```luau local Yaml = require("@builtin::modules.yaml") local doc = Yaml.decode(vfs.read(path)) vfs.write(path, Yaml.encode(doc)) ``` ## Supported subset - Block mappings (`key: value`) and block sequences (`- item`), nested to any depth. - Compact sequence-of-mapping entries (`- path: x` / ` kind: y`). - Flow collections — `{ a: 1, b: 2 }` and `[1, 2, 3]` — single line. - Plain scalars with type inference: `~` / `null` → nil, `true` / `false` → boolean, numeric literals → number, everything else → string. - Single- and double-quoted strings (`''` escapes a literal quote inside a single-quoted string; `\n` `\t` `\r` `\\` `\"` inside a double-quoted one). A quote opens a quoted scalar where a scalar begins — after `key:`, after a `- ` entry marker, or inside a flow collection — so a plain scalar carries an apostrophe as data (`note: the world's rules`). Quoted keys are read in flow mappings. - `#` comments — honored outside quotes, so a `#` inside a quoted string is kept as data. - Literal (`|`) and folded (`>`) block scalars, with a chomping indicator (`-` strips the final newline, `+` keeps every trailing blank line, none keeps one newline) and an indentation indicator (`1`-`9`: the content's indent past the parent's), in either order (`|-`, `>+`, `|2`, `>1-`). A block scalar's content is literal text: quotes (balanced or not), `#`, `key: value` and `---` inside it are data. - An optional leading `---` document marker. ## Loud-error contract Constructs outside the subset above raise instead of misparsing: anchors/aliases (`&`, `*`), tags (`!`), directives (`%`), multi-document streams (a second `---`), a block-scalar header it cannot read (`|x`, `|-+`, `|0`), tab indentation, and inconsistent indentation (both block structure and block-scalar bodies). Every error carries the offending line number (`yaml: line N: ...`), so a bad config points straight at the line to fix. Tab indentation is rejected everywhere — including block-scalar body lines whose leading whitespace contains a tab. A tab after the first non-space character of a line is content and passes through. ## API - `Yaml.decode(text: string): any` — decode a YAML document into a Luau value (table, scalar, or nil for an empty document). Raises on malformed input or an unsupported construct. - `Yaml.decodeWithComments(text: string): (any, boolean)` — decode as `decode` does, and report whether the text carries a comment by the decoder's own rule: a `#` at a line's start or after whitespace, outside a quoted scalar and outside a block scalar. Re-encoding the value drops such comments, so an editor that writes a document back reads this first. - `Yaml.encode(value: table): string` — encode a Luau table as YAML (block style, two-space indent, alphabetically sorted keys). Raises on values YAML can't represent (functions, userdata, non-string mapping keys). A top-level empty table encodes to an empty document, which decodes back to `nil` (the YAML empty-document ambiguity).
▲ 0↑ born
▣
module · born here
❒asset
# json JSON encode/decode library for Luau. Encodes Lua values to JSON strings and decodes JSON strings back to Lua values. Used for communication with the Rust side of the engine, the VFS read/write bridge, and any wire-format that needs JSON. Pure Luau, no engine dependencies. Compact and pretty-printed encoders, plus a hand-rolled decoder that streams the input by position so it works under WASM as well as native. ## Exports - `Json.encode(value: any, indent?: string, currentIndent?: string) -> string` — compact encode. Functions / unknown types and NaN/Inf encode as `null`. - `Json.encodePretty(value: any, indentStr?: string) -> string` — pretty-printed encode with sorted object keys (diff-friendly). - `Json.encodeArgs(...: any) -> string` — encode varargs as a JSON array. - `Json.decode(str: string) -> any` — decode a JSON string. Returns the decoded value, or `nil` + error message on failure. ## Usage ```luau local Json = require("@builtin::modules.json") local widget = { type = "button", text = "Click Me" } local compact = Json.encode(widget) -- '{"text":"Click Me","type":"button"}' local pretty = Json.encodePretty(widget, " ") local decoded = Json.decode(compact) local v, err = Json.decode("oops") -- v = nil, err = error message ``` ## Notes - Object keys are sorted alphabetically in both encoders for consistent output across runs. - Numeric keys on objects are stringified at encode time (JSON has no numeric keys). Pure-integer key sets get detected as arrays via `isArray` and encoded with brackets. - NaN, +Inf, -Inf encode as `null` — JSON has no representation. Round trips through `decode` recover `null` (Lua `nil`), so they don't preserve. - Unicode `\uXXXX` escapes decode to UTF-8 by hand to stay WASM-safe. Only the BMP is covered; supplementary planes via surrogate pairs are not. - Functions encode as `null`. - Decode is character-streamed — no regex, no `string.match` patterns on the whole input — so the line-and-column information needs to be reconstructed from the position offset.
▲ 0↑ born
▣
module · born here
❒asset
# assetType runtime The machinery that reads a `<typename>.assetType/behavior.luau` and turns its declarations into live behaviour. A `behavior.luau` is a table of declarations — `ref` methods, `modules` shared code, an `events` schema, a `namePattern`, `refShapes`, and the `onCreate` / `onRegister` / `onChange` / `onDelete` / `validate` / `settingsDefaults` / `settingsCorrections` hooks. None of it runs itself. This is the code that runs it, and it lives here because reading a type's declarations is the **assetType type's own behaviour** — the same way `material.assetType` owns what a `.material` does. ## Sub-modules | Module | Reads | Responsibility | |---|---|---| | `ref.module` | `ref`, `modules` | Builds every `AssetRef` envelope, attaches the shared metatable, and dispatches per-type methods and shared modules onto it. Also owns edit-mode write-behind persistence. | | `create.module` | `onCreate`, `namePattern`, `validate` | Backs `asset.create`: resolves the type, checks the name against its pattern, runs `onCreate` (or clones `template/`), and writes the instance. `validate.module` beside it checks a creation `opts` table against the type's `createSchema`. Before running `onCreate`, resolves the type's settings chain (below) and hands the result to the hook as `opts.settings`. | | `settings.module` | `settings`, `settingsDefaults`, `settingsCorrections` | A type's declared settings schema and where its values live (`type.yaml`'s `settings:` block). `Settings.resolveForCreate` layers the schema's own defaults, the type's own `settingsDefaults(name, opts, asked)` hook (a DEFAULT the schema can't express — a name-derived convention, a fact read off a payload the caller handed it, a value following a field `asked` shows a higher layer naming; any later layer overrides it), the Preset Manager, an importer's settings, the caller's `settings` table, then the type's own `settingsCorrections(values, name, opts)` hook (a CROSS-FIELD CONSTRAINT the schema can't express, applied last over the fully merged values). A correction over a default/preset/importer value lands silently; a correction that would override what the caller's own `settings` table explicitly asked for refuses the creation instead, naming the field and why. Neither hook is ever handed a table to mutate; each returns what it wants changed (`settingsCorrections` may also return a `{ [field]: reason }` table for that refusal message). `Settings.cloneValues` deep-copies a values table — `create.module` hands `onCreate` a copy, never the table it stamps. `Settings.valuesOf` / `writeValues` read and write an asset's own values file. | | `typeYaml.module` | `type.yaml` | The folder a type lives in and its parsed `type.yaml`, decoded once per content version of the file. `settings.module` and `inspector.module` read their blocks through it. `about` / `aboutAt` read a type's `about.yaml` (`intent`, `function`, `usage`), leaving out any key that is empty or still starts with `[[describe]]`; `aboutRows` and `aboutMarkdown` lay the texts out for the Inspector and the `types/<name>` guide. | | `inspector.module` | `type.yaml`'s `inspector:` block | Which inspector a type declares for its assets (`inspector: { type: ... }` or `{ instance: ... }`), and the declaration that file returns — the sections it adds, the generic ones it replaces, and their order — or the problem that kept it from loading. | | `onRegister.module` | `onRegister` | Fires an instance's once-only registration hook — on arrival, on world load, and for `@builtin` library instances. | | `changeDispatch.module` | `onChange`, `onDelete`, `refShapes` | Routes a VFS source write or a folder delete to the enclosing typed asset's type hooks. | | `refShapes.module` | `refShapes`, `ref` | Publishes what every `AssetRef<category>` answers to, so a member read on an asset-typed value is checked against that category's real surface. | | `events.module` | `events` | The per-asset event runtime behind `ref.events`. | | `instantiable.module` | `ref.instantiate` | The instantiation contract an asset type opts into: `root` stands the root entity, `place` applies the base placement opts to one the type adopted, and `result` shapes the `(root, idMap)` every `instantiate` returns. Also registers the `sceneInstantiable` field-constraint validator. | | `declaration.module` | `type.yaml` | The type's decoded declaration, read once and held until a write inside an `.assetType` folder; what every question about a type as a whole reads. | | `previewRecipe.module` | `type.yaml` `preview:` | How an instance's `preview.png` is produced: which of the four recipes (`instantiate`, `image`, `surface`, `custom`) the type declares, and what that recipe needs. | ## Reaching it ```luau local rt = require("@builtin::assetTypes.assetType.shared") rt.ref.loadTypeBehavior("material") ``` Fields resolve lazily. The prelude requires the sub-modules directly, in dependency order (`ref`, then `changeDispatch`, `onRegister.install()`, `refShapes.install()`) — a table that required all six on load would take that ordering away from it.
▲ 0↑ born
backing path · systems/characterController.package/characterController.module

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

0problems
No problems reported on this asset or on the parts this page shows. Parts it leaves out are not counted here.
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up agent_score is exposed.
usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor

Usability ratings

Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".

—%no reports yet
Sign in to report whether this part worked for you.
Discussion

Scoped to this part · feeds back into the world's score.

0comments
Sign in to post.sign in
No comments yet. Be the first.