📋 Bug Fix Prioritization — Ordered Task List #127

New Issue

2026-05-22T13:28:57+02:00

Anexim commented

2026-05-22 13:28:57 +02:00

Bug Fix Prioritization

This issue provides a recommended order for tackling the current bug backlog. Issues are grouped by priority tier.

🔴 HIGHEST PRIORITY — Game-Breaking Bugs

These bugs make core features completely unusable or crash the game. Fix first.

1. Issue #125 — Entering the spire crashes the game irreversibly

Why first: This is a hard crash with no recovery — the player gets stuck in a corrupted state that persists across refreshes. It completely blocks access to the spire feature and can soft-lock the entire game. The fix (resetting spire state on entry) is also a prerequisite for properly testing any other spire-related work.

2. Issue #118 — Stats tab does not load

Why second: A core UI tab that is completely broken. Players cannot view their stats, which is fundamental to understanding game progress. Likely a type mismatch / prop passing issue that should be straightforward to fix.

3. Issue #123 — Equipping/unequipping gear in EquipmentTab doesn't work

Why third: Core equipment management is non-functional. Players cannot equip gear they craft or find, which blocks progression. The root cause appears to be that equipItem/unequipItem actions from equipment-actions.ts are never wired into the crafting store.

🟠 HIGH PRIORITY — Core Mechanics Broken

These bugs break important gameplay systems but don't crash the game.

4. Issue #119 — Disciplines don't accumulate XP or drain mana when active

Why fourth: The discipline system is a core progression mechanic. If it doesn't work at all, players can't progress through disciplines. This likely involves the activate() guard preventing re-activation of auto-paused disciplines, and possibly tick pipeline issues.

5. Issue #120 — Discipline pause button doesn't revert to "Activate" after pausing

Why fifth: Closely related to #119 — the deactivate() action doesn't set paused: true on the discipline state. This is a small, isolated fix that should be done alongside #119 since they touch the same file (discipline-slice.ts).

6. Issue #124 — Guardian pacts tab locked to old 100-floor system; needs dynamic procedural guardians

Why sixth: The Pacts tab only shows guardians from the static GUARDIANS constant (floors 10–100) but the extended guardian system in guardian-encounters.ts (compound, exotic, combo guardians up to floor 150+) is never used. This is a significant refactor that touches multiple files. Should be done after the crash fix (#125) since it involves the same spire/guardian systems.

🟡 MEDIUM PRIORITY — UX Improvements & Cleanup

These are important but don't break core functionality.

7. Issue #122 — Remove memory slot system and Memories section from PrestigeTab

Why seventh: The memory slot system is fully wired but has no gameplay mechanic — no code calls addMemory() outside of tests. It's dead code that adds complexity. Removing it simplifies the Prestige tab and eliminates orphaned state. Should be done before adding new discipline-based unlock systems (#126) to reduce the surface area of things to maintain.

8. Issue #126 — Add enchanter disciplines to unlock enchantment effects

Why eighth: This is a new feature request, not a bug fix. It depends on the discipline system working correctly (#119, #120) and benefits from the memory system cleanup (#127) being done first. The EFFECT_RESEARCH_MAPPING already provides the effect groupings needed — the work is primarily in wiring discipline perks to effect unlocks.

🟢 LOW PRIORITY — Cosmetic / Text Changes

9. Issue #121 — Rename discipline buttons from "Activate/Pause" to "Start Practicing/Stop Practicing"

Why last: Purely a text/UI flavor change. One line in DisciplinesTab.tsx. Should be done after the discipline bugs (#119, #120) are fixed since those touch the same component.

Suggested Execution Order

#125 (Spire crash)  →  #118 (Stats tab)  →  #123 (Equipment)
    →  #119 + #120 (Discipline bugs, same file)  →  #124 (Guardian refactor)
    →  #122 (Memory cleanup)  →  #126 (Enchanter disciplines)  →  #121 (Button text)

Key dependencies:

#119 and #120 should be done together (same file: discipline-slice.ts)
#124 should wait for #125 (both touch spire/guardian systems)
#126 should wait for #119/#120 (disciplines must work first) and benefits from #122 (less dead code)
#121 is independent but naturally fits at the end

# Bug Fix Prioritization This issue provides a recommended order for tackling the current bug backlog. Issues are grouped by priority tier. --- ## 🔴 HIGHEST PRIORITY — Game-Breaking Bugs These bugs make core features completely unusable or crash the game. Fix first. ### 1. Issue #125 — Entering the spire crashes the game irreversibly **Why first:** This is a hard crash with no recovery — the player gets stuck in a corrupted state that persists across refreshes. It completely blocks access to the spire feature and can soft-lock the entire game. The fix (resetting spire state on entry) is also a prerequisite for properly testing any other spire-related work. ### 2. Issue #118 — Stats tab does not load **Why second:** A core UI tab that is completely broken. Players cannot view their stats, which is fundamental to understanding game progress. Likely a type mismatch / prop passing issue that should be straightforward to fix. ### 3. Issue #123 — Equipping/unequipping gear in EquipmentTab doesn't work **Why third:** Core equipment management is non-functional. Players cannot equip gear they craft or find, which blocks progression. The root cause appears to be that `equipItem`/`unequipItem` actions from `equipment-actions.ts` are never wired into the crafting store. --- ## 🟠 HIGH PRIORITY — Core Mechanics Broken These bugs break important gameplay systems but don't crash the game. ### 4. Issue #119 — Disciplines don't accumulate XP or drain mana when active **Why fourth:** The discipline system is a core progression mechanic. If it doesn't work at all, players can't progress through disciplines. This likely involves the `activate()` guard preventing re-activation of auto-paused disciplines, and possibly tick pipeline issues. ### 5. Issue #120 — Discipline pause button doesn't revert to "Activate" after pausing **Why fifth:** Closely related to #119 — the `deactivate()` action doesn't set `paused: true` on the discipline state. This is a small, isolated fix that should be done alongside #119 since they touch the same file (`discipline-slice.ts`). ### 6. Issue #124 — Guardian pacts tab locked to old 100-floor system; needs dynamic procedural guardians **Why sixth:** The Pacts tab only shows guardians from the static `GUARDIANS` constant (floors 10–100) but the extended guardian system in `guardian-encounters.ts` (compound, exotic, combo guardians up to floor 150+) is never used. This is a significant refactor that touches multiple files. Should be done after the crash fix (#125) since it involves the same spire/guardian systems. --- ## 🟡 MEDIUM PRIORITY — UX Improvements & Cleanup These are important but don't break core functionality. ### 7. Issue #122 — Remove memory slot system and Memories section from PrestigeTab **Why seventh:** The memory slot system is fully wired but has no gameplay mechanic — no code calls `addMemory()` outside of tests. It's dead code that adds complexity. Removing it simplifies the Prestige tab and eliminates orphaned state. Should be done before adding new discipline-based unlock systems (#126) to reduce the surface area of things to maintain. ### 8. Issue #126 — Add enchanter disciplines to unlock enchantment effects **Why eighth:** This is a new feature request, not a bug fix. It depends on the discipline system working correctly (#119, #120) and benefits from the memory system cleanup (#127) being done first. The `EFFECT_RESEARCH_MAPPING` already provides the effect groupings needed — the work is primarily in wiring discipline perks to effect unlocks. --- ## 🟢 LOW PRIORITY — Cosmetic / Text Changes ### 9. Issue #121 — Rename discipline buttons from "Activate/Pause" to "Start Practicing/Stop Practicing" **Why last:** Purely a text/UI flavor change. One line in `DisciplinesTab.tsx`. Should be done after the discipline bugs (#119, #120) are fixed since those touch the same component. --- ## Suggested Execution Order ``` #125 (Spire crash) → #118 (Stats tab) → #123 (Equipment) → #119 + #120 (Discipline bugs, same file) → #124 (Guardian refactor) → #122 (Memory cleanup) → #126 (Enchanter disciplines) → #121 (Button text) ``` **Key dependencies:** - #119 and #120 should be done together (same file: `discipline-slice.ts`) - #124 should wait for #125 (both touch spire/guardian systems) - #126 should wait for #119/#120 (disciplines must work first) and benefits from #122 (less dead code) - #121 is independent but naturally fits at the end

Anexim added the ai:todo label 2026-05-22 13:28:57 +02:00

n8n-gitea was assigned by Anexim

2026-05-22 13:28:57 +02:00

Anexim commented

2026-05-22 13:39:39 +02:00

Starting work on bug fix prioritization. Will tackle issues in the recommended order: #125 → #118 → #123 → #119+#120 → #124 → #122 → #126 → #121

Anexim closed this issue

2026-05-22 18:22:07 +02:00

Anexim commented

2026-05-22 18:22:07 +02:00

✅ Completed all 5 prioritized bug fixes from the prioritization ticket:

#125: Spire crash (done in previous commit)
#118: Stats tab (done)
#123: Equipment equip/unequip (done)
#119: Discipline XP (done)
#120: Discipline pause button (done)

All changes pushed to master.

✅ Completed all 5 prioritized bug fixes from the prioritization ticket: - #125: Spire crash (done in previous commit) - #118: Stats tab (done) - #123: Equipment equip/unequip (done) - #119: Discipline XP (done) - #120: Discipline pause button (done) All changes pushed to master.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Anexim/Mana-Loop#127