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

[Medium] [Bug] Earth element desync between localStorage and UI after Unlock All #338

New Issue
Open
opened 2026-06-09 12:51:55 +02:00 by Anexim · 1 comment
Anexim commented 2026-06-09 12:51:55 +02:00
Owner
Copy Link
Copy Source

Bug: Earth element desync between localStorage and UI

Steps to reproduce

  1. Open the game
  2. Go to Debug → Elements
  3. Click "Unlock All Elements"
  4. Check localStorage → mana-loop-mana → elements.earth

Expected

All elements including earth show unlocked: true in localStorage, matching the UI.

Actual

The UI shows earth as unlocked (with 0/10 and a +10 button), but localStorage shows earth: { unlocked: false, ... }. This is a desync between the persisted state and the in-memory state.

Root cause

The handleUnlockAll function in ElementDebugSection.tsx calls handleUnlockElement(id) which calls useManaStore.getState().unlockElement(element, 0). The unlockElement function updates the in-memory state but the persist middleware may not be writing it correctly for all elements, or there's a race condition where the earth element's unlocked state is not being persisted.

Store

useManaStore → manaStore.ts → unlockElement action

## Bug: Earth element desync between localStorage and UI ### Steps to reproduce 1. Open the game 2. Go to Debug → Elements 3. Click "Unlock All Elements" 4. Check localStorage → `mana-loop-mana` → `elements.earth` ### Expected All elements including `earth` show `unlocked: true` in localStorage, matching the UI. ### Actual The UI shows earth as unlocked (with 0/10 and a +10 button), but localStorage shows `earth: { unlocked: false, ... }`. This is a desync between the persisted state and the in-memory state. ### Root cause The `handleUnlockAll` function in `ElementDebugSection.tsx` calls `handleUnlockElement(id)` which calls `useManaStore.getState().unlockElement(element, 0)`. The `unlockElement` function updates the in-memory state but the persist middleware may not be writing it correctly for all elements, or there's a race condition where the earth element's unlocked state is not being persisted. ### Store `useManaStore` → `manaStore.ts` → `unlockElement` action
Anexim added the ai:todo label 2026-06-09 12:51:55 +02:00
n8n-gitea was assigned by Anexim 2026-06-09 12:51:55 +02:00
Anexim added ai:in-progress and removed ai:todo labels 2026-06-09 19:10:00 +02:00
Anexim commented 2026-06-09 19:10:00 +02:00
Author
Owner
Copy Link
Copy Source

Starting work. Investigating Earth element desync between localStorage and UI after Unlock All.

Starting work. Investigating Earth element desync between localStorage and UI after Unlock All.
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:in-progress
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#338
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?