Every item, station and recipe in RuneScape: Dragonwilds, woven into one navigable map. Click a node to open its codex — recipes, facilities, skills and everything it unlocks.
First it answers “what do I need to craft this from what I have now?” — then it is a place to browse every crafting, item and skill tree.
RuneScape: Dragonwilds has a complex system of skills, recipes and items, and while this atlas tries to make it easy to navigate that system, it is necessarily complicated itself. Nothing here is hidden, it is only unsorted until you read it once: the columns below cover planning, the map, the graph and the keys, and the guided tours at the bottom walk each one through a real errand — your view is restored afterwards.
“From nothing” — every item panel opens with the plan: Gather (raw materials, total quantities), Build (stations), Train (skills + levels), and the Critical chain — the longest prerequisite run that gates your progress. Click any chip to jump.
Path to… — pick a starting item, press the button, then tap a target on the map or pick one from the gold-pulsing search box. The shortest material route lights up with numbered steps.
Waypoint checklist — cycle the plan button to plan: waypoint: the remaining work becomes an ordered, checkable list (Gather → Build → Craft) from your ledger to the item. Check a step off as you craft it and the plan re-runs; the header tracks X of N done · re-plans per item, with a reset.
☆ / ★ beside an item's name marks it owned (★ when you have it). Flip the Possessions chip to show only what you can reach from what you own. Counts persist in your browser. The ✎ next to it opens the item's edit form — correct its fields and add its links there (⚙ → Your data edits).
Shift+Click isolates a crafting tree — by default everything the item requires at any depth plus one level of what it enables (that is "how do I make this, and what is it for"). The direction select switches to outputs only (what it enables — the full both-way walk can swallow most of the map for hub items), inputs only or up + down; those three honour the Depth box (blank = all). Requires ⤵ highlights every ingredient behind an item. The legend (top left) is the single control surface for what the map shows: every item kind, all link kinds, Dead ends (items nothing crafts) and Possessions (with your owned-item count) toggle there — Show everything and ↺ All — reset view sit at the bottom of the VIEW section. Found in rows in a panel jump to green region hubs (map aids from the wiki's location prose — their links start hidden; enable Region links in the legend). The wiki's quests are nodes too: region → quest → reward in gold, each quest leading with its Where to start line and listing its rewards and the mounts it unlocks — that layer is on by default (LINKS → Quest links), and quests, mounts and regions never affect recipes, plans or paths.
⚉ Character (header) keeps a level per skill plus a separate memory of your layout, settings and owned items — two characters on one browser no longer overwrite each other. The number beside a name is its total level (the sum of all skills); set each skill from the grid in the panel, or from a skill hub's own Your level row. The atlas asks for a character once and remembers your answer — add, rename, switch or delete them any time.
All of the graph controls live in the ⚙ graph settings dropdown in the header: the algorithm select (24 algorithms, grouped force / trees / simple — similar ones ship on purpose; the same graph renders differently under each, and subtrees can prefer different algorithms than the whole), force-directed (off = spread presets), animate (off jumps straight to the result), saved positions (applies the bundled snapshot instantly, marked · saved), the density slider (tunes elk layer spacing live, 50–200%; 💾 saves the arrangement as a custom snapshot that boots instantly, marked · custom; ✕ clears it; ⤓ downloads it to share — merged ones ship with the atlas for every visitor, marked · curated), worker layout (computes heavy layouts in a background thread so the page keeps responding; if a worker can't run a layout it falls back to the main thread automatically) and re-layout on graph change (on: any change to what's shown re-runs the layout so nothing clumps; off: nodes appear where they fit without moving the rest). Toggles that re-arrange the map toast an Undo link for a few seconds. The gold Arranging pill spins and shows a live progress bar until the layout settles; algorithms that can't run here (rooted-tree ones on the full map) tell you so instead of failing silently.
/ search · ? help · F fit · Esc cancel path → clear isolation → close panel.
Wheel = zoom, drag = pan. The breadcrumb shows lineage; the minimap (bottom right) shows where you are — click it to jump.
A wrong name, a missing link, a find spot nobody wrote down — you can fix it here and send it in. Your fixes stay in this browser until a maintainer merges the file you send, so nothing you do changes the atlas for anyone else.
1 · Fix it — the ✎ beside an item's name opens its edit form: its fields, and its Links (makes · gives · found-in). ⚙ → Your data edits → ＋ Add item adds one that is missing; Hide item removes one that should not be here.
2 · Check the diff — ⚙ → Your data edits lists every change as bundled → yours, so you can see exactly what you are about to send. revert drops a row you did not mean.
3 · Export it — ⤓ Export edits saves dragonwilds-edits.json: the file you send.
4 · Send it in — drag that file into the pre-filled form and submit. That is the whole job; a maintainer merges it and it lands on the live atlas.
The address bar always mirrors your view — copy it to send someone exactly what you are looking at.
#/iron_sword opens that item. #/iron_ore/iron_sword opens the path between two items, gold trail and all. Graph options ride along as query params — ?layout=grid, ?cats=food, ?links=0, ?iso=iron_sword&isodir=up&isodepth=2 — covering everything in ⚙ graph settings and the legend. A link's options apply to that visit only: they are never saved over your own settings. Anything unusable is reported with a toast instead of failing silently.
Short scripted walkthroughs — each answers one real question. Your view is restored afterwards.
Your layout, settings and owned items are saved per character, and each character tracks a level per skill — the number beside the name is their total. Name one to keep it all together; you can add more later from the header.
What this browser has changed, next to the atlas as it ships. Nothing here touches the shipped files — your corrections stay yours until you export them and send them in. When the atlas catches up with one of your edits it moves to in dataset, and can be cleared.
Done editing? ⤓ Export edits hands you dragonwilds-edits.json — the one file to send in. Nothing reaches the shipped atlas until a maintainer merges it.
Found something wrong — a name, a missing link, a place nobody wrote down? Fix it right here, save it as a small file, and hand the file over. Nothing to download or install, and nothing you do changes the atlas for anyone else.
Your fixes live in this browser until a maintainer merges the file you send, so you can experiment freely: the shipped atlas is never rewritten from here, and Clear all my edits puts everything back the way you found it.
A wrong name, kind or item type; a missing or wrong wiki link; a description line or a stat; a relationship the atlas is missing (makes · gives · found-in); an item that is missing altogether. Recipes, drops and locations come from the wiki, so stick to what you can check in game or on the wiki — an honest gap beats a plausible guess.
Search the item (/ jumps to the search box), press Enter to open it, then press the ✎ beside its name. The panel becomes a form: the item's fields on top, its Links below. Missing item? ⚙ → Your data edits → ＋ Add item. An item that should not be here at all? Hide item in its form.
⚙ → Your data edits lists every difference from the bundled atlas as bundled → yours, so you can see exactly what you are about to send. revert drops a row you did not mean; nothing is sent until you send it.
Still in ⚙ → Your data edits, press ⤓ Export edits. That downloads dragonwilds-edits.json — a few kilobytes holding only your changes, which is the fix. (⤓ Export full data is the whole dataset; only wanted for a big overhaul.)
Open the data-fix form, drag dragonwilds-edits.json into the file box, say in one line what you fixed and how you checked it, and submit. That is the whole job — the merge, the commit and the deploy are someone else's problem, and you can watch the fix appear on the live atlas.
Your file is merged into the dataset and the atlas picks the fix up on your next visit. Then it notices your browser is still holding the same values, marks them in dataset and asks once whether to drop the local copies — say yes and you are back to a clean slate, with your fix in the atlas for everyone.
With the repo cloned, node scripts/open-edits-pr.mjs dragonwilds-edits.json merges your export, commits it on a branch and opens the pull request for you — the same run also prints the plan it is about to apply. The full technical guide — the dataset's shape, the scraper pipeline, the audit scripts and what a data PR has to show — is CONTRIBUTOR-DATA.md.