feat: persist exploration zone selection in sessionStorage

Applies the same sticky-zone pattern as the boss and quest panels. The handleZoneSelect wrapper already existed — it just needed to write to sessionStorage alongside updating state, and the useState initialiser needed to read from sessionStorage on mount.
fix: use item name as key for equipped items list
2026-03-09 22:15:38 -07:00 · 2026-03-09 22:12:42 -07:00 · 2026-03-09 22:07:36 -07:00 · 2026-03-09 22:02:56 -07:00 · 2026-03-09 22:02:52 -07:00
1 changed files with 2 additions and 9 deletions
@@ -26,9 +26,7 @@ const bonusLabel: Record<string, string> = {
 */
 const CraftingPanel = (): JSX.Element => {
  const { state, craftRecipe, formatNumber } = useGame();
-  const [ activeZoneId, setActiveZoneId ] = useState(() => {
-    return sessionStorage.getItem("elysium_craft_zone") ?? "verdant_vale";
-  });
+  const [ activeZoneId, setActiveZoneId ] = useState("verdant_vale");
  const [ pendingRecipeId, setPendingRecipeId ] = useState<string | null>(null);

  if (state === null) {
@@ -70,11 +68,6 @@ const CraftingPanel = (): JSX.Element => {
    });
  }

-  function handleZoneSelect(zoneId: string): void {
-    setActiveZoneId(zoneId);
-    sessionStorage.setItem("elysium_craft_zone", zoneId);
-  }
-
  async function handleCraft(recipeId: string): Promise<void> {
    setPendingRecipeId(recipeId);
    try {
@@ -92,7 +85,7 @@ const CraftingPanel = (): JSX.Element => {

      <ZoneSelector
        activeZoneId={activeZoneId}
-        onSelectZone={handleZoneSelect}
+        onSelectZone={setActiveZoneId}
        zones={zones}
      />
Author	SHA1	Message	Date
hikari	c3e85c3768	feat: persist exploration zone selection in sessionStorage CI / Lint, Build & Test (pull_request) Successful in 1m16s Details Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m17s Details Applies the same sticky-zone pattern as the boss and quest panels. The handleZoneSelect wrapper already existed — it just needed to write to sessionStorage alongside updating state, and the useState initialiser needed to read from sessionStorage on mount.	2026-03-09 22:15:38 -07:00
hikari	2c16736bdf	fix: use item name as key for equipped items list Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m4s Details CI / Lint, Build & Test (pull_request) Successful in 1m8s Details item.type only has three possible values (weapon/armour/trinket). Using it as a React key is safe in practice because the equipment system enforces one item per slot, but item.name is a stable, semantically correct unique identifier that does not rely on that invariant.	2026-03-09 22:12:42 -07:00
hikari	0dc572c6fa	fix: use stable unique keys for quest reward list Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m3s Details CI / Lint, Build & Test (pull_request) Successful in 1m8s Details The previous key `${reward.type}-${amount ?? ""}` collapsed to "adventurer-" for every adventurer-unlock reward (which carries no amount), producing duplicate-key React warnings on every render tick. Because console.error is forwarded to the backend telemetry service, this caused continuous email alerts. The key now uses targetId (present on adventurer and upgrade rewards) first, falls back to amount (present on gold/essence/crystal rewards), and uses the map index only as a last resort.	2026-03-09 22:07:36 -07:00
hikari	9fcc5bb836	feat: persist zone selection across panel navigation in sessionStorage Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m2s Details CI / Lint, Build & Test (pull_request) Successful in 1m7s Details Both the boss panel and the quest panel now read their active zone from sessionStorage on mount and write back to it whenever the user selects a new zone. The stored selections are cleared automatically when the session ends, and fall back to verdant_vale when no stored value exists. Closes #36	2026-03-09 22:02:56 -07:00
hikari	fc93efd245	feat: persist adventure multiplier selection in localStorage Reads the saved batch-size preference on mount and writes it back to localStorage on every selection change, so the chosen multiplier survives page refreshes. Falls back to 1 when no stored value is found or the value is unrecognisable. Closes #35	2026-03-09 22:02:52 -07:00