Skip to content

MARKDOWN SOURCE

Raw
# Agent notes

## Castle kit is not unit-scale art

`assets/castle_objects` (walls, towers, gate, and the other pieces under
`MODEL_DIR` in `src/assets.js`) is too low resolution to stand in for a
battlefield unit, and it must not be used as one.

- Do not treat a castle module as "unit 1" or as a hex-sized object. Do not
  size, place, or scale kit pieces to represent units, tiles, or props on the
  hex grid.
- The castle ring in `BattleView` (`CASTLE_SCALE`, `WALLS_ACROSS`, `WALLS_DEEP`
  in `src/view.js`) is built from many smaller pieces, each scaled down, so the
  whole ring keeps the same overall size. That is the intended build. Keep the
  footprint the same when changing the scale: more pieces at a smaller scale.
- If a new feature needs a wall, gate, or building, ask the user first. Do not
  assemble it from castle pieces without approval.

Heroine models (`HERO_MODEL_FILES`) and the procedural enemy silhouettes are the
unit art. Keep castle pieces to set dressing that the user has approved.

Agent notes

Castle kit is not unit-scale art

assets/castle_objects (walls, towers, gate, and the other pieces under MODEL_DIR in src/assets.js) is too low resolution to stand in for a battlefield unit, and it must not be used as one.

  • Do not treat a castle module as "unit 1" or as a hex-sized object. Do not size, place, or scale kit pieces to represent units, tiles, or props on the hex grid.
  • The castle ring in BattleView (CASTLE_SCALE, WALLS_ACROSS, WALLS_DEEP in src/view.js) is built from many smaller pieces, each scaled down, so the whole ring keeps the same overall size. That is the intended build. Keep the footprint the same when changing the scale: more pieces at a smaller scale.
  • If a new feature needs a wall, gate, or building, ask the user first. Do not assemble it from castle pieces without approval.

Heroine models (HERO_MODEL_FILES) and the procedural enemy silhouettes are the unit art. Keep castle pieces to set dressing that the user has approved.