Skip playerbots so bot re-rolls don't spam the realm #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/skip-playerbots"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Upstream compiles clean against AzerothCore
efe123fab/ mod-playerbots8d9f6aa6(2026-08-14) -- all six TUs, no changes needed. The problem is behavioural, and specific to a Playerbots realm.PlayerbotFactorycallsPlayer::GiveLevel()in six places while randomising a bot, andGiveLevelfiresOnPlayerLevelChangedexactly as a real ding does. So every bot re-roll past 10/20/.../80 currently:X has reached Level Yto the whole server (twice -- per-level and reward-level)With 135 bot accounts cycling, that is close to continuous. Setting
CongratsPerLevel.Enable = 0does not fix it: the reward-level broadcast and raid warning sit outside that gate, and there is no upstream option to exclude bots.Change
Adds
Congrats.SkipBots, default1. The bot test isGET_PLAYERBOT_AI(player) != nullptr, guarded by#ifdef MOD_PLAYERBOTS-- the core applies-DMOD_PLAYERBOTSand all 105 playerbots include dirs to every module in themodulestarget when mod-playerbots is present, so this stays portable to a core built without it.Also adds the missing
overrideonOnPlayerLogin. The signature already matchedPlayerScript::OnPlayerLogin(Player*)so behaviour is unchanged; it just stops a future base-class change from silently detaching the hook.Verification
clang++ -fsyntax-only -DMOD_PLAYERBOTSagainst the live build's own flags plus the playerbots include tree: clean. Not built or run.Note
The two SQL files apply automatically --
Updates.EnableDatabases = 7,AutoSetup = 1. No collision atacore_string60000 and no existingmod_congrats_on_level_itemstable.