Slush beach lighting demo (fork of Dockhands)
- ..
- .metadata87 B
- README.md2.3 KB
- workflow.js10.6 KB
- workflow.yaml2.5 KB
README.md
add-disguises-to-a-level
Turns an existing level into a disguise level with disguiseKit: guards who care what you wear, ground where only some roles belong, clothes to take, work to hide in, and a notice sign over each watcher.
What it does
- Survey. Finds where the level is authored, whether the kit is already on, the disguiseKit pieces already placed, and the places and people in it. Changes nothing.
- Switch on. One
Disguisescomponent (orDK.setup) with the start role and sign style. - Areas. An
Areaper place (public, workyard, staff, guards, innerCourt, forbidden) sized to its walls, labelled, withallowwhere the kind's own list does not fit; each checked withDK.areaAtandDK.belongs. - Watchers. Guards at the doors and at least one watcher who sees through a role up close (foreman, captain, head of house or abbot, 4 m by default), dressed with
Outfits. - Wardrobes and work. Laundry lines, chests and robe racks with the clothes the areas need, and work spots (sweep, fish, pickup / dropoff...) to blend in at, placed at the same time.
- Sign style. One of inkBrush, paperLantern, woodPlaque, pixel, minimal, comic, set on the Disguises component.
- Play test. In a sub-client: wrong clothes in a restricted area fill a watcher's meter and blow the cover; right clothes do not; the seeing-through watcher catches its own role up close; wardrobes and work spots work. Kit bugs are reported, not patched.
- Tests. Runs the
disguiseKitTestssuite in edit mode.
It answers with the areas, watchers, wardrobes, work spots and sign style placed, the play checks that failed, any kit bugs, and the test counts.
What it needs
disguiseKit installed (its dependencies come with it) and a level to work on. Everything goes into the level's authored source, so it survives a reload.
Starting it
zero workflow start --name add-disguises-to-a-level --args '{"level":"main","theme":"a harbour at dusk","startRole":"fisher"}'
All args are optional: level (scene or build file; default the startup scene), theme, startRole (default own), signStyle. Then zero workflow next --runner <you> / zero workflow answer --request <id> --value <json> until it finishes.