Troubleshooting

1. Read the specific warning first — it names the missing fact: a stat, an item state, a price, or the active character. A blank power score shows its reason in place of the number (see When the score is paused), and recommendations keep working.
2. Check the active character's class, level, and stats on Gear, and the world type plus price settings in Settings; the tools read both.
3. Re-run after fixing; the missing number rejoins the ones that were there already.
4. When the fix does not land, report through Feedback with expected vs actual, the settings that reproduce it, and an optional screenshot — not credentials.

1. Power score differs from MapleScouter — compare inputs first: class, level, gear, and toggles, as set out in the scores guide. If matched inputs still disagree, file the case rather than bending either tool.
2. Crit looks defaulted or overcapped — an empty Crit Rate % means a default is in use; enter your real rate, and Over cap by % if you know it, as described in the character setup guide before re-reading a plan.
3. Continuous Ring or HEXA levels stale — the ring level is in the Oz Rings (Skill Rings) panel of a ring slot on Gear, and HEXA progress is on the HEXA pages; optimizer snapshots use them as they are.
4. A low hit figure feels harsh — in the Luck Analyzer, a small "Would have hit it by now" early in a chase is normal.

1. The top bar on every page holds Save and the character menu with Restore from cloud. Auto-save writes your build to cloud about a minute after edits; with it off, saving is manual.
2. A build marked Not synced exists only in this browser until it saves.
3. Moving devices: restore the newer cloud copy before editing on the second device.
4. Back up with Export All and Import on the Characters page; the full steps live in the recovery section — work these before anything destructive.

The bot reads the cloud copy of a build. A share link represents the snapshot that was shared, so create a new share when you want to send an updated build. Local edits and a successful cloud save are different states; check the sync status.

1. Do not clear browser data to "rebuild" a problem — export first if clearing is ever required, and work the warning's named fact instead.
2. Do not re-type stats until two scores match; enter the facts once, and report the case if matched inputs still disagree.
3. Do not treat n/a or a withheld number as a free result — it usually marks state you can enter or fix, then re-run.
4. Do not chase a friend's optimizer plan with different inputs; plans only match under the same level, class, stats, and budget.