[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E6GYBYBWDD37XGX2VC17S0":3,"skill-same:01M7E6GYBYBWDD37XGX2VC17S0":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7E6GYBYBWDD37XGX2VC17S0","game-data",null,"Use when a Godot game keeps items, enemies, levels, dialogue or balance numbers as data (Resources, JSON or CSV tables, spreadsheets), or when that data loads wrong, changes by itself or is missing from an export.","nick-vas\u002Fhyperdot","nick-vas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7181961?v=4","01M7E6F6F0BQ49V0JZHX9BXCBD","Nikolaos Vasilikiotis","01M7E6F6FZW8SW1AJ1S7ARFE89",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgame-data\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: game-data\ndescription: Use when a Godot game keeps items, enemies, levels, dialogue or balance numbers as data (Resources, JSON or CSV tables, spreadsheets), or when that data loads wrong, changes by itself or is missing from an export.\n---\n\n# Data-driven design in Godot 4 (C#)\n\nKeep what designers tune (numbers, lists, ids, references between them) out of code, check it in CI like code, and load\nit the same way in the editor, in tests and in the exported game. Every behaviour below was measured on Godot 4.7.2\nmono; sources: `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fdata.md`.\n\n## 1. Resources or tables\n\n| | `[GlobalClass]` Resources (`.tres`) | JSON or CSV tables |\n|---|---|---|\n| Best for | A few hand-tuned items tied to art and scenes | Many rows of numbers, tuned in a spreadsheet |\n| Editing | The inspector | A spreadsheet, exported to the repository |\n| Reviewing a change | Readable diffs | Readable diffs; one row per item |\n| Checked by the kit | Section 3 | The `data` runner (section 4) |\n| Mods and downloads | Never: a `.tres` runs scripts embedded in it | Yes, validated (`modding`) |\n\nEither way: every definition has a stable string `Id` (not a file name, not an index); references name ids; one loader,\nused by the game, tests and CI, reports every problem at once instead of stopping at the first.\n\nContent edited often (maps, waves, dialogue) deserves its own editor, a `@tool` script or a small plugin, so people\nother than the programmer can make it: Toru Hidaka's graphics, map and sound utilities let others make games at Enix\n(*Untold History*).\n\n## 2. The traps of custom Resources\n\n- **A loaded Resource is one shared object.** Two enemies with `[Export] Weapon` set to `axe.tres` hold the same\n  object; `a.Weapon.Damage += 5` changes `b` and every later `GD.Load(\"res:\u002F\u002Faxe.tres\")`. Definitions are read-only at\n  run time; per-instance state goes in a plain C# object built from the definition (`new WeaponState(def)`).\n- `ResourceLocalToScene` copies only when a scene is instantiated; two `GD.Load` calls still share.\n- `Duplicate(true)` keeps external sub-resources (another `.tres`) shared and drops fields that are not `[Export]`ed;\n  `Duplicate()` shares arrays. `DuplicateDeep(Resource.DeepDuplicateMode.All)` copies external ones too. Cost: 45 µs for\n  a small resource, 1.5 ms for a large one, against 5 µs for `new`; never duplicate per bullet.\n- **Renaming or removing an `[Export]` property loses data silently.** The old `.tres` loads with no warning (not even\n  with `--verbose`), the property gets its C# default, and the next save erases the old value. When renaming, edit\n  every `.tres` in the same commit (the keys are plain text) and check with the test below.\n- **Renaming a class or its file**: move the `.cs.uid` with the `.cs` (`git mv` both); a `.tres` without a `uid=` (any\n  written by `ResourceSaver.Save` in a running game) then fails to load and returns null.\n- **Values equal to the default are not written.** Changing a C# default silently changes every file that had it. Give\n  balance numbers no meaningful default (0, then validate).\n- **Inspector hints are not validation.** A hand-edited `.tres` loaded `Hp = 999` past `PropertyHint.Range \"0,100\"`, an\n  enum value 7 that does not exist, and `Speed = \"fast\"` on a float as 0, all without an error.\n- **Hot reload**: `GD.Load` returns the cached object after the file changes;\n  `ResourceLoader.Load(path, \"\", ResourceLoader.CacheMode.Replace)` reloads into the same object, so every holder sees\n  the new values. A debug \"reload data\" key can do this for changed files.\n\n## 3. Tests for Resources (in the game's test project)\n\n- every `.tres` under the data folders loads, non-null, of the expected class\n- every key in each `.tres` is a stored property of its class: parse the keys from the text and compare with\n  `GetPropertyList()` entries whose usage has `PropertyUsageFlags.Storage` (this alone catches renamed properties); the\n  kit's `validate` runner now does this for every `.tres` (`keeps spead, which EnemyStats no longer has`)\n- ids unique and matching `^[a-z0-9_]+$`; references resolve; no cycles where none belong (upgrade chains)\n- ranges from the `PropertyHint.Range` hint strings; enums with `Enum.IsDefined`\n- the game's balance rules from the GDD: damage rises with tier, drop weights sum above 0, every enemy beatable at the\n  level's expected player power\n- a cost curve: one formula, kept in one place, gives each item's benefits minus its costs; the test fails on any item\n  outside a stated band (the method of a game balance course's GDC talk)\n- chance tables: no negative weight, every probability within 0 and 1, the exclusive outcomes summing to exactly 1 (most\n  probability mistakes fail one of these); where the exact chance of an outcome is known, the seeded rate of `procgen`'s\n  \"Chances come out right\" test must agree with it\n\n## 4. Tables: JSON and CSV\n\n- **A `.csv` is imported as a translation by default**, even a table of enemies, and then the file itself is not in the\n  exported game. In the Import dock choose Import As > Keep File and commit its `.import` (`importer=\"keep\"`); read it\n  with `FileAccess.GetCsvLine()`, which handles quoted commas.\n- `.json` is exported as is. `.txt` and `.yaml` are exported only if the export preset's include filter names them.\n- A `.tres` is converted to binary in an export and appears as `name.tres.remap`, so a `DirAccess` scan for `*.tres`\n  finds nothing there. List with `ResourceLoader.ListDirectory(\"res:\u002F\u002Fdata\")` and load by path.\n- Godot's `Json` returns every number as a double (`10` is `10.0`; ids above 2^53 are corrupted), accepts trailing commas\n  and keeps the last of duplicate keys. Parse tables in C# with `System.Text.Json` into records; set\n  `UnmappedMemberHandling = JsonUnmappedMemberHandling.Disallow` so a misspelt field fails.\n- Parse numbers with `CultureInfo.InvariantCulture`: `float.Parse(\"0.5\")` gives 5 on a German system, inside Godot too,\n  and CI machines never show it; the `architecture` runner warns (`culture-parse`).\n\n### The `data` runner\n\n`data.json` in the project describes each table; the `data` runner (picked automatically when the file exists) checks\nevery row without Godot and writes one JUnit case per table:\n\n```json\n{ \"tables\": {\n    \"items\":   { \"file\": \"data\u002Fitems.json\", \"id\": \"id\",\n                 \"fields\": { \"price\": { \"type\": \"int\", \"min\": 0 }, \"rarity\": { \"enum\": [\"common\", \"rare\"] } } },\n    \"enemies\": { \"file\": \"data\u002Fenemies.csv\", \"id\": \"id\",\n                 \"fields\": { \"hp\": { \"type\": \"int\", \"min\": 1 }, \"drops\": { \"ref\": \"items\", \"list\": true },\n                             \"boss\": { \"type\": \"bool\", \"optional\": true } } } } }\n```\n\n- It catches: duplicate or missing ids, wrong types, values out of range or not in the enum, references to ids that do\n  not exist, unknown columns (typos in a header), and a CSV still imported as a translation; a mistyped id, enum value,\n  column or table comes with the near name (\"did you mean 'mining'?\").\n- Field rules: `type` (string, int, number, bool), `min`, `max`, `enum`, `pattern`, `ref`, `list` (`;` between values\n  in a CSV cell), `optional`, `acyclic` (on a `ref` to its own table: prerequisites that loop, as in a tech tree,\n  `algorithms`); `\"extra\": \"allow\"` on a table permits unlisted columns.\n- Across rows: `\"totals\"` on a table (what a zone's quests give must reach its next level: `progression`) and\n  `\"names\"` at the top level (misspelt proper nouns in dialogue, translations and scenes: `narrative`);\n  `\"economy\": { \"currency\": ..., \"rate\": ... }` on a table of flows per hour fails a currency with no sink\n  (`progression`).\n- Dialogue rules: a table of `\"kind\": \"responses\"` (`narrative` section 4), with `\"locales\"` for lines missing a\n  translation; `\"type\": \"criteria\"` checks the same criteria grammar (`health\u003C25;!seen_tank`) in any table, such as quest\n  or unlock conditions.\n- Soft-locks: a table of `\"kind\": \"softlock\"`, levels as areas, passages, pickups, supplies and goals, searched like\n  `SoftLockCheck` in C# (`game-playtest` section 6), so GDScript games get it too.\n- Run it alone: `pwsh ${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Fhyperdot.ps1 test -Json -Quiet -Runners data`.\n- Puzzle levels: `game-design` section 6 has a `levels` table that requires a one-sentence solution and a purpose\n  for every level.\n\n## 5. Spreadsheets\n\n- One direction only: the sheet, then an export (a script or a downloaded CSV) committed to the repository, then the\n  game. Never hand-edit the export; commit it so a review shows every balance change.\n- Keep derived columns (damage per second, time to kill) in the sheet; export only the inputs.\n- Feature switches are data too, so a feature can be turned off for a test (DayZ). Values tuned around a bug break when\n  it is fixed: retune after fixes, and keep whole-system regression runs (IL-2).\n- Print a digest of all data tables in the game's log and in bug reports, so a report says which balance it ran.\n- Balance downloaded from a server (rebalancing without a patch; a Sony online consultant's GDC advice) is data only:\n  JSON or CSV parsed into the same records and checked by the same rules, never a `.tres`, a script or an expression,\n  which would be a way in for an attacker. The shipped tables stay the fallback, so the game plays offline with\n  whatever version it has; apply a download between missions or runs, never mid-mission; write its version into saves.\n\n## 6. Placed objects: every one, every run\n\nAnyone breaks placed content, often far from where they worked: a prop's collision fix moves AI points off the navmesh\nin every level that uses the prop, a navmesh change drops the slopes, a code change lowers a limit. Check every placed\nnode of every level in each test run instead of by hand (Assassin's Creed Origins: 228 zip lines at two minutes each is\na tester's full day; `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fgdc\u002Fassassins-creed-origins-world-data.md`).\n\nWrite a `placement.json` and the `placement` runner checks every level in each `test` run, no test to write:\n`{ \"levels\": [\"res:\u002F\u002Flevels\"], \"limits\": { \"reach\": \"res:\u002F\u002Fplayer.gd:REACH\" } }`, each limit read from the GDScript\nconstant it names, in GDScript or C# (`\"res:\u002F\u002FTuning.cs:Reach\"`: a `const` or `static readonly` set to a literal or arithmetic on other such fields). Or copy\n`${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Ftemplates\u002Fplacement_check.gd` into the game's test folder and call it from a GUT test\n(its header has the code). It loads each level, waits for navigation, checks nodes by group and reports one line per\nfinding: scene, node path, position, rule, measured value and limit.\n\n| Group | Rule | Passes when |\n|---|---|---|\n| `ai_point` | `navmesh_below` | navmesh is at most 0.5 m straight below |\n| | `path_to_link` | a path reaches each node in its `links` metadata |\n| `interactable` | `ground_in_reach` | a ray down hits ground within the player's reach |\n| `zipline` | `zipline_clear` | a capsule swept under the rope to its `End` child hits nothing |\n| | `zipline_angle` | the rope is no steeper than the movement code allows |\n| `landmark` | `landmark_still` | it is no moving body and did not move in 30 physics frames |\n| | `landmark_seen` | it is in view ahead from at least two separate stretches of the `route` paths |\n| `route` (a `Path3D`) | `landmark_ahead` | walked each way (metadata `one_way` skips the way back), a landmark is in view ahead on a quarter of it |\n\n- The wayfinding rules and why they matter: `game-design` section 7. They aim at a landmark's `Marker3D` children\n  (the top of a tower), from `eye_height` within `view_fov`; only what has collision hides a landmark.\n- **Limits come from gameplay code**: `check.reach = Player.REACH` with `const Player := preload(\"res:\u002F\u002Fplayer.gd\")`.\n  A copied number keeps passing after the code changes; yesterday's valid zip line must fail the day the limit drops.\n- **A bug found once becomes a rule for its whole type**: one torch out of reach means a check of every torch.\n- **Prove each rule on a broken fixture before trusting it.** A false positive sends someone looking for nothing, and\n  they stop reading the report. Two traps the kit's fixture caught: before the map syncs, `map_get_closest_point`\n  returns (0, 0, 0), so a probe at the origin looks ready early (wait for `map_get_closest_point_owner` to be valid);\n  `map_get_path` to another navmesh island returns a path to the nearest reachable point, so compare where it ends.\n- **Exemptions are visible**: node metadata `placement_skip = {\"zipline_clear\": \"the crate breaks\"}`; the summary lists\n  each with its reason, and one without a reason is a finding.\n- **One summary with the change per type since the last run** (`counts_file`; keep the file between runs). The talk's\n  most useful line was \"ladders +500\", seen before anyone complained.\n- On 4.7.2 headless, navigation answered after 9 to 11 physics frames for the first level of a GUT run and 3 or 4 for\n  the next; the helper polls, capped. The checks take about 10 ms per 1,000 nodes.\n- A check at commit time does not replace the full run: data fine on day one breaks on day ten through another change.\n- Run it: `pwsh ${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Fhyperdot.ps1 test -Json -Quiet -Runners gut -Filter test_every_level`.\n","# Data-driven design in Godot 4 (C#)\n\nKeep what designers tune (numbers, lists, ids, references between them) out of code, check it in CI like code, and load\nit the same way in the editor, in tests and in the exported game. Every behaviour below was measured on Godot 4.7.2\nmono; sources: `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fdata.md`.\n\n## 1. Resources or tables\n\n| | `[GlobalClass]` Resources (`.tres`) | JSON or CSV tables |\n|---|---|---|\n| Best for | A few hand-tuned items tied to art and scenes | Many rows of numbers, tuned in a spreadsheet |\n| Editing | The inspector | A spreadsheet, exported to the repository |\n| Reviewing a change | Readable diffs | Readable diffs; one row per item |\n| Checked by the kit | Section 3 | The `data` runner (section 4) |\n| Mods and downloads | Never: a `.tres` runs scripts embedded in it | Yes, validated (`modding`) |\n\nEither way: every definition has a stable string `Id` (not a file name, not an index); references name ids; one loader,\nused by the game, tests and CI, reports every problem at once instead of stopping at the first.\n\nContent edited often (maps, waves, dialogue) deserves its own editor, a `@tool` script or a small plugin, so people\nother than the programmer can make it: Toru Hidaka's graphics, map and sound utilities let others make games at Enix\n(*Untold History*).\n\n## 2. The traps of custom Resources\n\n- **A loaded Resource is one shared object.** Two enemies with `[Export] Weapon` set to `axe.tres` hold the same\n  object; `a.Weapon.Damage += 5` changes `b` and every later `GD.Load(\"res:\u002F\u002Faxe.tres\")`. Definitions are read-only at\n  run time; per-instance state goes in a plain C# object built from the definition (`new WeaponState(def)`).\n- `ResourceLocalToScene` copies only when a scene is instantiated; two `GD.Load` calls still share.\n- `Duplicate(true)` keeps external sub-resources (another `.tres`) shared and drops fields that are not `[Export]`ed;\n  `Duplicate()` shares arrays. `DuplicateDeep(Resource.DeepDuplicateMode.All)` copies external ones too. Cost: 45 µs for\n  a small resource, 1.5 ms for a large one, against 5 µs for `new`; never duplicate per bullet.\n- **Renaming or removing an `[Export]` property loses data silently.** The old `.tres` loads with no warning (not even\n  with `--verbose`), the property gets its C# default, and the next save erases the old value. When renaming, edit\n  every `.tres` in the same commit (the keys are plain text) and check with the test below.\n- **Renaming a class or its file**: move the `.cs.uid` with the `.cs` (`git mv` both); a `.tres` without a `uid=` (any\n  written by `ResourceSaver.Save` in a running game) then fails to load and returns null.\n- **Values equal to the default are not written.** Changing a C# default silently changes every file that had it. Give\n  balance numbers no meaningful default (0, then validate).\n- **Inspector hints are not validation.** A hand-edited `.tres` loaded `Hp = 999` past `PropertyHint.Range \"0,100\"`, an\n  enum value 7 that does not exist, and `Speed = \"fast\"` on a float as 0, all without an error.\n- **Hot reload**: `GD.Load` returns the cached object after the file changes;\n  `ResourceLoader.Load(path, \"\", ResourceLoader.CacheMode.Replace)` reloads into the same object, so every holder sees\n  the new values. A debug \"reload data\" key can do this for changed files.\n\n## 3. Tests for Resources (in the game's test project)\n\n- every `.tres` under the data folders loads, non-null, of the expected class\n- every key in each `.tres` is a stored property of its class: parse the keys from the text and compare with\n  `GetPropertyList()` entries whose usage has `PropertyUsageFlags.Storage` (this alone catches renamed properties); the\n  kit's `validate` runner now does this for every `.tres` (`keeps spead, which EnemyStats no longer has`)\n- ids unique and matching `^[a-z0-9_]+$`; references resolve; no cycles where none belong (upgrade chains)\n- ranges from the `PropertyHint.Range` hint strings; enums with `Enum.IsDefined`\n- the game's balance rules from the GDD: damage rises with tier, drop weights sum above 0, every enemy beatable at the\n  level's expected player power\n- a cost curve: one formula, kept in one place, gives each item's benefits minus its costs; the test fails on any item\n  outside a stated band (the method of a game balance course's GDC talk)\n- chance tables: no negative weight, every probability within 0 and 1, the exclusive outcomes summing to exactly 1 (most\n  probability mistakes fail one of these); where the exact chance of an outcome is known, the seeded rate of `procgen`'s\n  \"Chances come out right\" test must agree with it\n\n## 4. Tables: JSON and CSV\n\n- **A `.csv` is imported as a translation by default**, even a table of enemies, and then the file itself is not in the\n  exported game. In the Import dock choose Import As > Keep File and commit its `.import` (`importer=\"keep\"`); read it\n  with `FileAccess.GetCsvLine()`, which handles quoted commas.\n- `.json` is exported as is. `.txt` and `.yaml` are exported only if the export preset's include filter names them.\n- A `.tres` is converted to binary in an export and appears as `name.tres.remap`, so a `DirAccess` scan for `*.tres`\n  finds nothing there. List with `ResourceLoader.ListDirectory(\"res:\u002F\u002Fdata\")` and load by path.\n- Godot's `Json` returns every number as a double (`10` is `10.0`; ids above 2^53 are corrupted), accepts trailing commas\n  and keeps the last of duplicate keys. Parse tables in C# with `System.Text.Json` into records; set\n  `UnmappedMemberHandling = JsonUnmappedMemberHandling.Disallow` so a misspelt field fails.\n- Parse numbers with `CultureInfo.InvariantCulture`: `float.Parse(\"0.5\")` gives 5 on a German system, inside Godot too,\n  and CI machines never show it; the `architecture` runner warns (`culture-parse`).\n\n### The `data` runner\n\n`data.json` in the project describes each table; the `data` runner (picked automatically when the file exists) checks\nevery row without Godot and writes one JUnit case per table:\n\n```json\n{ \"tables\": {\n    \"items\":   { \"file\": \"data\u002Fitems.json\", \"id\": \"id\",\n                 \"fields\": { \"price\": { \"type\": \"int\", \"min\": 0 }, \"rarity\": { \"enum\": [\"common\", \"rare\"] } } },\n    \"enemies\": { \"file\": \"data\u002Fenemies.csv\", \"id\": \"id\",\n                 \"fields\": { \"hp\": { \"type\": \"int\", \"min\": 1 }, \"drops\": { \"ref\": \"items\", \"list\": true },\n                             \"boss\": { \"type\": \"bool\", \"optional\": true } } } } }\n```\n\n- It catches: duplicate or missing ids, wrong types, values out of range or not in the enum, references to ids that do\n  not exist, unknown columns (typos in a header), and a CSV still imported as a translation; a mistyped id, enum value,\n  column or table comes with the near name (\"did you mean 'mining'?\").\n- Field rules: `type` (string, int, number, bool), `min`, `max`, `enum`, `pattern`, `ref`, `list` (`;` between values\n  in a CSV cell), `optional`, `acyclic` (on a `ref` to its own table: prerequisites that loop, as in a tech tree,\n  `algorithms`); `\"extra\": \"allow\"` on a table permits unlisted columns.\n- Across rows: `\"totals\"` on a table (what a zone's quests give must reach its next level: `progression`) and\n  `\"names\"` at the top level (misspelt proper nouns in dialogue, translations and scenes: `narrative`);\n  `\"economy\": { \"currency\": ..., \"rate\": ... }` on a table of flows per hour fails a currency with no sink\n  (`progression`).\n- Dialogue rules: a table of `\"kind\": \"responses\"` (`narrative` section 4), with `\"locales\"` for lines missing a\n  translation; `\"type\": \"criteria\"` checks the same criteria grammar (`health\u003C25;!seen_tank`) in any table, such as quest\n  or unlock conditions.\n- Soft-locks: a table of `\"kind\": \"softlock\"`, levels as areas, passages, pickups, supplies and goals, searched like\n  `SoftLockCheck` in C# (`game-playtest` section 6), so GDScript games get it too.\n- Run it alone: `pwsh ${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Fhyperdot.ps1 test -Json -Quiet -Runners data`.\n- Puzzle levels: `game-design` section 6 has a `levels` table that requires a one-sentence solution and a purpose\n  for every level.\n\n## 5. Spreadsheets\n\n- One direction only: the sheet, then an export (a script or a downloaded CSV) committed to the repository, then the\n  game. Never hand-edit the export; commit it so a review shows every balance change.\n- Keep derived columns (damage per second, time to kill) in the sheet; export only the inputs.\n- Feature switches are data too, so a feature can be turned off for a test (DayZ). Values tuned around a bug break when\n  it is fixed: retune after fixes, and keep whole-system regression runs (IL-2).\n- Print a digest of all data tables in the game's log and in bug reports, so a report says which balance it ran.\n- Balance downloaded from a server (rebalancing without a patch; a Sony online consultant's GDC advice) is data only:\n  JSON or CSV parsed into the same records and checked by the same rules, never a `.tres`, a script or an expression,\n  which would be a way in for an attacker. The shipped tables stay the fallback, so the game plays offline with\n  whatever version it has; apply a download between missions or runs, never mid-mission; write its version into saves.\n\n## 6. Placed objects: every one, every run\n\nAnyone breaks placed content, often far from where they worked: a prop's collision fix moves AI points off the navmesh\nin every level that uses the prop, a navmesh change drops the slopes, a code change lowers a limit. Check every placed\nnode of every level in each test run instead of by hand (Assassin's Creed Origins: 228 zip lines at two minutes each is\na tester's full day; `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fgdc\u002Fassassins-creed-origins-world-data.md`).\n\nWrite a `placement.json` and the `placement` runner checks every level in each `test` run, no test to write:\n`{ \"levels\": [\"res:\u002F\u002Flevels\"], \"limits\": { \"reach\": \"res:\u002F\u002Fplayer.gd:REACH\" } }`, each limit read from the GDScript\nconstant it names, in GDScript or C# (`\"res:\u002F\u002FTuning.cs:Reach\"`: a `const` or `static readonly` set to a literal or arithmetic on other such fields). Or copy\n`${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Ftemplates\u002Fplacement_check.gd` into the game's test folder and call it from a GUT test\n(its header has the code). It loads each level, waits for navigation, checks nodes by group and reports one line per\nfinding: scene, node path, position, rule, measured value and limit.\n\n| Group | Rule | Passes when |\n|---|---|---|\n| `ai_point` | `navmesh_below` | navmesh is at most 0.5 m straight below |\n| | `path_to_link` | a path reaches each node in its `links` metadata |\n| `interactable` | `ground_in_reach` | a ray down hits ground within the player's reach |\n| `zipline` | `zipline_clear` | a capsule swept under the rope to its `End` child hits nothing |\n| | `zipline_angle` | the rope is no steeper than the movement code allows |\n| `landmark` | `landmark_still` | it is no moving body and did not move in 30 physics frames |\n| | `landmark_seen` | it is in view ahead from at least two separate stretches of the `route` paths |\n| `route` (a `Path3D`) | `landmark_ahead` | walked each way (metadata `one_way` skips the way back), a landmark is in view ahead on a quarter of it |\n\n- The wayfinding rules and why they matter: `game-design` section 7. They aim at a landmark's `Marker3D` children\n  (the top of a tower), from `eye_height` within `view_fov`; only what has collision hides a landmark.\n- **Limits come from gameplay code**: `check.reach = Player.REACH` with `const Player := preload(\"res:\u002F\u002Fplayer.gd\")`.\n  A copied number keeps passing after the code changes; yesterday's valid zip line must fail the day the limit drops.\n- **A bug found once becomes a rule for its whole type**: one torch out of reach means a check of every torch.\n- **Prove each rule on a broken fixture before trusting it.** A false positive sends someone looking for nothing, and\n  they stop reading the report. Two traps the kit's fixture caught: before the map syncs, `map_get_closest_point`\n  returns (0, 0, 0), so a probe at the origin looks ready early (wait for `map_get_closest_point_owner` to be valid);\n  `map_get_path` to another navmesh island returns a path to the nearest reachable point, so compare where it ends.\n- **Exemptions are visible**: node metadata `placement_skip = {\"zipline_clear\": \"the crate breaks\"}`; the summary lists\n  each with its reason, and one without a reason is a finding.\n- **One summary with the change per type since the last run** (`counts_file`; keep the file between runs). The talk's\n  most useful line was \"ladders +500\", seen before anyone complained.\n- On 4.7.2 headless, navigation answered after 9 to 11 physics frames for the first level of a GUT run and 3 or 4 for\n  the next; the helper polls, capped. The checks take about 10 ms per 1,000 nodes.\n- A check at commit time does not replace the full run: data fine on day one breaks on day ten through another change.\n- Run it: `pwsh ${CLAUDE_PLUGIN_ROOT}\u002Fci\u002Fgodot\u002Fhyperdot.ps1 test -Json -Quiet -Runners gut -Filter test_every_level`.\n",{"name":5,"description":7},"main","5fa4c2262d814d50f72198a95b8c483ff195f90f",".agents\u002Fskills\u002Fgame-data",0,"https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot","https:\u002F\u002Fnick-vas.github.io\u002Fhyperdot\u002F","https:\u002F\u002Fgithub.com\u002Fnick-vas","https:\u002F\u002Fcommon-beef.itch.io\u002F","2026-11-13 18:55:29",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add nick-vas\u002Fhyperdot --skill game-data",{"tool":39,"command":40},"bunx","bunx skills add nick-vas\u002Fhyperdot --skill game-data",{"tool":42,"command":43},"pnpm","pnpm dlx skills add nick-vas\u002Fhyperdot --skill game-data","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgame-data\u002FSKILL.md",true,[],[48,55,61,68,75,82],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7E6RF2S03S92PB9RZB4S4W0","over-budget","Use when a fixture exceeds the size budget.","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002Ftests\u002Fskill-fixtures\u002Fover-budget\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7E6RBY8SDNMA3ZARE8MAH0G","bad-yaml","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002Ftests\u002Fskill-fixtures\u002Fbad-yaml\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7E6R9S9YHTC552SR41RQAJ1","bad-workflow-description","Use when testing; runs the kit and then reads the JSON.","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002Ftests\u002Fskill-fixtures\u002Fbad-workflow-description\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7E6R6CWSAN48C80130CM1AK","bad-version","Use when a fixture quotes a stale package version.","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002Ftests\u002Fskill-fixtures\u002Fbad-version\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7E6R2C0E24TC133ESHKZT9R","bad-value","Use when a fixture passes a value outside a parameter's set.","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002Ftests\u002Fskill-fixtures\u002Fbad-value\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7E6QYM81V061X7DSQ94CZRP","bad-trigger","Helps with Godot tests.","https:\u002F\u002Fgithub.com\u002Fnick-vas\u002Fhyperdot\u002Fblob\u002Fmain\u002Ftests\u002Fskill-fixtures\u002Fbad-trigger\u002FSKILL.md",[],[]]