Use this as a working reference
Open this HTML in a browser. No server, account or install is needed for local search and calculations. The bundled catalog, coordinates and routes work offline. Collision relief is embedded and works offline. Original map artwork can be downloaded separately and reused from browser storage after a successful save. Only external source pages and optional original artwork need an internet connection.
The downloadable package also includes ASSISTANT_LOOKUP.md, REFERENCE_CATALOG.md, JSON, CSV, an indexed SQLite database, a character-profile template and a Python command-line tool. The HTML itself embeds the cache and remains useful on its own.
For a future conversation
Attach ASSISTANT_LOOKUP.md and the latest data/resolved_records.json, or attach the whole package when supported. Include your updated character profile for personalized answers. A new conversation is not guaranteed access to these files without you supplying them.
What is actually cached?
All 35,944 corrected Classic source entities are embedded, with every available English name and source field. This includes 109,560 valid source spawn points, linked acquisitions, quest starts, objectives, turn-ins and prerequisite links. Named-place supplements are retained from the earlier reference. The catalog retains its stated branch scope. Navigation now includes the supplied Forever 1.8.2 collision data and source transit timings; these are not a live game survey.
Update deliberately
python tools/rebuild.py rebuilds from the bundled corrected source JSONL. It does not fetch new game data. When a beta patch changes something, check the source, keep its build and date, and add a separate build-specific observation instead of overwriting the uploaded baseline.
Nothing here connects to your game, reads your account or monitors patches automatically.
Evidence rules
| Label | Meaning |
|---|
| user_measured | User-entered observation tied to a build and UI map; not independently verified. |
| official_announced | Blizzard’s stated design or schedule; not proof of every live implementation detail. |
| client_extraction | A third-party extraction of a specified beta build. |
| client_index | Metadata or a place/map index from the beta atlas; not a validated route. |
| published_listing | A current Forever-labeled database page; inherited fields may still need confirmation. |
| classic_reference | Classic data or positions; not verified for Forever. |
| user_entered / imported_unverified | Manual or imported information, not independently verified. |
| legacy_comment | Historical hint; never silently promote to current fact. |
| provisional_baseline | A starting assumption awaiting character measurement. |
| source_directory | Navigation to broader data, not a local mirror. |
| reference_only / unconfirmed_report | Incomplete linked record or unverified report. |
When sources disagree
Match the question to the correct game branch and exact build. Prefer a relevant reproducible current-character observation for that character’s speed or position, official statements for announced design, and current component data for entity values. Record conflicts rather than averaging them.
Unknown is a useful value
A null field is unknown, not zero, unavailable or unnecessary. Do not infer your level, equipment, talents, completed quests, flight nodes or hearth location from “Orc Rogue.”