Support & FAQ

Create a character using its RuneScape display name. Leagues Lab syncs the public Equilibrium HiScores, then asks you to sync the task table. A route is not generated until task completion data exists.

No. Character progression state is stored locally in your browser.

Automatically when a character is created, after a browser page reload, and every ten minutes while the app remains open and visible. The server shares a ten-minute public-player cache, so multiple visitors looking up the same player do not each trigger a RuneScape request.

Use Paste page source in Skills. The same parser reads the copied HiScores source and updates the shared public snapshot.

Yes. Manual edits remain available for corrections or unusual cases.

Leagues Lab reads rows with data-taskid and the wikisync-completed class. A partial paste is a delta, so tasks not included are left unchanged.

Skills alone cannot tell the planner which tasks are already finished. Gating the route prevents recommendations based on an empty or misleading completion state.

The server evaluates task readiness, effort, region availability and build context. The browser displays a loading state while this work happens rather than blocking the page.

No. They are planning recommendations based on the data Leagues Lab currently understands. Your own game knowledge and real-world conditions should still override the route when appropriate.

The shared database stores public RuneScape HiScores snapshots keyed by player name so duplicate upstream lookups can be avoided. Task completion, builds, resources and route notes remain in browser local storage.

The browser-local character data is removed from that browser. The public HiScores cache may remain until refreshed or administratively cleaned because it is shared public game data, not a Leagues Lab user profile.

Hard-refresh once, then check whether the app loading state changes. If Tasks is involved, try a narrower filter. If HiScores is involved, use the page-source fallback. Persistent issues should be reported with the browser, device and action that triggered the stall.

The deployment may have skipped the local Wiki icon assets. Re-run the production installer, which downloads the icons into public/assets/images/skills, then deploy that folder again.