wtclaude
a194ec68e0
Until now the only way a creature got a picture on this site was for an
operator to open UOFiddler on a desktop, export sprites by hand, copy them to
the web host and write a spawnAtlas.art.json naming each one. Almost nobody
did, so shard_spawn_creatures.art was NULL on every install.
The shard has had those files the whole time. Admin -> Shard -> Import now
walks its asset manifest, fetches only the sprites whose hash changed, writes
them under uploads/atlas/, asks the shard for a body id per atlas creature
(§8: it CONSTRUCTS the creature and reads Body.BodyID, which is the only thing
that is right for a shard's own custom creatures) and points each creature at
its picture. On a stock client that is 787 portraits, about a megabyte.
**The one thing v8.md §12 got wrong, and it is not cosmetic.** It says
`shard_spawn_creatures.art` "starts being filled by the import". That table is
emptied and refilled by replaceAtlas on EVERY atlas refresh, and a refresh runs
on every boot -- so a filename stored there would be destroyed by an ordinary
re-parse of the ServUO tree, with the next Update finding the client files
unchanged, reporting "nothing to do", and never restoring it. Nothing would
report a fault; the pictures would just be gone.
So the assets and the body map live in their own tables outside that blast
radius, and applyAtlas re-derives `art` on the way past as
`{ ...derived, ...operatorMap }` -- which is also the one place "the operator's
own artwork wins" is enforced, on every rebuild rather than only at import.
Smaller decisions worth not rediscovering:
- The derivation joins on the catalogue KEY, not on the body id. The simpler
join is correct today and stops being correct the moment phase 6 adds
body/400/a2/f0, at which point one slug matches dozens of rows.
- Filenames are content-addressed. A stable name overwritten in place leaves
every browser and CDN serving the previous client's sprite, with the database
row perfectly correct.
- An unchanged key whose FILE is missing is fetched again. The row and the disk
can disagree (a wiped uploads volume, a restore from a dump), and a broken
image on a creature page is worse than one re-fetched sprite.
- A key the shard cannot render is not a failure. Two thirds of the playable
ghost and gargoyle bodies have no art on a stock client, and an import that
reported eight failures every time would teach an operator to ignore the panel.
- A key that VANISHED from the manifest needs review before anything changes:
an unmounted client volume and a deliberate downgrade look identical here.
23 new tests; 674 server and 42 client tests pass. The SQL was also run against
a real MariaDB, which is what proved the CONCAT join and the singleton CHECK.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016wDDVXWMDz82WqE1i969r4
71 lines
3.7 KiB
SQL
71 lines
3.7 KiB
SQL
-- ── module-uo's teardown ──────────────────────────────────────────────────
|
|
--
|
|
-- Destructive, and run ONLY by an explicit admin purge (MODULE_API.md §2.6).
|
|
-- Nothing on the boot path ever executes this file — uninstalling a module
|
|
-- leaves its data alone, and removing the data is a separate decision an
|
|
-- operator has to make on purpose.
|
|
--
|
|
-- It exists because `schema.sql` does. A module that can create tables and
|
|
-- cannot drop them leaves an operator with orphaned data and no supported way
|
|
-- to remove it, which is why core refuses to load a module that declares one
|
|
-- without the other.
|
|
--
|
|
-- **The order is the reverse of creation, and that is load-bearing**: two of
|
|
-- these tables carry a foreign key into core's `users`, and several reference
|
|
-- each other. Dropping a parent before its children fails on the constraint,
|
|
-- and a purge that fails halfway is worse than one that does not run — it
|
|
-- leaves exactly the orphaned data this file exists to remove. `IF EXISTS` on
|
|
-- every line so a partially-installed module still tears down cleanly.
|
|
--
|
|
-- What is NOT here, deliberately: rows this module wrote into core's tables.
|
|
-- `notification_subs` rows for `shard.*` streams and `announce_job_legs` rows
|
|
-- with leg `towncrier` belong to core's tables, and a module does not delete
|
|
-- from those — core prunes them when it drops the registrations, which it can
|
|
-- do because it knows which registrant owned what. The two `settings` rows
|
|
-- schema.sql seeds (`game_account_signup`, `uo_link_protocol_3_migrated`) are
|
|
-- the same case with an extra reason: the second is a one-shot MIGRATION
|
|
-- marker, and deleting it would re-arm a protocol bump against tables this
|
|
-- file has just dropped.
|
|
|
|
-- The Asset Bridge's three (phase 3). No foreign keys of their own, so they lead:
|
|
-- `shard_creature_bodies.slug` mirrors an atlas slug and `shard_assets.body` a body
|
|
-- id, but neither is declared as a constraint — the atlas tables are rebuilt from
|
|
-- scratch on every refresh, and an FK into a table that is emptied and refilled
|
|
-- would make an ordinary re-parse fail on rows that are about to be re-inserted.
|
|
--
|
|
-- The uploaded PNGs are NOT removed here. They live under the uploads directory
|
|
-- alongside the operator's own artwork, this file drops tables rather than files,
|
|
-- and a purge that deleted an operator's hand-drawn creature portraits because
|
|
-- they shared a directory with imported ones would be unrecoverable.
|
|
DROP TABLE IF EXISTS `shard_asset_meta`;
|
|
DROP TABLE IF EXISTS `shard_creature_bodies`;
|
|
DROP TABLE IF EXISTS `shard_assets`;
|
|
DROP TABLE IF EXISTS `shard_atlas_pending`;
|
|
DROP TABLE IF EXISTS `shard_atlas_meta`;
|
|
DROP TABLE IF EXISTS `shard_cliloc_meta`;
|
|
DROP TABLE IF EXISTS `shard_clilocs`;
|
|
DROP TABLE IF EXISTS `shard_champion_spawns`;
|
|
DROP TABLE IF EXISTS `shard_landmarks`;
|
|
DROP TABLE IF EXISTS `shard_regions`;
|
|
DROP TABLE IF EXISTS `shard_spawn_point_types`;
|
|
DROP TABLE IF EXISTS `shard_spawn_points`;
|
|
DROP TABLE IF EXISTS `shard_spawn_creatures`;
|
|
DROP TABLE IF EXISTS `shard_feature_visibility`;
|
|
DROP TABLE IF EXISTS `shard_vendor_items`;
|
|
DROP TABLE IF EXISTS `shard_vendors`;
|
|
DROP TABLE IF EXISTS `shard_points_boards`;
|
|
DROP TABLE IF EXISTS `shard_ruleset`;
|
|
DROP TABLE IF EXISTS `shard_presence`;
|
|
DROP TABLE IF EXISTS `shard_governor_terms`;
|
|
DROP TABLE IF EXISTS `shard_governors`;
|
|
DROP TABLE IF EXISTS `shard_guild_members`;
|
|
DROP TABLE IF EXISTS `shard_guilds`;
|
|
DROP TABLE IF EXISTS `shard_pages`;
|
|
DROP TABLE IF EXISTS `shard_champs`;
|
|
DROP TABLE IF EXISTS `shard_account_links`;
|
|
DROP TABLE IF EXISTS `shard_houses`;
|
|
DROP TABLE IF EXISTS `shard_economy`;
|
|
DROP TABLE IF EXISTS `shard_online`;
|
|
DROP TABLE IF EXISTS `shard_events`;
|
|
DROP TABLE IF EXISTS `uo_link_config`;
|