[High] [Task] [WIP/Incomplete] Golemancy system is "spec-defined, implementation pending" — golem combat disconnected from pipeline #276

New Issue

2026-06-05T02:10:52+02:00

Anexim commented

2026-06-05 02:10:52 +02:00

Type: Work in progress / Incomplete feature
Priority: High

golemancy-spec.md §0 explicitly states:

⚠ Spec-defined, implementation pending. This spec is based on docs/specs/spire-combat-spec.md §9 and represents the intended design. The current code has golem data defined but disconnected from the combat pipeline.

golemancy-spec.md §11 Known Gaps:

Feature	Status
Golem data definitions	✅ Complete (10 golems in `data/golems/`)
Golem loadout UI	✅ Partial (GolemancyTab exists)
Summoning on room entry	❌ Not wired into combat tick
Maintenance cost per tick	❌ Not wired into combat tick
Room duration tracking	❌ Not wired into room clear
Golem combat (attack timer)	❌ Not wired into combat tick
Golemancy combat pipeline	❌ `golem-combat-actions.ts` exists but disconnected

spire-combat-spec.md §9 also notes:

| Feature | Status |
| Golemancy combat | Full golem data exists | Disconnected |

The golemancy system has full data definitions but the entire runtime pipeline is disconnected. This is a major incomplete feature.

Recommendation: Wire the golemancy system into the combat tick pipeline. This includes: summoning on room entry, maintenance cost deduction, attack timers, room duration tracking, and dismissal logic.

**Type:** Work in progress / Incomplete feature **Priority:** High **golemancy-spec.md §0** explicitly states: > **⚠ Spec-defined, implementation pending.** This spec is based on `docs/specs/spire-combat-spec.md` §9 and represents the intended design. The current code has golem data defined but disconnected from the combat pipeline. **golemancy-spec.md §11** Known Gaps: | Feature | Status | |---------|--------| | Golem data definitions | ✅ Complete (10 golems in `data/golems/`) | | Golem loadout UI | ✅ Partial (GolemancyTab exists) | | Summoning on room entry | ❌ Not wired into combat tick | | Maintenance cost per tick | ❌ Not wired into combat tick | | Room duration tracking | ❌ Not wired into room clear | | Golem combat (attack timer) | ❌ Not wired into combat tick | | Golemancy combat pipeline | ❌ `golem-combat-actions.ts` exists but disconnected | **spire-combat-spec.md §9** also notes: > | Feature | Status | > | Golemancy combat | Full golem data exists | Disconnected | The golemancy system has full data definitions but the entire runtime pipeline is disconnected. This is a major incomplete feature. **Recommendation:** Wire the golemancy system into the combat tick pipeline. This includes: summoning on room entry, maintenance cost deduction, attack timers, room duration tracking, and dismissal logic.

Anexim added the ai:todo label 2026-06-05 02:10:52 +02:00

n8n-gitea was assigned by Anexim

2026-06-05 02:10:52 +02:00

Anexim commented

2026-06-05 13:12:48 +02:00

ultimate truth: the golemancy system should have already be implemented, but undergoing major refactoring, see comment on gitea issue #268

Anexim closed this issue

2026-06-05 14:30:26 +02:00

Anexim added ai:done and removed ai:todo labels 2026-06-05 14:30:26 +02:00

Anexim commented

2026-06-05 14:30:26 +02:00

✅ RESOLVED (status updated) — Updated golemancy-spec.md to reflect the full redesign status. The golemancy system data definitions exist but are disconnected from the combat pipeline. Awaiting the new component-based construction system redesign (see issue #268).

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Anexim/Mana-Loop#276