Games, labs and tooling

Causeway is a turn-based tactics game. Wardens hold an eight-by-eight island while the Hollow cross the causeway from the mainland at low tide; each Hollow shows on the ground what it will strike, and a shove that moves it moves its strike, so a turn is read and answered rather than raced. The tide comes in on a schedule shown in advance, drowning any Hollow it reaches, and high tide closes the causeway and wins the island. Three wardens of six are mustered for a crossing, a road of six islands that forks three times, with a boon chosen between islands and the Hearth carried from one to the next. Past the Lighthouse it divides between two worlds, where a fourth warden joins. In the Cinderfast lava rises instead of the tide: it burns what it reaches, vents spill it across the board, and water a warden throws on it cools into new ground. In the Rime anything shoved onto ice skids on until something stops it, and thrown water freezes. Some forks offer an uncharted island, generated from the crossing's seed to its world's rules and built at runtime.

The rules are one value and pure shared functions in rules.decay, so aiming previews a skill by running it on a copy of the board; the director plays back the beats each change leaves. The islands are text in islands.decay, read by the rules and by tools/causeway_art.py, which builds every island, figure and building as a low-poly GLB. It uses imported models with point lights, the environment's grade and bloom in the shipped player, Weave screens, the pointer's world ray for picking cells, camera shake, and Sound Lab effects and an Ogg song. a_crossing_is_played.rs plays a whole crossing with a bot through the real rules; the_game_is_played plays it by clicks and keys. Four 300 ms quarter views use J/L, compact touch buttons and sea swipes. View-relative keys and guarded ray picking preserve movement and combat; muted model silhouettes reveal units behind raised terrain.

Orbital Last Stand is the proof named by many entries on the other pages: masks and sensor events, overlap queries, typed script references, profiles, tags and spatial queries, tweening, the mixer and save, the full form-widget set and composed Weave styling. Its own evidence and plan documents record what it exercises in detail. Its complete-game edition adds a fleet hangar with four sidegrade hulls, three difficulty settings, a finite twelve-boss rush, evasive burst, career salvage/unlocks, commendations, the full module/threat archive, recent sortie records and accessibility settings. All nineteen synergy recipes grant explicit build bonuses, catalog descriptions match their combat effects, and three Sound Lab compositions crossfade through named audio buses. Game logic remains Decay; Weave owns responsive screens. Unicode text saves were the general engine gap found by the callsign and flight log.

A side-view level painted as a tilemap and made solid by a Tilemap Collider 2D, a hero who runs and jumps, ten coins and a flag, a HUD, and a camera that follows. The scene and its Decay scripts are the game, and it exports to the site.

Its hero uses the scene-owned Character 2D controller. Decay integrates velocity and gravity, queues displacement and reads cached walkable support. One capsule probe checks ground obstacles; body and foot sensors preserve pickups independently. Walls, ceilings and one-way undersides never grant standing. It gives the jump a buffer for a press just before landing and coyote time for one just after running off a ledge. Letting go early cuts the rise short.

It found three gaps, all closed as general capabilities: a script moving a body's transform was undone by the next physics step, so a respawn did nothing; a frictionless hero clung to walls because friction averaged; and camera behaviors ran only in the camera example. Its tests stand the hero on the painted ground, have a scripted player reach the flag without falling, and hold the camera to following it inside the level. Its joints, materials, one-way planks, ferry, forces and lighting are listed with those capabilities.

A scene, four prefabs and four Decay scripts are the game, and it exports to the site. Gamepads were the capability it needed and were added for it as a general one.

Players are made when a pad joins. The match reads Gamepad.joined(), spawns a player prefab, and authors its slot with World.set_property; odd slots play for Blue and even for Red. Unplugging a pad takes its player off through Gamepad.left(). Each player readies with North, picks one of two characters with the d-pad, walks with the left stick and kicks with the right bumper, aimed with the right stick, all read through its own slot.

Scripts talk by type and by event. A player kicks the ball with a typed message (this.ball.kick(velocity, slot)) and bends the shot with nudge; the match counts players whose live ready field is set; a power-up sends power_up to the player who took it, or emits WindPicked or FirePicked; the ball sends catch_fire to an opponent it touches while alight, and emits GoalScored when it crosses a goal line. Possession, pickups and reach are distance checks, because a collider does not scale with its entity and the Enlarger makes a player bigger.

It found two gaps, both closed. A child sprite was drawn from its own transform alone; a child's transform is now local to its parent everywhere. And the test harness did not lay out screen text, so a misspelled text anchor passed every test; the harness now lays it out each step.

It is checked, not just run. The tests press pads: two join on their own sides, ready up and kick off; Blue takes the ball, dribbles past Red and scores; a sign cannot be taken until it lands; unplugging a pad takes its player off; Blue collects all four powers; and a Fireball sets an opponent running wild until it burns out. Select in the lobby adds a bot, which attacks, supports, defends goal-side of the ball and goes for loose balls it can reach first; the tests have one score on a player standing still, and two play each other until one scores.

Low Tide's Basin is a voxel world viewed as a map. It exercises sparse Grid.set_block edits for biome harvesting, typed shared state and deck tiles for its six-resource hold (four slots on the small starter crawler, growing to sixteen through three resource-funded stern extensions), and prefab spawning for deterministic wrecks across the Basin. Keyboard and phone-touch runtime tests harvest, carry, stow and jettison actual blocks; the workbench consumes physical cargo for deck expansion, a bunk and an engine upgrade, preserving the crew and deck origin while driving. Its viewport-sized workbench exposes three directly selectable blueprints, current cargo versus cost, installed and chassis-limit states and explicit actions.

Its wrecks spawn six resource-specific cargo prefabs as hull children; Decay selects the nearby physical crate and retains a per-slot mask across wreck streaming. Carried cargo can be set down as a world prefab and picked up again before stowing. Its instrument HUD uses authored atlas icons, real hold segments and speed/phase-time meters, and discard confirmation is tied to a cell and cancels on movement, Escape or timeout.

A side-view high-tide dive frames a wreck tilemap with a second authored camera; Decay swims against hull cells, manages air and a heavy cache, then deposits ore and scrap in the original hold only after returning. The map tide continues; recall, empty air and ebb recover crew without loot. It found the reversible map flood capability; its season, cargo loss, waiting and escape rules are Decay gameplay. These are Decay gameplay rules on existing engine APIs.

A movable origin and radius guide accompany the actual nearest result and ordered radius snapshot. Tag selection, equal-distance samples, an exact boundary target, active/parent toggles, rotating and scaled parent transforms, a transformless tagged entity and persistent gray markers make the query contract observable. Native regressions exercise these cases and phone touch; browser smoke exercises visible controls and captures desktop/phone project-subpath and custom-domain exports. Orbital remains the gameplay proof of the APIs.

Camera-relative dead-zone and world-space camera-center bounds guides, mode toggles, sampled coordinates, an automatic tour, impact button and touch movement pad make follow, confinement and shake observable. The native harness uses the same scene/scripts, binds the packaged font and supplies UI hit-testing; Pages uses the existing shared browser host. Runtime regressions exercise modes and phone touch; browser smoke covers desktop and phone controls and project/custom-domain routes.

Nothing the engine, editor, native game or browser export builds depends on the tool: the assets it produces are ordinary PNGs and sheet documents, and by the time a game loads one there is nothing left to say it was baked.

It bakes three views. Isometric is the default; top-down and side were added because the isometric camera cannot reach them by any choice of tile. The flat views state pixels_per_unit rather than deriving a scale from a diamond they do not draw, and each view refuses the other's fields. A grain option shifts texels along a material's ramp, hashed from the texel's position on the model, so the same texel is the same shade in every bake. Height is baked rather than scaled, so a slab is its own tile. The baker refuses art that overhangs its own footprint, and a sheet declares where its sprites meet the ground.

The same bake runs in a page on the site (web/), built from the tool's own sources with their types stripped. web.test.ts asserts its output matches the command line's pixel for pixel; a browser smoke test opens it in CI. The page also bakes Blender models: a recipe may name a .glb, .gltf or .obj ("kind": "file"), which Three.js reads into triangles that are fitted, centred on the footprint and banded like a hand-written model (imported.test.ts, models.test.ts). A model that comes as several files opens whole, from a zip, a folder or the files chosen together, and a textured model's colors are cut to a few (quantize.test.ts, unzip.test.ts). The command line cannot read model files yet.

Orbital Last Stand uses it for one thing: textures/detonation.isobake bakes a five-frame blast, top-down, as variants of one sheet, and scripts/detonation.decay plays the clip and despawns when Animation.is_finished says it ended.

A quad is drawn centred on its entity, so without an anchor the middle of the picture is what lands on the tile. A sheet declares where its sprites meet the ground, and sindri.tilemap has tile_overhang, how far below its cell a tile's art may reach: the cell is unchanged and still what the grid, picking, occupancy and gameplay measure in; only the drawn quad grows, downward.