-
QOL Patch
After the recent ban of a QOL patch called AwesomeWotlk I've seen a decent number of people complain because they are losing some really nice QOL features that it provided. My interpretation of why it was banned judging from staff messages I've seen is that it allowed Addons functionality that they aren't supposed to have which in turn resulted in it being abused and giving unfair advantage in PVP. From what I've seen staff members post Warmane would be ok with the QOL uses but can't allow the abusive/cheating uses of the patch and since there is no way to partially pick and choose what's allowed, and it's either all or nothing, the patch got banned.
My suggestion is similar to what was done with multiboxing. The patch could be allowed exclusively while inside raid instances, with a small grace period to re-enter the instance after a wipe. This would allow players to have a separate "patched" client that they can specifically use while in raids. All the weakauras and addons that depend on the patch could also be configured to load only while inside a raid, giving players the raiding experience they desire while also keeping it fair for PVP.
All this is based of my understanding of the situation so I'm sorry if I misunderstood something.
-
Yes, you misunderstood. Considering I was likely the one that gave the majority of replies about the subject, it's a bit odd that you missed the most important part: there's no "kinda" allow it; either the client trying to use stuff it shouldn't triggers Warden or it's forced to not be triggered; it's something server-wide, there's no "ban it almost everywhere."
-
I have no idea how Warden works, figured it might be able to check if player is in ICC or Ulduar or another raid when it gets triggered and if they are in a raid not kick them so I just posted this on the off chance that it was possible. Understandable if it's not.
-
No, it checks if something protected is being accessed, so to say. It doesn't matter where someone is at or what they are using it for. Either it's acted on or or it isn't, because they are stuff players shouldn't have access to in the first place, so the game's anti-cheat wasn't built to have any conditionals when it detects something that shouldn't happen.
If there was a way to filter it somehow, we would have tried. The devs didn't want to disable it because of the positives, but can't leave it allowed due to the negatives.