AnvilDirector
<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this component provides and who consumes it, then delete both comment lines. -->
AnvilDirector
<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this component provides and who consumes it, then delete both comment lines. -->TODO: describe this component.
Interface
What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.
conforms to
zero/source-extract/v2AnvilDirector — the one tick in ANVIL CROWN. It sits on the scene's `Director` entity and does four things: 1. resolves the scene's named anchors into `A.anchors`, once; 2. calls `build(anchors)` on any system that has registered and not yet been built — including one that arrives later, so a slice that hot-reloads its module joins the running game without a restart; 3. ticks every registered system in declared order; 4. owns the run's phase machine and the clock. No slice edits this file and no slice edits the scene. A slice writes its own module, calls `A.register(...)` from the top of it, and the director picks it up on the next frame.
resolveAnchors( ) → void
buildPending( ) → void
tickSystems(dt: number) → void
| arg | type | description |
|---|---|---|
| dt | number |
standInStorm(dt: number) → void
Until the storm slice claims it, the director walks the altitude itself so the skeleton is a moving, checkable thing rather than a still frame. The moment `A.claims.storm` is set, this stands down for good.
| arg | type | description |
|---|---|---|
| dt | number |
fitCamera( ) → void
The camera stands where the shaft touches both screen edges. Staging owns the camera during cutscenes; until `A.claims.staging` is set, the director holds the framing so the game is never mis-framed or letterboxed.
dropStandIn(key: string) → void
| arg | type | description |
|---|---|---|
| key | string |
cloudFar( ) → void
Statically pinned so the scene carries its stand-in materials as real dependencies rather than a name computed at runtime. The stand-in shaft is EMISSIVE by design, not lit: a supercell's interior is lit from within, and three receding slabs at rising emissive read as depth in one frame. The vfx slice replaces all of it.
cloudMid( ) → void
cloudNear( ) → void
hullMat( ) → void
slab(parent: ?, name: ?, w: ?, h: ?, z: ?, mat: ?) → void
| arg | type | description |
|---|---|---|
| parent | ? | |
| name | ? | |
| w | ? | |
| h | ? | |
| z | ? | |
| mat | ? |
standInShaft( ) → void
standInAirframe( ) → void
advanceBand( ) → void
phaseMachine(dt: number) → void
| arg | type | description |
|---|---|---|
| dt | number |
awake( ) → void
ensureScene( ) → void
verifyBands(dt: number) → void
| arg | type | description |
|---|---|---|
| dt | number |
update(dt: number) → void
| arg | type | description |
|---|---|---|
| dt | number |
editorUpdate(dt: number) → void
The scene must be visible and legible while authoring too, so anchors resolve and systems build in edit mode as well — they just do not tick.
| arg | type | description |
|---|---|---|
| dt | number |
Sub-parts
Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.
Problems
Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.
agent_score is exposed.+ 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".
Scoped to this part · feeds back into the world's score.