# registry This machine's list of placed pieces (with a spatial hash for nearby lookups and a map from collider entity to piece), the build zones the scene declares, the shared ticker for animating pieces, and the kit's event bus (`on`, `fire`). BuildPiece and BuildMode components fill it; everything else reads it.

# geom The maths buildPlaceKit places pieces with, pure and identical on every machine: vectors, yaw and quaternion helpers, piece poses, oriented boxes (OBB) from a kind's boxes, the separating-axis overlap test, ray against box, point in box, a standing capsule against a box, and slope from a normal. Rules, snapping, the ghost and the tests use it.

# controller Build mode on one player's machine: it reads the build controls (keyboard, gamepad and touch taps), aims from the pointer or the view, asks `buildPlaceKit.snap` for candidate poses and `buildPlaceKit.rules` which fits, colours the ghost, draws the menus, and sends what the player decides to `buildPlaceKit.authority`. It also finds the door in front of the player for Interact and runs the shared ticker for swinging and burning pieces. BuildMode components drive it once per frame; `Build.open`, `select`, `setStyle` and friends call into it.

# buildPlaceKit **A base-building kit for any multiplayer Zero world: press B, pick a piece, see a green or red ghost where you aim, turn it, click to place it.** Pieces cost money and give part of it back when you take them down, they snap to a grid, to any surface or to each other, and every player (and everyone who joins later) sees the same base. Version **1.0.18** (`Build.VERSION`; this README, `package.yaml` and `Build.VERSION` move together). **What you get:** 24 piece kinds in two styles (a rustic **Frontier** style in oak timber, dry stone and thatch, and a sci-fi **Outpost** style in hull panels with glowing trim), three snap modes, four ghost looks, three build menus, prices and refunds through economyKit's cheat-proof wallets, a thud, a camera kick and a dust puff on every placement (juiceKit and the kit's own sounds), keyboard and mouse, gamepad and touch controls, pieces kept between sessions, and 22 automated tests. One install brings gridKit, economyKit and juiceKit with it, and the wood, stone, masonry and sci-fi material collections the styles are drawn with. ## First example 1. Install **buildPlaceKit** into your world: search ZeroMind for "buildPlaceKit" and install it from the ZeroMind panel, or install the package id `710d96cd-5dfe-476c-aa76-f43ac60fdefc` (`zeromind.installAsset`). It takes a few seconds to a minute. On the current engine, install 1.0.17 or newer: older releases are refused (#22402, see Known limits). 2. In `scenes/main.scene/build.luau`, add this line inside `function content()`, before its `end`: ```lua require("buildPlaceKit.api").BuildMode {} ``` 3. Press Play and press **B**. If, right after installing, no wallet shows in the top-left and every piece is refused with "Not enough Coins", close the world and open it again once (#22328, see Known limits). Stop and Play does not clear it; reopening does, and it does not come back. A 60 × 60 m build zone sits around the scene's origin. A hotbar of pieces opens at the bottom of the screen and a glowing hologram of a foundation follows where you aim. Click to build it: 20 coins leave your wallet (top-left; every new wallet starts with 100), it lands with a thud and a puff of dust. Pick a Wall (scroll or number keys) and aim at the foundation's edge: the wall clicks onto it. Aim at the ground under your own feet and the ghost turns red (*Someone is standing there*); clicking there buzzes and builds nothing. (Aim a second foundation at the first instead and it clicks on beside it: piece-to-piece snapping is the default.) Press **X** and click a piece to take it down for half its price back. **B** or **Esc** puts build mode away. economyKit, which the kit uses for wallets, also starts inventoryKit's bag for every player. When the kit sets economyKit up itself (as here), it turns the bag's strip, its Tab/I keys and its touch button off, and stands the rest of inventoryKit's keys down (G for its screen-style gallery, the number keys, E at a chest; the `buildPlaceKit.bagQuiet` input map), so a world that only wants building gets no bag and no bag keys. (This needs economyKit 1.0.13 or newer, which buildPlaceKit 1.0.14 and newer install: older economyKit releases loaded a second copy of inventoryKit, so the bag strip stayed on whatever the kit asked.) Pass `inventory = true` to `Build.setup` to keep the bag; with the bag on, build mode stands it and its keys down while it is open (so Tab, G and the number keys are the build kit's) and puts them back when build mode closes. The kit sets economyKit up again at the start of every Play, so the bank, the wallet and coins on the ground work on the second Play of a session as on the first. If your own code calls economyKit or juiceKit too (coins on the ground, an effect of your own), install those two kits into your world as well: economyKit `d113a24e-3a87-40d2-a725-af49b56f629b`, juiceKit `eed55f6d-afaf-4767-83c5-539ef91e0dc5`. The install moves the copies buildPlaceKit brought up to your world's top level rather than adding second ones, so there is still one wallet and one bank. A kit that only came in as buildPlaceKit's dependency belongs to buildPlaceKit, and a game that requires it without installing it can find it unresolved once published. Today, on the current engine, those two installs are refused (#22402, see Known limits). Until economyKit and juiceKit are published again, your code can call the copies buildPlaceKit brought, which run in your world; install the two kits yourself once they install again, before you publish a game that relies on them. ## Guides Two guides ship inside the package and open in the Docs panel, with `man`, or with the `guides` tool by their folder path: - **How do I let players build walls, floors and roofs in my game?** What the kit gives you, how pieces, styles, snap modes, ghost looks, menus, prices and multiplayer fit together, and what to do first: `buildPlaceKit.package/how-to-let-players-build-walls-floors-and-roofs-in-your-game`. - **Make a base building survival game, step by step.** From an empty world to a small multiplayer game where players earn coins and build themselves a shelter, with buildPlaceKit, economyKit, juiceKit and gridKit: `buildPlaceKit.package/make-a-base-building-survival-game-step-by-step-earn-coins-and-build-a-shelter`. ## Changing it with one setting ```lua local Build = require("buildPlaceKit.api") -- inside content(): Build.BuildMode { style = "scifi", -- "rustic" (Frontier) | "scifi" (Outpost) | your own ghost = "blueprint", -- "hologram" | "tint" | "wireframe" | "blueprint" | your own menu = "catalogue", -- "hotbar" | "radial" | "catalogue" snap = "grid", -- "grid" | "surface" | "socket" size = { 40, 30, 40 }, -- the build area (x, height, z), centred on `position` position = { 0, 0, 20 }, } ``` Every name also answers to its aliases (`"Outpost"`, `"wheel"`, `"outline"`, `"piece to piece"`, ...); an unknown name is an error that lists the valid ones. Several zones can sit side by side, each with its own settings; a player builds by the rules of the zone they aim into. Players can switch style (**T**), snap mode (**G**) and, where the world allows it, ghost look (**V**) themselves; a zone turns that off with `allowStyleSwitch = false` / `allowSnapSwitch = false`. All `BuildMode` options: `label`, `style`, `ghost`, `menu`, `snap`, `size` (or `sizeX`, `sizeY`, `sizeZ`), `cell` (grid cell, default 3 m), `free` (no cost), `costScale`, `refund` (0-1, default 0.5), `removeAnyone` (default: only the builder takes a piece down), `pieces` (list of kinds allowed), `styles` (list of styles allowed), `allowStyleSwitch`, `allowSnapSwitch`, `maxSlope` (degrees, default 35), `showBounds` (mark the edges on the ground while building), `order` (which zone wins where two overlap), plus `name`, `position`, `yaw`. Kit-wide defaults go in `Build.setup` from code that runs in play (a scene's `entrypoint.luau`): ```lua local Build = require("buildPlaceKit.api") function onLoad() Build.setup({ style = "rustic", ghost = "hologram", menu = "hotbar", snap = "socket", refund = 0.5, removeAnyone = false, persist = true, startCoins = 500, -- what a new wallet starts with (economyKit currency "coins") wallet = "corner", -- economyKit wallet display; economy = false leaves economyKit's setup to you allowGhostSwitch = true, -- V cycles the ghost look inventory = false, -- true keeps inventoryKit's bag (strip, Tab/I, touch button), which economyKit starts }) end ``` ## Languages Every word a player reads (the build panel, the menus, the touch buttons, the hints, piece, style, look, menu and snap-mode names and descriptions, prices, and every refusal) comes in **English** and **Brazilian Portuguese**, the languages of economyKit and gridKit. Each player reads the kit in their own language (`i18n.pick` over the kit's languages), and refusals travel from the deciding machine as codes, so two players in different languages each read the reason in theirs. To change a line or add a language, put a catalog in your world, `/locales/<tag>/buildplacekit.json`, with any of the kit's keys (`buildPlaceKit.lang` lists them all in `Lang.WORDS.en`): ```json { "place": "Build {{ piece }} for {{ cost }}", "piece_wall_name": "Palisade" } ``` or from code: `require("buildPlaceKit.lang").define("es", { place = "Colocar {{ piece }} {{ cost }}", ... })`. A piece, style or look you add yourself reads `piece_<id>_name` / `_desc` (`style_`, `ghost_`, `menu_`, `snap_`) the same way, and shows the name you gave it until a catalog names it. ## Controls | | keyboard and mouse | gamepad | touch | |---|---|---|---| | build mode on / off | **B** | **Y** | **Build** button | | place | left click | **RT** | tap the world to aim, then **Place** | | rotate | **R** | **RB** | **Rotate** | | pick a piece | wheel, **1-0**, **[ ]** | d-pad left / right | tap it in the menu | | menu (catalogue, wheel, next hotbar page) | **Tab** or **Q** (hold for the wheel) | **LB** (hold for the wheel) | **Menu** | | demolish (take down, part refund) | **X**, then click | d-pad down | **Demolish** | | snap mode | **G** | d-pad up | **Snap** | | style | **T** | in the catalogue | in the catalogue | | ghost look | **V** (when allowed) | | | | open doors, gates, chests | **E** | **X** | | | close menu / leave build mode | **Esc** | **B** | **Exit** | On a touch screen the kit reads where the engine draws its own buttons (Sprint, Interact, Jump, and any a game adds) every frame and keeps clear of them: its own buttons stand on top of that column, or beside it on a screen too short to stack them, and the piece strip and hotbar stop short of it. Checked on a wide touch screen (1920 × 1080), a phone held sideways (1688 × 780) and upright (780 × 1688). While the catalogue or the wheel is open, walking and the camera stand down (the `buildPlaceKit.buildBlock` input map) and the mouse is freed, so pointing at the menu never turns the view. ## Catalogue `Build.catalogue()` returns every entry below as `{ kind, setting, id, name, description, tags }`; `Build.variants{ kind = "piece", category = "roof" }` filters it. ### Pieces (`Build.select("wall")`, or `pieces = { ... }` on a zone) Sizes are in metres (width × height × depth). One cell is 3 m, one storey 3 m. Prices are coins in the Frontier style; the Outpost style costs 1.5 times as much. | id | name | category | size | price | snaps onto | |---|---|---|---|---|---| | `foundation` | Foundation | foundation | 3 × 0.45 × 3 | 20 | the ground; other foundations' edges | | `floor` | Floor | floor | 3 × 0.25 × 3 | 10 | the ground; slab edges; wall tops (upper storey) | | `wall` | Wall | wall | 3 × 3 × 0.25 | 15 | slab edges; wall tops; beside walls | | `wallWindow` | Window Wall | wall | 3 × 3 × 0.25 | 18 | as a wall | | `wallDoorway` | Doorway Wall | wall | 3 × 3 × 0.25 | 16 | as a wall; takes a Door | | `door` | Door | door | 1.3 × 2.3 × 0.12 | 12 | a doorway only; opens with Interact | | `wallHalf` | Half Wall | wall | 3 × 1.5 × 0.25 | 8 | as a wall | | `roofFlat` | Flat Roof | roof | 3 × 0.25 × 3 | 12 | wall tops; slab edges; walls stand on it | | `roofSlope` | Sloped Roof | roof | 3 × 1.5 × 3 | 14 | wall tops (rising inward); another slope (peak or higher course); beside a slope | | `roofCorner` | Roof Corner | roof | 3 × 1.5 × 3 | 14 | wall tops; beside slopes | | `stairs` | Stairs | stairs | 2.4 × 3 × 3 | 20 | on a slab; out from a slab edge; the ground | | `ramp` | Ramp | stairs | 3 × 1.5 × 3 | 15 | on a slab; out from a slab edge; the ground | | `ladder` | Ladder | stairs | 0.7 × 3 × 0.15 | 6 | a wall face | | `pillar` | Pillar | wall | 0.4 × 3 × 0.4 | 5 | slab corners; the ground | | `fence` | Fence | defense | 3 × 1.1 × 0.12 | 6 | the ground; slab edges; beside fences | | `gate` | Gate | defense | 3 × 1.4 × 0.15 | 14 | as a fence; opens with Interact | | `barricade` | Barricade | defense | 3 × 1.4 × 1.2 | 10 | the ground; slabs; slab edges | | `towerBase` | Tower Base | foundation | 3 × 3 × 3 | 40 | the ground; floors and walls click onto its deck | | `campfire` | Campfire | utility | 1.3 × 0.9 × 1.3 | 8 | the ground; slabs; lit, flickering light | | `chest` | Storage Chest | utility | 1.1 × 0.75 × 0.65 | 12 | the ground; slabs; lid opens with Interact | | `torch` | Torch | utility | 0.3 × 1.7 × 0.3 | 3 | the ground; slabs; wall faces; lit | | `workbench` | Workbench | utility | 2 × 0.95 × 0.9 | 18 | the ground; slabs | | `bed` | Bed | utility | 1.1 × 0.7 × 2.1 | 16 | the ground; slabs | | `banner` | Banner | utility | 1 × 3.2 × 0.2 | 7 | the ground; slabs | ### Styles (`style`) | id | name | what it looks like | price | |---|---|---|---| | `rustic` | Frontier | oak-bark log frames, oak boards and planks, dry-stone footings, golden thatch, iron straps, warm firelight | × 1 | | `scifi` | Outpost | gunmetal and light hull panels, deck plating, carbon, hazard stripes, cyan light strips and energy cores | × 1.5 | ### Ghost looks (`ghost`) | id | also | what it looks like | |---|---|---| | `hologram` | holo, glow | a glowing see-through hologram with a bright rim that breathes (default) | | `tint` | plain, transparent | the piece washed green or red, half see-through | | `wireframe` | outline, lines, edges | edges only: clearly green where the piece fits, red where it does not | | `blueprint` | plan, schematic | drafting blue, coloured edges and a grid on the ground | Every look is green where the piece fits and red where it does not; a refused click also jolts the ghost sideways. ### Build menus (`menu`) | id | also | what it is | |---|---|---| | `hotbar` | strip, bar | a strip of pieces along the bottom; number keys, scroll or tap; Tab pages through categories (default) | | `radial` | wheel, pie | hold Tab / LB for a wheel of categories and pieces; point and release | | `catalogue` | grid, shop, store | a full catalogue with pictures, prices, refunds, the style switch and your wallet | ### Snap modes (`snap`) | id | also | how pieces land | |---|---|---| | `grid` | cells, tiles | slabs on cell centres, walls on cell edges (turned along the edge you aim nearest), posts and torches on corners, on whatever surface is under the cell (walls on a floor's edge stand on the floor); roofs rest on the wall tops around their cell; cells come from gridKit's square grid | | `surface` | free, anywhere | exactly where you aim, on whatever is there: on open ground turned to face you in 15° steps, on a placed piece squared up with it; aimed right at a matching edge or wall top (within 0.7 m) it clicks on, so floors, walls and roofs still meet; torches and ladders aimed at a wall hang on it | | `socket` | piece to piece, snap | onto the nearest matching socket of a placed piece within 1.8 m (default); with nothing near, ground pieces sit on the surface | In every mode: - **Torches and ladders hang where you aim on a wall:** a placed wall, or any solid surface of the world (a scene's wall, a rock face). A torch also stands on the ground or a floor. - **Roofs follow the wall top you aim at.** Aimed at a wall top, or just past it so the aim lands on the ground behind, a roof rests on that wall top, over the floor side first (Rotate puts it on the other side). A roof never sits at floor level beside a floor. - **Gentle slopes are fine.** Pieces stay level, so on a slope a piece dips into the ground at its low side; ground up to `maxSlope` (35° by default) takes any piece. ## Refusals A red ghost names why, and a click there is refused with that reason and nothing is built or charged: | code | text | |---|---| | `overlap` | Something is already built there | | `player` | Someone is standing there | | `floating` | Needs something to rest on | | `slope` | The ground is too steep | | `outside` | Outside the build area | | `blocked` | Something is in the way (scenery that is not a piece, and not the ground or slope the piece stands on) | | `needsSocket` | Needs a doorway to fit into (doors) | | `cost` | Not enough Coins: you need 12 more | | `tooFar` | Too far away | | `notYours` | Someone else built this (taking down) | ## Events ```lua local Build = require("buildPlaceKit.api") local stop = Build.on("placed", function(e) print("built", e.kind, e.id) end) Build.on("refused", function(e) print("refused", e.code, e.text) end) Build.on("fx", function(e) print(e.what, e.kind, "by peer", e.peer) end) -- every change, on every machine stop() ``` Events: `placed`, `refused`, `removed` (this player's requests), `pieceAdded`, `pieceRemoved` (any piece on this machine), `buildOpened`, `buildClosed`, `message`, `fx` (every placement, removal and door from the deciding machine), `restored`, `rejected`. ## Your own pieces, styles and ghost looks ```lua local Build = require("buildPlaceKit.api") -- a piece: size, price and how it snaps; its look is drawn by the style Build.definePiece("well", { name = "Well", category = "utility", size = { 2, 1.2, 2 }, cost = { coins = 25 }, description = "A stone well.", }) -- a style: borrow the shapes of a flavor ("timber" or "panel") and give each surface role a material Build.defineStyle("desert", { name = "Desert", flavor = "timber", costScale = 1.2, materials = { plank = asset.resolve("masonryMaterials.materials.stucco", "material"), roof = asset.resolve("masonryMaterials.materials.roofClayPantiles", "material"), cloth = { color = { 0.85, 0.55, 0.2 }, rough = 0.9 }, }, }) -- a ghost look: build(ghost, parts, kind) spawns under ghost.root, color(ghost, valid) recolours Build.defineGhost("sketch", { name = "Sketch", build = function(ghost, parts, kind) --[[ spawn entities under ghost.root ]] end, color = function(ghost, valid) end, }) ``` Material roles: `frame`, `plank`, `floor`, `stone`, `roof`, `metal`, `accent`, `trim` (emissive), `glass`, `cloth`, `fire`. A role is a material handle (always write `asset.resolve("…", "material")` with a literal name: `zm push` refuses computed asset names) or a colour spec `{ color, rough, metal, glow, alpha }`. A role a style leaves out is borrowed from `rustic` (or `base = "<style>"`). A piece kind's full shape, for snapping your own kinds to the built-in ones: `boxes` (what it blocks, `{ c = centre, s = size, pitch? }`), `support` (points that must rest on something), `sockets` (`{ tag, p, yaw }` it offers) and `plugs` (`{ tag, p, yaw }` it attaches with). Socket tags in use: `floorEdge`, `floorTop`, `floorCorner`, `wallTop`, `wallSide`, `wallFace`, `doorway`, `roofTop`, `roofSide`, `pillarTop`, `fenceSide`. See `buildPlaceKit.catalog`. ## Pieces the scene places ```lua -- inside content(): a real piece (doors open, fires burn, players snap to it) that cannot be taken down Build.piece { kind = "campfire", style = "rustic", position = { 4, 0, 6 }, yaw = 0 } ``` ## Reference `local Build = require("buildPlaceKit.api")` - Scene: `BuildMode(opts)`, `piece(opts)`. - Setup: `setup(opts)`, `definePiece`, `defineStyle`, `defineGhost`, `catalogue()`, `variants(filter)`. - This player: `open()`, `close()`, `toggle()`, `isOpen()`, `select(kind)`, `setStyle`, `setSnap`, `setGhost`, `setMenu`, `state()`. - Requests (answered by the deciding machine, `cb(res)` with `{ ok, code, text, id, costs, refund }`): `place(kind, style, position, yawDegrees, cb)`, `remove(pieceId, cb)`, `toggleOpen(pieceId, cb)`. - Reading: `check(kind, position, yawDegrees)` → `ok, code, text`; `pieces()`; `stats()`; `clearSaved()`. - Modules for advanced use: `buildPlaceKit.catalog` (data), `.snap` (where a piece goes), `.rules` (whether it fits), `.geom` (oriented boxes), `.art` (how pieces look), `.ghost`, `.menus`, `.fx`, `.sfx`, `.authority`, `.registry`. - Components: **BuildMode** (a zone), **BuildPiece** (one placed piece; put there by the deciding machine or by `Build.piece`). ## How it stays fair in multiplayer - **One machine decides.** The machine running economyKit's bank (the lowest peer in the room) decides every placement, removal and door. A player's machine only sends a request; the deciding machine checks it against its own copy of the world with the same rules the ghost uses, takes the price from the wallet through the bank, and only then builds the piece. Two players clicking the same spot in the same moment are decided one after the other, so the second gets "Something is already built there" and pays nothing. - **Pieces are synced entities** the deciding machine owns, so every player sees them and a player who joins later receives them all. Each machine draws a piece's look and colliders itself from its kind and style, so a piece costs one small synced record on the wire. - **No free pieces.** Money moves only through the bank (economyKit's rules apply: balances written by hand are put back). A piece entity some other machine spawns without asking is not vouched for by the deciding machine: it is refused and every machine hides it. - **Wallets and the bank restart on every Play.** After Stop and Play the kit starts economyKit's bank and every player's wallet again (a player's coins are kept by economyKit), so the wallet shows, coins on the ground pay, and a second player who joins after the host restarted gets a ready wallet with their starting coins. - **Kept between sessions.** The deciding machine writes each piece to the world's runtime data and puts them back at the start of every play session: after Stop and Play, after reopening the world, and beside any pieces the scene places itself (`persist = false` turns that off; `Build.clearSaved()` forgets them). ## Performance Each piece is 4-14 instanced parts and 1-5 box colliders, built locally, with nothing per frame unless it burns or swings. Fires and torches share a light budget (the nearest 8 are lit; `require("buildPlaceKit.art").lightBudget(4)` for phones). The ghost is one set of parts recoloured in place. Overlap checks only compare pieces within a few metres. ## Tests The `buildPlaceKit` suite (22 tests): Stop letting the next Play set economyKit up again, inventoryKit's keys standing down while its bag is off, saved pieces coming back on every Play (also on the second Play of one engine session, and beside the scene's own pieces), the first Tab paging the hotbar, building on a 12° slope (and a 48° rock refused), torches and ladders hanging on world walls, a torch on a built wall under a roof, a roof aimed past a wall top landing on the walls in all three modes, both languages complete, the catalogue, every kind drawn in every style, prices and refunds, grid cells/edges/corners, grid walls on a floor and a roof on the walls, surface placement and wall mounts, a surface-mode hut (free floor, walls clicking onto its edges, roof on the wall tops), placed pieces keeping their colliders, a piece-to-piece hut (walls on floor edges and at a corner, a second floor, a roof on a wall top and at the peak, a door in a doorway, stairs), every refusal, the deciding machine (one spot, one piece; only the builder takes it down; a forged piece refused), your own piece and style, and this README's first example. Run it in edit mode with `tools.use("tests", "run", { suite = "buildPlaceKit" })` (a suite is picked by its `.testSuite` asset name). Each release is also installed from ZeroMind into a brand new world, the way anyone installs it, and checked there. 1.0.15 changed only the deciding-machine test (its made-up players now take peer ids above every peer in the session, so a real player can never share one) 1.0.16 only these texts, 1.0.17 only how `package.yaml` writes its description (on one line, so the current engine installs it; #22402) and these texts, and 1.0.18 only the wording of that description (what the kit gives you and how to install it), so the play checks of 1.0.14 still hold: the four kits of the example guide installed, the world reopened once, the guide's code pasted, then a wallet of 30, a coin paying 5, no bag strip over the hotbar, **G** switching to Grid, and on the second Play the bank up, the wallet kept and coins paying. Earlier, the 1.0.9 release candidate was checked in depth: one install of the package (7,676 files in 7 s), this README's first example added word for word to `scenes/main.scene/build.luau`, the test suite passing 18 of 18 twice there (and twice in this world), and in play with real mouse aim and clicks: a floor, two walls and a roof built in each of the three snap modes (grid walls on two cell edges and the roof on their tops; piece-to-piece walls on the floor's edge sockets; surface walls clicking onto the edges of a floor turned to face the camera), a foundation aimed at the player's own feet shown red with *Someone is standing there* and its click refused, a 60-coin Outpost tower base with 40 in the wallet shown red with *Not enough Coins: you need 20 more*, refused and charging nothing, and every placed piece a synced entity owned by the deciding machine. The example guide's game was built in that world from its steps too. The 1.0.17 release candidate (1.0.17-rc1, the same files with only the version number different) was installed into a brand new world on the current engine in one step (7,676 files) and passed 22 of 22 twice there. ## Known limits - **#19525: a Text3D label rasterised at `scale` 2 has the tops of its letters cut off.** The showcase's big headers (FRONTIER STYLE, OUTPOST STYLE, RAISE THE ROOF) showed it. The showcase now draws its signs at `scale = 1`, which shows whole letters; if you put up your own signs, do the same until the engine fixes it. The kit itself draws no Text3D labels. - **#22121: a fresh install of economyKit can leave inventoryKit's parts failing to load** ("module 'inventoryKit.items' not found", or "module `~.items` ... has no root to resolve against"). It comes from the install of economyKit's own dependencies, not from this kit. In fresh worlds checked for earlier releases those lines stayed in the log for the whole session, and building, prices, refunds and coins all worked; if the kit's BuildMode or BuildPiece components say they are waiting for content, a scene reload (or reopening the world) brings them up. - **Showcase signs are English.** The kit itself speaks English and Brazilian Portuguese; the signs and painted words of this showcase world are scenery and are not translated. - **No structural collapse.** Taking down a wall leaves the roof on it standing; pieces do not fall. - **Ladders do not carry you up by themselves.** The default character controller has no climb state: walk into a ladder and jump, or use stairs and ramps (they are walkable). - **The storage chest opens and shuts but holds no items.** Pair it with inventoryKit (already installed with economyKit) if your game needs storage. - **The deciding machine is a player's machine**, as with economyKit's bank: a player alone in a world is their own decider, so a modified client playing alone can build for free. - **#14448**: two engines signed in to one account collide as one player, so a real two-player race for one spot could not be run by the author; it is covered by the tests (two requests through the deciding machine), and every placed piece was checked to be a synced entity the deciding machine owns. A second player on another account sees the same pieces. - **#20750**: the web build's frame rate drops in busy scenes; keep large bases to a few hundred pieces and lower the light budget on phones. - **#20946**: this kit was checked in the desktop engine; the browser build was not run by its author. - **#21420**: an install with several dependencies can be slow: economyKit brings several kits and the styles bring four material collections. A fresh-world install of the package alone has taken 7 s; a first install on a slow connection can take about a minute. - **#19849**: some ZeroMind calls (install, preview) can take a long time to answer. - **#19258**: the ZeroMind search description can lag a release. - **#22328: right after installing, the wallet can fail to start.** No wallet shows and build mode refuses every piece with "Not enough Coins: you need 20 more", and Stop and Play does not clear it. Close the world and open it again once after the install; everything then works and it does not come back. It shows most after installing several kits in a row, as the example guide does, and often follows a log line `package collision: 'economyKit' already registered at /zero/source/deps/...` while the install moves buildPlaceKit's copy of a kit to the world's top level. - **#22402: on the current engine, a package whose `package.yaml` writes its description as a folded block is refused at install.** You see the install fail with "... is not installed, because it does not run: 1 installed asset(s) do not load as their type: ... package.yaml is not valid YAML: yaml: line 3: block-scalar indicators (chomping/indentation) are not supported", and the world keeps nothing of the install. buildPlaceKit 1.0.16 and older are refused this way; 1.0.17 writes its description on one line and installs. economyKit 1.0.13 and juiceKit 1.2.8 are still refused when you install them on their own, so the example guide's step of installing them by name fails today; they arrive and run inside buildPlaceKit's own install all the same, and gridKit installs as usual.