I believe everyone in TBCC community by now is familiar with the whole “drums” change (at least anyone that cared about it). Drums were strong and desirable to the point that you wanted 4 people in your group to be able to use them. This led to Blizz giving the drums a 2 min CD so that players didn’t feel like they had to use a team of drummers.
This is happening again with battle chickens. Thats right, the wimpy mechanical chickens spawned from engineering… They have a powerful 5% haste buff that lasts 5 minutes that stacks. Throughout Classic and early TBCC we didn’t know there was a way to guarantee a proc, so it was just kinda a “chance” tool to see if you could proc it before a boss fight, or you spawn it during the boss fight and hope it gives the “squawk” buff.
Somewhat recently though, it was discovered how to guarantee a squawk. Since this discovery the parse meta has completely shifted towards “chickens chickens chickens!” and there’s not much the player base or Warcraft logs can do about it. My understanding of it is that it’s a long enough buff that sometimes it can go completely undetected, or it has difficulty being shown in the combat log. So as a parsing community there’s no way to “ban” it or flag it as “this parse had this many squawks” similar to how we have lusts and other singular buffs.
I think most would agree that the squawks from chickens shouldn’t stack at all. It doesn’t seem all that authentic, even if it was possible in TBCC, because it’s such a powerful buff especially when stacked together. 25% if additive or 27.6% haste if multiplicative (can’t remember which). For comparison, drums is about 5% haste. From a design standpoint, adjusting a buff that was only 5% haste there should definitely be removal of the stacking nature of these buffs which is 5x the amount.
Whether it’s providing players and the parsing community with methods to handle it ourselves via better combat log detection (similar to lust or long duration buffs) or the much preferred method of making it not stack, it really feels like this should be looked at to keep the feel of the parsing community authentic.