docs(website): record the spawn atlas pipeline and what real data changed #67
Reference in New Issue
Block a user
No description provided.
Delete Branch "docs/spawn-atlas"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Protocol 3.0 order 3 (Part C), docs half of website #112. Part C is website-only
— no plugin, no sidecar, no new kinds, no wire change.
New: website/SPAWN_ATLAS.md
The operator-facing reference: the build/import split and why it exists (build
needs a ServUO tree, import does not, and the container has the artifact but not
the tree), the re-run story, the artifact format, the placement transform, and
the three quirks in the source data that are silent when unhandled.
Also documents the artwork policy explicitly: the project ships no creature
art and no extraction tooling. Sprites live in the operator's own client
.mul/.uop files and are theirs, not ours to redistribute.
artis nullable andNULL on every fresh import; an operator who wants art extracts it themselves into
the gitignored uploads/atlas/ and maps slugs in a gitignored art map. Text-only
is the normal, supported state — not a degraded one.
New: v3.md §6.1 — what the build against real data changed
Six corrections, kept as a diff rather than edited into §6 in place, because
each is a trap the next person would otherwise re-enter:
TerMur/Trammel points; the facet comes from each record's
<Map>.fast-xml-parser vs a tokenizer open.
Ter Mur,<Map>says
TerMur. Unreconciled the landmark fallback never fires there and everyunregioned Ter Mur/Tokuno spawn silently reads "Wilderness".
Fairy,{RND,4,8},alchemist/z/-50). Taken literally they invent creatures that do not existand split real ones in two. 71 of 845 affected; 800 remain after stripping.
three encodings. Getting under 1 MB would mean dropping the spawner name.
which would defeat the all-or-nothing reload the design asked for.
§6 also now records that Part C ships as two website PRs: the parsing half is
where the correctness risk lives and should not be reviewed inside a 10k-line
diff alongside routes and React.
BACKEND_DESIGN.md
The seven atlas tables, the import-owned contract, the four column choices that
are traps (
spawn_range/grpreserved words, DELETE vs TRUNCATE, explicit pointids, plain INDEX not FULLTEXT), and the distinction between the configured
champion roster and the live champ.update feed.
PROJECT_TREE.md is left alone — it is auto-generated by the sync-project-tree
workflow.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01U7CBg11prhLimL9iHSX1bP