Fence
Field cell-object reference. Type tag: fence. The key words
MUST, MUST NOT, and MAY are
used as in RFC 2119. See the Cell Objects index
and the Field Stage Lifecycle for how
objects are spawned and persisted.
Config schema
Fields authored on this object in the stage JSON:
| Field | Type | Default | Note |
|---|---|---|---|
position | [x, y, z] | — | stage-local spawn position |
link_id | string | — | pairs the fence to a step-switch with the same link_id |
scale_x | number | 1 | stretches the fence span along X |
Spawn behavior
A toggleable barrier placed from the stage config. Starts solid (raised) and blocks the exit / path it spans.
Persisted state
Link state (raised / lowered) is persisted with the cell. A fence lowered by its switch MUST stay lowered on re-entry.
Interactions
A fence is not attacked. It is toggled by stepping on the step-switch that shares its link_id (the flip_switch plan action). A switch is bound to a specific fence link, so it only ever affects its own fence(s).
Notes
Distinct from gates: a fence is switch-driven and link-scoped, whereas a key is section-scoped.