wtclaude
aea94b5d7a
- Schema: fourteen title columns on rust_player_wipe_stats (the two best_* distances move by GREATEST, the rest are sums), rust_weapon_kills (kills by weapon prefab name) and rust_title_categories (the admin's title per category). purge.sql drops the two tables. - Ingest: player.tally's new fields, in one statement per frame, none for an older plugin's frame. - Titles: 23 categories plus playtime, each naming where it is read from (a sum, a MAX, npc_kills - animal_kills in signed arithmetic, or a named list). The bow/melee/blade/revolver/wood/ore/plants lists are one file, applied when a title is read. "NPC kills" ranks human NPCs only (D209). - A rule's text may be empty, meaning the category's title: the rule's own, then the admin's, then the default. Typed-only-markup is still refused. A rename forgets every server's cached answer. - Admin API: GET /admin/rust/title-categories and PUT /admin/rust/title-categories/:stat (empty text resets); the server list returns them too. Swagger fragment and routes.manifest.json regenerated (63 routes, against the pinned core). - Screen: every category in the rule form, the category's title as a placeholder, and a Category titles section with Save and Reset. The weapon lists are unverified until the rig probe runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
78 lines
3.3 KiB
SQL
78 lines
3.3 KiB
SQL
-- ── The teardown ──────────────────────────────────────────────────────────
|
|
--
|
|
-- Destructive, and run ONLY by an explicit admin purge (MODULE_API.md §2.6).
|
|
-- Nothing on the boot path executes this file, and uninstalling the module does
|
|
-- not either: removing an operator's data is a second decision they make on
|
|
-- purpose, offered inside the uninstall flow and confirmed separately.
|
|
--
|
|
-- 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, so core refuses to load a module that declares one without the
|
|
-- other.
|
|
--
|
|
-- **Drop in the reverse of creation order**, which this file depends on:
|
|
-- `rust_server_state` carries a foreign key into `rust_servers`, so dropping the
|
|
-- parent first fails on the constraint — and a purge that fails halfway leaves
|
|
-- exactly the orphaned data it exists to remove.
|
|
--
|
|
-- What does NOT belong here: rows written into core's tables. Core prunes what
|
|
-- it knows this module registered, because it is the side that knows which
|
|
-- registrant owned what.
|
|
|
|
-- The chat-title conditions (PLAN_REDESIGNS §5). No foreign keys; the stats
|
|
-- columns go with their table below.
|
|
DROP TABLE IF EXISTS rust_title_categories;
|
|
DROP TABLE IF EXISTS rust_weapon_kills;
|
|
|
|
-- The permission manager, rebuilt (PLAN_REDESIGNS §1). Children before
|
|
-- `rust_permgroups`, which they reference.
|
|
DROP TABLE IF EXISTS rust_perm_exceptions;
|
|
DROP TABLE IF EXISTS rust_perm_steam_grants;
|
|
DROP TABLE IF EXISTS rust_permgroup_chat;
|
|
DROP TABLE IF EXISTS rust_permgroup_steam_members;
|
|
DROP TABLE IF EXISTS rust_permgroup_members;
|
|
DROP TABLE IF EXISTS rust_permgroup_permissions;
|
|
DROP TABLE IF EXISTS rust_permgroup_servers;
|
|
DROP TABLE IF EXISTS rust_permgroups;
|
|
|
|
-- Phase 17. `rust_perm_group_chat` before `rust_perm_groups`, which it
|
|
-- references; the rest of this phase is columns, which go with their tables.
|
|
DROP TABLE IF EXISTS rust_perm_group_chat;
|
|
DROP TABLE IF EXISTS rust_title_rules;
|
|
|
|
-- Phase 14.
|
|
DROP TABLE IF EXISTS rust_map_overrides;
|
|
DROP TABLE IF EXISTS rust_map_images;
|
|
|
|
-- Phase 13b.
|
|
DROP TABLE IF EXISTS rust_perm_run_grants;
|
|
|
|
-- Phase 7b.
|
|
DROP TABLE IF EXISTS rust_clan_boards;
|
|
DROP TABLE IF EXISTS rust_clan_members;
|
|
DROP TABLE IF EXISTS rust_clans;
|
|
DROP TABLE IF EXISTS rust_settings;
|
|
DROP TABLE IF EXISTS rust_config_writes;
|
|
|
|
-- Phase 7. Children before parents: every one of these carries a foreign key
|
|
-- into `rust_servers`, `users` or `rust_perm_groups`.
|
|
DROP TABLE IF EXISTS rust_perm_catalogue;
|
|
DROP TABLE IF EXISTS rust_perm_sync;
|
|
DROP TABLE IF EXISTS rust_perm_revocations;
|
|
DROP TABLE IF EXISTS rust_perm_drift;
|
|
DROP TABLE IF EXISTS rust_perm_pushed;
|
|
DROP TABLE IF EXISTS rust_perm_grants;
|
|
DROP TABLE IF EXISTS rust_perm_group_members;
|
|
DROP TABLE IF EXISTS rust_perm_group_permissions;
|
|
DROP TABLE IF EXISTS rust_perm_groups;
|
|
DROP TABLE IF EXISTS rust_account_links;
|
|
DROP TABLE IF EXISTS rust_ingest_cursor;
|
|
DROP TABLE IF EXISTS rust_presence;
|
|
DROP TABLE IF EXISTS rust_events;
|
|
DROP TABLE IF EXISTS rust_gather_totals;
|
|
DROP TABLE IF EXISTS rust_player_wipe_stats;
|
|
DROP TABLE IF EXISTS rust_players;
|
|
DROP TABLE IF EXISTS rust_wipes;
|
|
DROP TABLE IF EXISTS rust_server_state;
|
|
DROP TABLE IF EXISTS rust_servers;
|