prey

2026-08-22 21:22:31 -03:00
parent 5a724d4525
commit 71f9b205b3
1 changed files with 58 additions and 0 deletions
@@ -0,0 +1,58 @@
+
+DELETE FROM `quest_objectives` WHERE `ID` IN (473640, 473641, 473642, 473643, 473644);
+DELETE FROM `quest_template` WHERE `ID` IN (96591);
+
+INSERT INTO `quest_template`
+  (`ID`, `QuestType`, `QuestPackageID`, `ContentTuningID`, `QuestSortID`, `QuestInfoID`,
+   `SuggestedGroupNum`, `RewardNextQuest`, `RewardXPDifficulty`, `RewardXPMultiplier`,
+   `RewardSpell`, `Flags`, `FlagsEx`, `FlagsEx2`, `FlagsEx3`,
+   `AreaGroupID`, `TimeAllowed`, `Expansion`, `LogTitle`, `VerifiedBuild`)
+VALUES
+  (96591, 3, 0, 5381, -656, 295,
+   0, 0, 5, 1,
+   1241124, 37290240 /*0x2390100*/, 0, 0, 0,
+   8797, 0, 11, 'Prey: Venom Ambush', 0);
+
+INSERT INTO `quest_objectives`
+  (`ID`, `QuestID`, `Type`, `Order`, `StorageIndex`, `ObjectID`, `Amount`,
+   `ConditionalAmount`, `Flags`, `Flags2`, `ProgressBarWeight`, `ParentObjectiveID`,
+   `Visible`, `Description`, `VerifiedBuild`)
+VALUES
+  -- Type 3 = QUEST_OBJECTIVE_TALKTO
+  (473640, 96591,  3, 0,  3, 266443,  1, 0,  4, 0,  0, 0, 1, 'Crystal Imbued',  0),
+  -- Type 15 = QUEST_OBJECTIVE_PROGRESS_BAR (StorageIndex -1: not slot-backed)
+  (473641, 96591, 15, 1, -1,      0,  1, 0,  2, 0,  0, 0, 1, 'Ambush Foiled',   0),
+  -- Flags 92 = 0x5C, includes 0x40 PART_OF_PROGRESS_BAR -> ProgressBarWeight applies
+  (473642, 96591,  0, 2,  0, 266444, 10, 0, 92, 0, 10, 0, 1, '',                0),
+  (473643, 96591,  0, 3,  1, 266445, 20, 0, 92, 0,  5, 0, 1, '',                0),
+  (473644, 96591,  3, 4,  2, 266443, 50, 0, 92, 0,  2, 0, 1, '',                0);
+
+--
+-- 2. prey_hunt_template — fill in the hunt registry that
+--    `2026_08_12_00_world_prey_voidforge.sql` shipped empty.
+--
+--    `Id` is the hunt's quest id; PreyMgr keys the rotation off it.
+--    `ContentTuningId` was marked CAPTURE-BLOCKED in that file and is now known
+--    from the capture: 5224 Normal / 5223 Hard.
+--    `ZoneId` and `VaultActivityId` stay 0 — the capture carries neither, and a
+--    guessed zone id is worse than a missing one. PreyMgr treats ZoneId 0 as
+--    "any zone" so the weekly rotation still works, it just has one bucket.
+--
+--    These rows are inert: they only populate PreyMgr's lookup table. Nothing
+--    reads them on a player-visible path until the Hunt Table wire exists.
+--
+DELETE FROM `prey_hunt_template` WHERE `Id` IN
+  (91098, 91102, 91109, 91123, 91210, 91212, 91214, 91242, 91248, 91255);
+
+INSERT INTO `prey_hunt_template` (`Id`, `ZoneId`, `Difficulty`, `ContentTuningId`, `VaultActivityId`) VALUES
+  (91098, 0, 0, 5224, 0), -- Prey: L-N-0R the Recycler (Normal)
+  (91102, 0, 0, 5224, 0), -- Prey: Nexus-Edge Hadim (Normal)
+  (91109, 0, 0, 5224, 0), -- Prey: Petyoll the Razorleaf (Normal)
+  (91123, 0, 0, 5224, 0), -- Prey: Grothoz, the Burning Shadow (Normal)
+  (91210, 0, 1, 5223, 0), -- Prey: Magister Sunbreaker (Hard)
+  (91212, 0, 1, 5223, 0), -- Prey: Magistrix Emberlash (Hard)
+  (91214, 0, 1, 5223, 0), -- Prey: Senior Tinker Ozwold (Hard)
+  (91242, 0, 1, 5223, 0), -- Prey: High Vindicator Vureem (Hard)
+  (91248, 0, 1, 5223, 0), -- Prey: Knight-Errant Bloodshatter (Hard)
+  (91255, 0, 1, 5223, 0); -- Prey: Dengzag, the Darkened Blaze (Hard)
+