[NG] Surface the 5-character cap in character creation UI #939

Closed
opened 2026-08-06 16:11:58 +00:00 by spikerj · 1 comment
Owner

Part of the Game Unification lane: all games become one game — different modes over one shared persistent universe (space → scan → hex-TD conquest → voxel base → satellite logistics → dungeon portals). Clients = Angular web + Godot (iOS/Android embed Godot). Full plan: ~/.claude/plans/i-want-a-plan-breezy-eclipse.md on the 4090.

Part of EPIC #926.

Handle the new CharacterCreationFailed reason in the dungeon-crawler character-creation HUD.

Part of the **Game Unification** lane: all games become one game — different modes over one shared persistent universe (space → scan → hex-TD conquest → voxel base → satellite logistics → dungeon portals). Clients = Angular web + Godot (iOS/Android embed Godot). Full plan: `~/.claude/plans/i-want-a-plan-breezy-eclipse.md` on the 4090. Part of EPIC #926. Handle the new `CharacterCreationFailed` reason in the dungeon-crawler character-creation HUD.
spikerj added the agenticenhancement labels 2026-08-06 16:11:58 +00:00
Author
Owner

Migrated to spikerj/spikersoft-angular#657 as part of the umbrella-tracker breakup.

Verified 2026-08-07 against the synced default branch.

  • Code: spikersoft-angular@8e5a4048 — a generic CharacterCreationFailed path already exists in projects/spikersoft/src/app/_components/_games/dungeon-crawler/dungeon-crawler.component.ts (subscription at :7713, server handler handleCharacterCreationFailedFromServer at :7325, SignalR handler at :7377), but it surfaces the failure with a bare alert(transloco.translate("games.dungeonCrawler.runtime.alerts.characterCreationFailed")) and then bounces back to the character-select modal. dungeon-crawler/hud/character-creation-hud.ts has no error surface at all. There is no cap-specific handling — and the server-side cap does not exist yet either (rg 'MaxCharacters|CharacterLimit' over spikersoft-backend returns nothing).
  • Live: Nothing runtime-observable — the 5-character cap reason is not emitted by the server yet.

Status: not started — nothing to preserve beyond the ticket text, which is carried over verbatim.

Closing here. Work now lives in the repo that holds the fix, so fixes #657 in a PR will
auto-close it on merge. The umbrella tracker keeps cross-repo epics only (parent epic
spikerj/spikersoft-issues#926 is untouched).

— Opus 5 Agent

Migrated to **spikerj/spikersoft-angular#657** as part of the umbrella-tracker breakup. Verified 2026-08-07 against the synced default branch. - **Code:** `spikersoft-angular@8e5a4048` — a **generic** `CharacterCreationFailed` path already exists in `projects/spikersoft/src/app/_components/_games/dungeon-crawler/dungeon-crawler.component.ts` (subscription at `:7713`, server handler `handleCharacterCreationFailedFromServer` at `:7325`, SignalR handler at `:7377`), but it surfaces the failure with a bare `alert(transloco.translate("games.dungeonCrawler.runtime.alerts.characterCreationFailed"))` and then bounces back to the character-select modal. `dungeon-crawler/hud/character-creation-hud.ts` has **no error surface at all**. There is no cap-specific handling — and the server-side cap does not exist yet either (`rg 'MaxCharacters|CharacterLimit'` over spikersoft-backend returns nothing). - **Live:** Nothing runtime-observable — the 5-character cap reason is not emitted by the server yet. Status: **not started** — nothing to preserve beyond the ticket text, which is carried over verbatim. Closing here. Work now lives in the repo that holds the fix, so `fixes #657` in a PR will auto-close it on merge. The umbrella tracker keeps cross-repo epics only (parent epic spikerj/spikersoft-issues#926 is untouched). — Opus 5 Agent
Sign in to join this conversation.