- What we wanted to create
- We wanted an original six-limbed forest creature that a player could notice, understand and safely retreat from. Its broad, low skull, sensory quills and mineral plates came from a written creature brief.
- Why we chose it
- A fair encounter gives clues before danger. The Veyr raises its plates before a lunge. The player can guard, dodge or take a quieter route; defeating every creature is not the only way forward.
- Tools we used
- We used Blender 4.5 LTS for the model and animations, Three.js for the moving 3D scene, TypeScript for the rules, GitHub for review, and unit tests and Playwright for checks.
- What we made
- The recorded asset was built from written shape rules using a Blender script. A hand-drawn Veyr sketch is not recorded. Sketches can help explore a silhouette, but they do not turn into a game automatically: this prototype needs a mesh, a skeleton, animation clips and code.
- How AI helped
- Codex assisted with source code, asset scripts and checks. Its exact model and reasoning settings were not recorded for these assets. AI suggestions still needed inspection, tests and corrections; the model did not decide that the game was ready to release.
- The problem to watch for
- A moving mesh and working rules can disagree. The project also found that a late interaction could use an old on-screen marker prompt after a pause or restart. Passing an art export check would not catch that gameplay bug.
- How we approached it
- The game keeps its animation files separate from its decision rules. Marker interaction now checks whether the game is paused, whether the player can act, and where the player is right now. We added regression checks for the late input.
- How we tested it
- The creature prototype has been checked for six-limb rigs, animation clips, movement, sight, pursuit, warning, damage, defence, retreat, restart and route isolation. Separate save checks reject malformed or future-version data and test a real browser reload. Physical-phone and human learner reviews remain separate; this lesson does not certify the full game.
- What you can try
- In the decision room below, move an imaginary player nearer, put a wall in the way, and advance one decision at a time. Try removing the warning rule. Explain why a fair attack needs a warning before you restore it.
- What comes next
- Next we will refine movement and visual intersections, review the lessons with a human learner and check physical phones where available. The full chapter, cloud saves and game launch still have their own acceptance gates.