Prey Fixed

sql/updates/world/master/2026_09_26_00_world.sql

@@ -0,0 +1,40 @@
+-- ============================================================================
+-- Prey / hunt-table POI fix for the world-quest (AdventureMapPOI) gate.
+-- Symptom fixed: hunt prey POIs never appear on the map for any player.
+--
+-- Ground truth: retail digest of build 69273 (your own capture) proves these
+-- world states are published __realm-wide__ (no map restriction) each week:
+--   regular hunt  : 28970..28999  (14 of them offered weekly, slot 1..14)
+--   nightmare hunt: 30629,30630,30631,30632 (the 3 offered specials)
+-- Retail WorldQuestMgr (WorldQuestMgr.cpp) only sends a template's VariableID as
+-- a __realm-wide__ init world state when the matching `world_state` row is NOT
+-- restricted to a specific map. A MapIds-restricted row suppresses the POI for
+-- everyone (the code warns exactly about this at WorldQuestMgr.cpp ~99-105).
+--
+-- Fix: ensure these hunt world states exist with EMPTY MapIds (realm-wide) and
+-- default value 0 (target not offered). Ids must not collide with existing rows.
+-- ============================================================================
+
+-- 1) Hunt world-state rows, realm-wide (no map restriction), default 0.
+SET @wsHigh := (SELECT COALESCE(MAX(Id), 0) FROM world_state);
+INSERT INTO world_state (Id, WorldStateId, MapIds, Value) VALUES
+-- slot 1..14 are the "regular" hunt targets; 30 world states in retail 28970..28999
+(@wsHigh + 1,  28970, '', 0), (@wsHigh + 2,  28971, '', 0), (@wsHigh + 3,  28972, '', 0),
+(@wsHigh + 4,  28973, '', 0), (@wsHigh + 5,  28974, '', 0), (@wsHigh + 6,  28975, '', 0),
+(@wsHigh + 7,  28976, '', 0), (@wsHigh + 8,  28977, '', 0), (@wsHigh + 9,  28978, '', 0),
+(@wsHigh + 10, 28979, '', 0), (@wsHigh + 11, 28980, '', 0), (@wsHigh + 12, 28981, '', 0),
+(@wsHigh + 13, 28982, '', 0), (@wsHigh + 14, 28983, '', 0), (@wsHigh + 15, 28984, '', 0),
+(@wsHigh + 16, 28985, '', 0), (@wsHigh + 17, 28986, '', 0), (@wsHigh + 18, 28987, '', 0),
+(@wsHigh + 19, 28988, '', 0), (@wsHigh + 20, 28989, '', 0), (@wsHigh + 21, 28990, '', 0),
+(@wsHigh + 22, 28991, '', 0), (@wsHigh + 23, 28992, '', 0), (@wsHigh + 24, 28993, '', 0),
+(@wsHigh + 25, 28994, '', 0), (@wsHigh + 26, 28995, '', 0), (@wsHigh + 27, 28996, '', 0),
+(@wsHigh + 28, 28997, '', 0), (@wsHigh + 29, 28998, '', 0), (@wsHigh + 30, 28999, '', 0),
+-- the 4 Nightmare special hunt world states
+(@wsHigh + 31, 30629, '', 0), (@wsHigh + 32, 30630, '', 0),
+(@wsHigh + 33, 30631, '', 0), (@wsHigh + 34, 30632, '', 0);
+
+-- 2) sanity check: exactly the 34 realm-wide hunt rows must now exist.
+-- SELECT WorldStateId, MapIds, Value FROM world_state
+--   WHERE WorldStateId BETWEEN 28970 AND 28999 OR WorldStateId BETWEEN 30629 AND 30632
+--   ORDER BY WorldStateId;
+-- Expected: 34 rows, every MapIds empty, every Value 0.