Mythic+: Phase 3 - death penalty, run scoring and best-run persistence

This commit is contained in:
luis
2026-07-03 21:29:27 -03:00
parent 98eadcf622
commit c68f9b6906
13 changed files with 294 additions and 35 deletions
-24
View File
@@ -1,24 +0,0 @@
build*/
.directory
.mailmap
*.orig
*.rej
*~
.hg/
*.kdev*
.DS_Store
CMakeLists.txt.user
*.bak
*.patch
*.diff
*.REMOTE.*
*.BACKUP.*
*.BASE.*
*.LOCAL.*
nbproject/*
.idea/*
.browse.VC*
.vscode
cmake-build-*/
.vs
@@ -0,0 +1,18 @@
--
-- Mythic+ (Challenge Mode): per-character best-run storage.
--
CREATE TABLE IF NOT EXISTS `character_mythic_plus` (
`guid` bigint unsigned NOT NULL DEFAULT 0 COMMENT 'Global Unique Identifier',
`challengeModeId` int unsigned NOT NULL DEFAULT 0 COMMENT 'MapChallengeMode.db2 ID',
`level` int unsigned NOT NULL DEFAULT 0 COMMENT 'Keystone level of the best run',
`durationMs` int unsigned NOT NULL DEFAULT 0 COMMENT 'Effective run time in milliseconds (incl. death penalty)',
`deaths` int unsigned NOT NULL DEFAULT 0,
`completionDate` bigint NOT NULL DEFAULT 0 COMMENT 'Unix time of the run',
`score` float NOT NULL DEFAULT 0,
`affix1` int unsigned NOT NULL DEFAULT 0,
`affix2` int unsigned NOT NULL DEFAULT 0,
`affix3` int unsigned NOT NULL DEFAULT 0,
`affix4` int unsigned NOT NULL DEFAULT 0,
PRIMARY KEY (`guid`,`challengeModeId`),
CONSTRAINT `fk_character_mythic_plus_character` FOREIGN KEY (`guid`) REFERENCES `characters` (`guid`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Mythic Keystone best runs';