This is the best bug in the history of WCL. So every week this guild has been uploading Kaelthas kills in TBC Classic, and every week the fight turned into "Boar Normal".... A player in their raid is named Boar. He was - every week - becoming the boss of the fight.
The icon associated with the mighty Boar was Razorgore. Why Razorgore? So digging into the log file, the player's GUID (globally unique identifier) - by a complete coincidence - is 12435. This is the same id as the NPC id of Razorgore in BWL.
Now normally this would be fine. Encounters in World of Warcraft are determined by ENCOUNTER_START events. However, in the case of Kaelthas, there is extended RP that occurs and I have to tighten the fight boundary to cut out the ENCOUNTER_START and the RP dead time.
This results in Kaelthas having no encounter id until the ENCOUNTER_END is seen to establish the id. This is normally fine. Except for Boar.
There is special case code for Razorgore to cut out P1, since in the original Classic Vanilla, players wanted only P2 to be counted as part of ranks. This check for whether or not you were in P1 Razorgore and needed a split just checked for the id of 12435.
Because it did not also say "Oh hey are you an NPC, let's not do this for a player", the code triggered, and Razorgore became the boss fight. He can just name change to Razorboar and accept his status as a boss.
@KihraOfTemerity Holy shit this thread was a wild ride of weird coincidences
@KihraOfTemerity That's hilarious lmao, did the guild know all the time XD ? Wondering how it got unnoticed for weeks unless they digged the bug xD
@KihraOfTemerity @DeviousKat89 This is an incredible bug - two different edge case handlers + a coincidental ID match, massive props for catching it