# Design This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold. ## Classic table (excerpt) The full file is `tables/classic.json`. Tests read that file. The excerpt is the part the screenshots and the first-combo fixture use. Starting ids: `fire`, `water`, `earth`, `air`. | A | B | Product | Label | | --- | --- | --- | --- | | fire | water | steam | Steam | | water | earth | mud | Mud | | earth | air | dust | Dust | | fire | earth | lava | Lava | | fire | air | smoke | Smoke | | water | air | cloud | Cloud | | steam | air | rain | Rain | | lava | water | stone | Stone | | rain | earth | plant | Plant | | plant | fire | ash | Ash | A pair not in the file is a miss. The kitchen table (`tables/kitchen.json`) has a different starting pack (`flour`, `water`, `salt`, `heat`) and its own products. It must contain at least 20 recipes so the same tests can run against a second file. ## Fixtures - First combo: drag `fire` onto `water` (or the other way). Product `steam`. Screenshot `first-combo`. - Discovery list: after steam, mud and lava, with `discoveries` on. Screenshot `discovered-list`. - Rare recipe: plant then ash, screenshot `rare-recipe`. - Miss: `fire` onto `fire` (classic table has no such recipe). ## Screenshot tolerance Same as other nova games: each channel within 8 levels, 98% of pixels. Positions of tiles at the start are the four corners of a 2 by 2 cell in the middle of the bench, in pack order, as `design.md` coordinates: | Id | x | y | | --- | --- | --- | | first | 200 | 200 | | second | 360 | 200 | | third | 200 | 360 | | fourth | 360 | 360 | Coordinates are the top-left of the 120 by 120 tile, on a 1600 by 1000 desktop frame. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | What can you make? | Shown at the top. | | `starting_pack` | Starting pack | fire,water,earth,air | Comma-separated ids from the recipe table that appear at the start. | | `discoveries` | List discoveries | on | A side list of everything made so far. | | `duplicates` | Allow extra copies | on | A second copy of an element can be dragged out from the bench. | | `table` | Recipe table | classic | classic starts from the four elements. kitchen starts from pantry staples. | ## Acceptance at the defaults The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins. | Fixture | Role | | --- | --- | | `design.md` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `tables/classic.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `tables/kitchen.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy. ## Screenshots These pictures are headless-Chrome captures of the working reference in `reference/preview.html`, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel. | File | What it shows | | --- | --- | | `shots/bench.png` | Fire and water on the table just became steam, a new discovery. | ## How to verify 1. Run the checks at the default inputs, without a network. 2. Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file. 3. Repeat once at the person's inputs when they differ from the defaults. 4. A frozen recipe table, never a live model, returns the specified product for each fixture pair and a miss for an unknown pair. Order of the two inputs does not matter. UI tests cover drag-combine and take a golden screenshot of a known combo. No network is used in the checks.