Files
sor/gameplay-todo.md
b442ed3d9c ci: switch registry to registry.aeternalisgames.com, rename host image sor-server
- REGISTRY: harbor.aeternalisgames.com → registry.aeternalisgames.com
- Host image: sor-host → sor-server (sor-admin unchanged)
- Remove stale TODO comments from k8s manifests
- Update harbor-pull-secret template with new registry hostname
- Update gameplay-effects-gap.md and gameplay-todo.md to reflect
  completed implementation work

Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)

Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
2026-02-26 23:12:13 -05:00

1.2 KiB

Gameplay TODO

Aura transition walkthrough scenario (movement)

Goal scenario: "A spirit moves on the battlefield and another spirit enters its aura range."

Current flow in engine

  1. GameEngine.MoveUnit(...) validates movement/path/MP.
  2. Unit position is updated on board.
  3. AbilitySystem.EvaluateAuraTransitions(state, movingUnitId, from, to) runs.
  4. System checks both:
    • stationary aura units vs moving unit transition
    • moving unit's own aura vs stationary units
  5. If range crossing occurs:
    • outside -> inside => EnterAuraRange trigger fires
    • inside -> outside => LeaveAuraRange trigger fires
  6. Triggered abilities are evaluated via FireTrigger(...) and matching triggered actions execute.

Test case outline

  • Place Aura Spirit A (with AuraRange 1..1 and an OnEnterAuraRange trigger).
  • Place Spirit B outside A's range.
  • Move B one tile so Manhattan distance to A becomes 1.
  • Expected:
    • EnterAuraRange trigger emitted with SourceId=A, TargetId=B.
    • Any matching triggered actions on A resolve.

Notes

  • Aura enter/leave also has dedicated helpers for summon/death transitions:
    • EvaluateAurasOnEnter(...)
    • EvaluateAurasOnLeave(...)