Dungeon crawler: exit-portal prompt uses a hardcoded 3-key gate instead of requiredKeys #1039

Closed
opened 2026-08-13 05:06:39 +00:00 by spikerj · 1 comment
Owner

updateExitPortalPrompt shows the finish prompt when the player is near the portal and keysCollected() >= 3 (hardcoded). tryEnterExitPortal / checkExitCollision correctly gate on this.requiredKeys.

If requiredKeys is not 3, the HUD can claim the portal is ready while E does nothing (or hide the prompt when extra keys are required). Characterized in dungeon-crawler.quest-skill.spec.ts (wave 7 a1 tick 2).

const shouldShow = distSq < interactionDistSq && this.keysCollected() >= 3;

Expected: compare against this.requiredKeys (same contract as enter/collision).

`updateExitPortalPrompt` shows the finish prompt when the player is near the portal **and** `keysCollected() >= 3` (hardcoded). `tryEnterExitPortal` / `checkExitCollision` correctly gate on `this.requiredKeys`. If `requiredKeys` is not 3, the HUD can claim the portal is ready while E does nothing (or hide the prompt when extra keys are required). Characterized in `dungeon-crawler.quest-skill.spec.ts` (wave 7 a1 tick 2). ```ts const shouldShow = distSq < interactionDistSq && this.keysCollected() >= 3; ``` Expected: compare against `this.requiredKeys` (same contract as enter/collision).
Author
Owner

Already present on spikersoft-angular master (48e93a23e). updateExitPortalPrompt gates on this.keysCollected() >= this.requiredKeys. Closing.

Already present on `spikersoft-angular` `master` (`48e93a23e`). `updateExitPortalPrompt` gates on `this.keysCollected() >= this.requiredKeys`. Closing.
Sign in to join this conversation.