Anexim/Mana-Loop
1
1
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

BUG: Spire tab shows inconsistent state — Max Floor 1 but Floors Cleared 0 #238

New Issue
Closed
opened 2026-06-01 09:22:36 +02:00 by Anexim · 1 comment
Anexim commented 2026-06-01 09:22:36 +02:00
Owner
Copy Link
Copy Source

Bug Description

After the ErrorBoundary recovers from a crash, the Spire tab shows "Max Floor Reached: 1" but "Floors Cleared: 0" simultaneously. These values should be consistent — if max floor is 1, at least 1 floor should be cleared or the max should be 0.

Steps to Reproduce

  1. Trigger a crash (e.g., click "Climb the Spire")
  2. Click "Reset & Recover"
  3. Navigate to the Spire tab
  4. Observe: "Max Floor Reached: 1" and "Floors Cleared: 0"

Additional Finding

  • Floor 10 guardian shows "Armor: 10%" followed by stray "000" text — a number formatting bug displaying extra zeros after the armor percentage.
## Bug Description After the ErrorBoundary recovers from a crash, the Spire tab shows "Max Floor Reached: 1" but "Floors Cleared: 0" simultaneously. These values should be consistent — if max floor is 1, at least 1 floor should be cleared or the max should be 0. ## Steps to Reproduce 1. Trigger a crash (e.g., click "Climb the Spire") 2. Click "Reset & Recover" 3. Navigate to the Spire tab 4. Observe: "Max Floor Reached: 1" and "Floors Cleared: 0" ## Additional Finding - Floor 10 guardian shows `"Armor: 10%"` followed by stray `"000"` text — a number formatting bug displaying extra zeros after the armor percentage.
Anexim added the ai:todo label 2026-06-01 09:22:36 +02:00
n8n-gitea was assigned by Anexim 2026-06-01 09:22:36 +02:00
Anexim added this to the (deleted) project 2026-06-01 11:45:48 +02:00
Anexim commented 2026-06-01 13:56:09 +02:00
Author
Owner
Copy Link
Copy Source

✅ Fixed spire tab inconsistent state (Max Floor 1 but Floors Cleared 0):

  • enterSpireMode no longer sets maxFloorReached to Math.max(s.maxFloorReached, s.currentFloor) which was inflating it to 1 when no floors were cleared
  • exitSpireMode now preserves maxFloorReached instead of resetting to 0
✅ Fixed spire tab inconsistent state (Max Floor 1 but Floors Cleared 0): - enterSpireMode no longer sets maxFloorReached to Math.max(s.maxFloorReached, s.currentFloor) which was inflating it to 1 when no floors were cleared - exitSpireMode now preserves maxFloorReached instead of resetting to 0
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai:blocked
ai:done
ai:in-progress
ai:priority:high
priority
 ai:review
ai:todo
No Label ai:todo
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
n8n-gitea zhipu Anexim
No Assignees n8n-gitea
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Anexim/Mana-Loop#238
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?