No description
  • Python 52.2%
  • JavaScript 25.8%
  • CSS 11.8%
  • HTML 10.2%
Find a file
ryan.mcgee 2f819348b8
All checks were successful
deploy / build (push) Successful in 58s
feat: fix game-name matching and add a game vs wiki cross-check (#9)
2026-11-19 04:09:44 +00:00
.gitea/workflows feat: guided game-save import with help dialog (#6) 2026-11-19 03:42:28 +00:00
content feat: dragonwilds item tracker on zola and cloudflare (#1) 2026-11-14 17:07:27 +00:00
data/wiki feat: filter items by completed quests (#2) 2026-11-14 19:55:31 +00:00
scripts feat: fix game-name matching and add a game vs wiki cross-check (#9) 2026-11-19 04:09:44 +00:00
static feat: fix game-name matching and add a game vs wiki cross-check (#9) 2026-11-19 04:09:44 +00:00
templates refactor: single import button and a dialog that reuses the mapping (#8) 2026-11-19 03:52:30 +00:00
.gitignore feat: fix game-name matching and add a game vs wiki cross-check (#9) 2026-11-19 04:09:44 +00:00
README.md feat: fix game-name matching and add a game vs wiki cross-check (#9) 2026-11-19 04:09:44 +00:00
wrangler.jsonc feat: dragonwilds item tracker on zola and cloudflare (#1) 2026-11-14 17:07:27 +00:00
zola.toml feat: collection log with optional quest logic mode (#3) 2026-11-19 01:46:17 +00:00

rsdclog

Collection log for RuneScape: Dragonwilds, live at https://rsdclog.ultravustudios.com. One page listing every item, crafted piece and build from the Dragonwilds Wiki, with crafting recipes, drop sources and the region each item is first found in. You tick the items you've collected and the quests you've completed; ticks are saved in the browser's localStorage.

It is a Zola site served as static assets by a Cloudflare Worker.

Layout

Path Purpose
scripts/fetch.py Downloads the wiki's infobox_item, recipe and dropsline buckets via the API
scripts/cats.py Downloads page categories (used to drop discontinued content)
scripts/text.py Downloads page wikitext (used to find each page's region)
scripts/quests.py Downloads the quest list pages and the "Quests" page (quest order, regions and quest-only rewards)
scripts/build.py Turns the wiki snapshot into data/items.json (items with categories, regions and quest rewards, plus the quest list) and, optionally, static/items-index.json (ids and names only)
data/wiki/ Committed wiki snapshot, so builds are reproducible offline
data/items.json Built item list (ignored); inlined into the page by templates/index.html
static/items-index.json Small index of item ids and names (ignored, generated by build.py); served for gamemap.py to match game assets against
static/tools/gamemap.py Standalone tool players run to make gamemap.json for the "Import game save" button; served from the site
scripts/crosscheck.py Local-only report comparing the game's item and quest lists with the wiki-derived ones (reuses gamemap.py); output is gitignored
templates/index.html Page markup
static/tracker.css, static/tracker.js Page styles and behaviour
zola.toml Site config, including base_url
wrangler.jsonc Cloudflare Worker config: serves public/ on the custom domain
.gitea/workflows/deploy.yml CI: builds every PR, deploys on push to main

Build

build.py uses only the Python standard library. The item list must be built before Zola runs, since the template loads it.

podman run --rm --network=none --userns=keep-id -v "$PWD":/work -w /work \
  docker.io/library/python:3.13-slim python scripts/build.py data/wiki data/items.json static/items-index.json
podman run --rm --network=none --userns=keep-id -v "$PWD":/work -w /work \
  ghcr.io/getzola/zola:v0.23.6 build

Output goes to public/. For a live-reloading preview at http://127.0.0.1:1111:

podman run --rm --network=host --userns=keep-id -v "$PWD":/work -w /work \
  ghcr.io/getzola/zola:v0.23.6 serve --interface 127.0.0.1 --port 1111

Deploy

Pushes to main deploy through the Gitea Actions workflow, which needs two repository secrets:

  • CLOUDFLARE_API_TOKEN: an API token with the Edit Cloudflare Workers template permissions, scoped to the account and the ultravustudios.com zone.
  • CLOUDFLARE_ACCOUNT_ID: the Cloudflare account ID.

wrangler.jsonc attaches the Worker to rsdclog.ultravustudios.com as a custom domain; Cloudflare creates the DNS record and certificate on first deploy, which requires the ultravustudios.com zone to be on the same account.

To check the Wrangler config without deploying (after building public/):

podman run --rm --network=host --userns=keep-id -e HOME=/tmp -v "$PWD":/work -w /work \
  docker.io/library/node:22.21.1-alpine npx --yes wrangler@4.162.0 deploy --dry-run

Refresh the wiki snapshot

After a game patch, re-download the data (in this order: cats.py and text.py read the files fetch.py writes), then rebuild:

podman run --rm --network=host --userns=keep-id -v "$PWD":/work -w /work docker.io/library/python:3.13-slim sh -c '
  python scripts/fetch.py data/wiki &&
  python scripts/cats.py data/wiki &&
  python scripts/text.py data/wiki &&
  python scripts/quests.py data/wiki'

Update the "pulled" date in the footer of templates/index.html to match.

How regions and quest rewards are assigned

Regions are inferred, not listed by the wiki. build.py matches location names (the REG table) against each page's title, infobox location fields and intro text, then propagates: an item's region is the earliest of where it drops, or the latest region among its crafting station and ingredients. Items with no resolvable location show as "Region not listed". By default the region is informational (a chip and a filter); nothing is hidden by it.

Quests come from the wiki's primary and secondary quest lists. An item is marked as a reward of a quest (q) when the "List of unique quest rewards" table on the wiki's Quests page names it, or when it is that quest's "Reward Pack". Rewards the table lists as given "during" or on "partial completion" of a quest are attributed to that quest too.

Logic mode

The "Only what my quests unlock" toggle is off by default. When on, the list is limited to items you could have by now, from the quests you've ticked. Ticks stay independent: a ticked quest also counts the main quests before it and the one that opens its region, but nothing is ticked for you.

  • A main quest opens the region of the next main quest (u on the quest; Dragon Slayer opens Fellhollow, where Withering Heights is set). Regions no main quest is set in (Ghornfell) are open from the start.
  • An item's gate (k) is its direct quest rewards, except those given "during" or on "partial completion" of a quest, plus anything for which every way to get it needs a gated item: each drop source, each recipe (station and ingredients), and an infobox location. "Tome of the Dragon Slayer" is gated because it only comes from the Dragon Slayer reward pack.
  • Items with no resolvable region count as available.
  • Category and overall item counts cover only the items in scope while the mode is on.

Export and import

Progress lives in the browser's localStorage, so clearing site data or switching browser loses it. "Export" downloads dragonwilds-collection-log-YYYY-MM-DD.json; "Import" loads one back.

{ "format": "rsdclog-progress", "version": 1, "exported": "2026-11-19T01:47:53.165Z", "items": ["coarse-thread"], "quests": ["Dragon Slayer"] }
  • Items are the ids build.py generates (a slug of the wiki page name) and quests are wiki quest names. View settings (filters, logic mode) are not exported.
  • Import replaces the current progress, after a confirmation that shows both sets of counts. Entries this version of the page doesn't know about (for example items removed from the wiki since the export) are skipped and counted in the confirmation.
  • Files that aren't valid JSON, lack "format": "rsdclog-progress", or have a version other than 1 are rejected without changing anything. If the format ever changes, bump version and keep reading the old one.

Import from a game save

"Import game save" reads a RuneScape: Dragonwilds character save and ticks the items you've picked up (Progress.ItemsPickedUp) and the quests with QuestState 2 (completed). It only adds ticks; it never removes any, and nothing is uploaded: the file is read in your browser. The button opens a dialog that walks through the steps below.

The ids in a save are opaque, so the page needs a mapping file (gamemap.json) from ids to this site's items and quests. It is built from the game's own data, so it is not committed or hosted: each player makes theirs.

Making the mapping (once, and after game updates, because new items get new ids): run the standalone tool, which is served from the site at /tools/gamemap.py and lives in static/tools/gamemap.py. It needs only Python 3.8+ and the game files:

python gamemap.py "path/to/game" --save "My Character.json"   # --save is optional: reports how much of it is covered
  • Game files: the free dedicated server (Steam app 4019830) has the same item and quest data and is the tested source (steamcmd +force_install_dir server +login anonymous +app_update 4019830 validate +quit). The path can be the install folder or its RSDragonwilds/Content/Paks folder. A client install may work but is untested and may be encrypted.
  • The tool downloads retoc v0.1.5 (MIT) for your platform, verifies its pinned SHA-256, extracts only the ITEM_, DA_, Quest_ and string-table assets to a temporary folder, matches each asset's id and display name to the site's item index (/items-index.json, or --index FILE), writes gamemap.json and deletes the temporary folder. Windows, macOS and Linux builds are pinned; only Linux has been tested.
  • gamemap.json holds ids and names only, plus the game build and date it was made. It is gitignored in this repo.

Using it: click "Import game save" to open the dialog. The first time, follow the how-to, load gamemap.json, then choose your character save. The mapping is kept in that browser and reused: on later visits the how-to is collapsed, the loaded mapping is shown, and focus is on "Choose character save", so you only pick the save. After a game update, make a new mapping and use "Load a different mapping".

Saves are on your machine as JSON, for example %localappdata%\RSDragonwilds\Saved\SaveCharacters\ on Windows. Xbox Game Pass saves are stored differently and are not supported.

Known gaps: items the wiki data doesn't list (some seeds, farming tools, quest-only items) are skipped and counted in the status message, and a few quests (tutorial tasks, some Umbral Sands tasks) have no wiki equivalent. Treat QuestState 2 meaning "completed" as an inference from observed saves. Extracting game files may be restricted by the game's terms; check them yourself.

Cross-check against the game files

scripts/crosscheck.py compares what is in the game files with what the wiki data lists, using the same extraction and name matching as gamemap.py. It is for maintainers and writes a report that names game assets, so the default output (crosscheck-report.md) is gitignored: don't commit it.

python scripts/crosscheck.py "path/to/game" --index static/items-index.json

The report lists: game assets that match a site item; item-like game assets the wiki data lacks; assets under a folder the game itself calls Deleted; non-item data; site items with no game asset; suspected renames (a game name and a wiki name that differ by a character, which has found wiki typos); and quests on each side. Treat "game only" as a lead, not a to-do list: it includes test items, placeholders ([PH]), old versions (_OLD), colour variants and vendor purchase recipes that don't belong in a collection log.