Paragon: Builds QoL -- share codes, unload, remaining AE/TE on hover

- Replace the "favorite" toggle with import-by-share-code: every build gets a 6-char realm-unique alphanumeric code on creation; pasting one into the BuildsPane share box copies the recipe (name + icon + spells + talents) into the importer's catalog as a new build, with a fresh share code so the imported copy can be re-shared independently. - Add C BUILD UNLOAD verb so the client can clear a stale active-build pointer without forcing a swap. Wired to a new "Unload (clear active)" right-click context menu entry on the active build. - Per-build tooltip now shows "Remaining if loaded: X AE / Y TE", computed server-side as total_earned - recipe_cost. Negative renders red so the player sees insufficient-currency cases before clicking Load. Suppressed for the active build (HandleBuildLoad short-circuits on target == active so the line would be misleading). - Schema migration 2026_05_10_04.sql: drop is_favorite from character_paragon_builds and add share_code CHAR(6) UNIQUE NULL with lazy backfill on every PushBuildCatalog (so pre-migration rows pick up codes the first time the player opens the panel). Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-10 04:15:11 -04:00
parent 7de018f7eb
commit a251e56c59
2 changed files with 416 additions and 29 deletions
@@ -0,0 +1,30 @@
+-- mod-paragon Character Advancement: Builds catalog schema cleanup.
+-- ----------------------------------------------------------------------------
+-- Two changes:
+--   1. Drop `is_favorite` -- the favorite flag and shift-click-to-favorite
+--      flow are removed. Builds are now ordered solely by build_id ASC.
+--   2. Add `share_code` CHAR(6) -- a random alphanumeric token generated
+--      server-side at build creation that uniquely identifies a saved
+--      build across the realm. Players exchange codes out-of-band and
+--      use the BuildsPane "Load Build!" share box to import a copy of
+--      the build (name + icon + spell + talent recipe) into their own
+--      catalog. The copy gets a fresh share_code so re-sharing is
+--      always traceable to the latest owner; the original isn't touched.
+--
+-- The column is NULL-tolerant so any rows that pre-date this migration
+-- (created under 2026_05_10_03's schema) coexist cleanly. The server
+-- backfills NULLs lazily in PushBuildCatalog -- the next time a player
+-- opens the BuildsPane on a Paragon character, any of their builds that
+-- still have a NULL share_code will get one generated and persisted.
+--
+-- Charset: 31 unambiguous chars (A-Z minus I/O minus 0/1) gives 31^6 ~=
+-- 887M codes; collision retry on insert keeps probability of a duplicate
+-- vanishing for any realistic catalog size.
+-- ----------------------------------------------------------------------------
+
+ALTER TABLE `character_paragon_builds`
+    DROP COLUMN `is_favorite`,
+    ADD COLUMN `share_code` CHAR(6) NULL DEFAULT NULL
+        COMMENT 'random alphanumeric token for import-by-code; lazily generated'
+        AFTER `icon`,
+    ADD UNIQUE INDEX `uk_share_code` (`share_code`);