Update for 2026-07-07 core merge + upstream merge

[james-huston]

Part of the core catch-up merge to upstream npcbots_3.3.5 @ 665021b72 (core branch araxia-merge-20260707, see the core repo's MERGE_20260707.md). Validated: full worldserver build with all 10 modules static-linked, plus a boot test against a copy of the production DB (all module SQL applied, server reached the client-data stage cleanly).

• Renamed 2024_11_10_04.sql → 2024_11_10_04_mod_premium_menu.sql: the core ships an (archived) update with the same name and the DB updater aborts on duplicate filenames — this blocked worldserver startup
• Fixed that file's DELETE range (0–9) to cover all inserted OptionIDs (0–13) so re-application is idempotent — it had duplicate-key failures against the production data
• Merged azerothcore master (5 commits, clean merge)

Note: araxia-builder/config.yml points this module at azerothcore/mod-premium — it should point at araxiaonline/mod-premium (this repo).

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request updates SQL scripts for a premium item and menu options, and reorders include directives in src/premium.cpp. Specifically, it removes the StatsCount column and resets VerifiedBuild for the premium item, and expands the range of deleted OptionIDs in the gossip menu update script. Feedback suggests replacing the discouraged REPLACE INTO statement with a DELETE and INSERT INTO sequence in the premium item SQL script to comply with AzerothCore SQL standards.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

According to the AzerothCore SQL standards, using REPLACE INTO is discouraged. Instead, we should always perform a DELETE statement before an INSERT INTO statement to ensure clean re-application and prevent duplicate key issues or other errors.

Let's replace the REPLACE INTO statement with a DELETE followed by an INSERT INTO statement.

DELETE FROM `item_template` WHERE `entry` = 9017;
INSERT INTO `item_template` (`entry`, `class`, `subclass`, `SoundOverrideSubclass`, `name`, `displayid`, `Quality`, `Flags`, `FlagsExtra`, `BuyCount`, `BuyPrice`, `SellPrice`, `InventoryType`, `AllowableClass`, `AllowableRace`, `ItemLevel`, `RequiredLevel`, `RequiredSkill`, `RequiredSkillRank`, `requiredspell`, `requiredhonorrank`, `RequiredCityRank`, `RequiredReputationFaction`, `RequiredReputationRank`, `maxcount`, `stackable`, `ContainerSlots`, `stat_type1`, `stat_value1`, `stat_type2`, `stat_value2`, `stat_type3`, `stat_value3`, `stat_type4`, `stat_value4`, `stat_type5`, `stat_value5`, `stat_type6`, `stat_value6`, `stat_type7`, `stat_value7`, `stat_type8`, `stat_value8`, `stat_type9`, `stat_value9`, `stat_type10`, `stat_value10`, `ScalingStatDistribution`, `ScalingStatValue`, `dmg_min1`, `dmg_max1`, `dmg_type1`, `dmg_min2`, `dmg_max2`, `dmg_type2`, `armor`, `holy_res`, `fire_res`, `nature_res`, `frost_res`, `shadow_res`, `arcane_res`, `delay`, `ammo_type`, `RangedModRange`, `spellid_1`, `spelltrigger_1`, `spellcharges_1`, `spellppmRate_1`, `spellcooldown_1`, `spellcategory_1`, `spellcategorycooldown_1`, `spellid_2`, `spelltrigger_2`, `spellcharges_2`, `spellppmRate_2`, `spellcooldown_2`, `spellcategory_2`, `spellcategorycooldown_2`, `spellid_3`, `spelltrigger_3`, `spellcharges_3`, `spellppmRate_3`, `spellcooldown_3`, `spellcategory_3`, `spellcategorycooldown_3`, `spellid_4`, `spelltrigger_4`, `spellcharges_4`, `spellppmRate_4`, `spellcooldown_4`, `spellcategory_4`, `spellcategorycooldown_4`, `spellid_5`, `spelltrigger_5`, `spellcharges_5`, `spellppmRate_5`, `spellcooldown_5`, `spellcategory_5`, `spellcategorycooldown_5`, `bonding`, `description`, `PageText`, `LanguageID`, `PageMaterial`, `startquest`, `lockid`, `Material`, `sheath`, `RandomProperty`, `RandomSuffix`, `block`, `itemset`, `MaxDurability`, `area`, `Map`, `BagFamily`, `TotemCategory`, `socketColor_1`, `socketContent_1`, `socketColor_2`, `socketContent_2`, `socketColor_3`, `socketContent_3`, `socketBonus`, `GemProperties`, `RequiredDisenchantSkill`, `ArmorDamageModifier`, `duration`, `ItemLimitCategory`, `HolidayId`, `ScriptName`, `DisenchantID`, `FoodType`, `minMoneyLoot`, `maxMoneyLoot`, `flagsCustom`, `VerifiedBuild`) VALUES (9017, 9, 0, -1, 'Book of Powers', 1143, 7, 0, 0, 1, 0, 0, 0, -1, -1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 54406, 0, 0, 0, -1, 0, -1, 0, 0, 0, 0, -1, 0, -1, 0, 0, 0, 0, -1, 0, -1, 0, 0, 0, 0, -1, 0, -1, 0, 0, 0, 0, -1, 0, -1, 0, 'Premium Account Magic!
Use with caution!

Allowed by Brann Bronzebeard!', 0, 0, 0, 0, 0, -1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, -1, 0, 0, 0, 0, 'premium_account', 0, 0, 0, 0, 0, 0);

References

1. AzerothCore SQL Standards require using DELETE before INSERT instead of REPLACE INTO to ensure clean re-application. ^(link)