They are gone now it’s on you to get good as people said
I’m not having any issues in BGs. I just thought it was odd that someone had that many KBs compared to everyone else.
Well the fact that u said Hunter says it they are overtuned
Someone else in that BG chat commented that the hunter could have solo’d our entire team. lol
Sounds like they’re just someone with Legion xpac still thats decked out in Antorus gear.
He was wearing “Heart of Azeroth” plus a couple other 300 items. He probably just unlocked XP.
There is another thread these same people are replying to with the answers on how this dude is exploiting the que system.
That just means that you also have BFA, hence the merged Expansion account.
The BFA gearing system will offer you much better choices, including three slots of AZ gear.
Dungeons, Quests are highly recommended.
Sounds about right. Thanks.
I was just in a 110 BG, and there was a Horde hunter with ilvl 254. He/she had 38 KBs in that BG!! The second highest was 9 KBs. Is this a situation someone simply not hitting 111 yet, or have some players figured out how to circumvent the XP off system?
My understanding is XP = Off means no twinks in regular BGs as of 8.1.5. Am I missing something?
Cool story. I had 138 kills in an AV once in the 80-84 twink bracket back in MoP with this toon. Loved getting those expensive blue MoP rare drops that were equippable at 81-84 ilevel (I’m still wearing them right now). Those BoEs cost a fortune but were worth it. I was one shotting groups with Chain Lightning. Then Blizz did their item squish and killed the bracket
Two ways to twink in XP on BGs that do not use any exploits:
- Be 110, don’t buy BFA–get good gear. You’re XP on with levelers
- Be 20, don’t activate your subscription–get good gear. You’re XP on with the levelers.
Other than that, people are either slow-rolling XP or just levelers that care to gear up. A few are using the exploit, but not many and that will get fixed.
They ended xp off for 110 months ago. That guy probably just doesn’t have BFA yet.
They ended xp off for 110 months ago
Incorrect. The “hotfix” was never implemented and Blizzard reversed their decision about that situation within hours.
For reference
Since the launch of Battle for Azeroth, we’ve noticed an increasing trend of players turning off XP gains at level 110 in order to repeatedly powerlevel other players’ characters at an excessive rate without increasing their own level. The intention of the XP-off feature is to allow alternate characters to stay in lower-level PvP brackets or relive lower-level content, not to purposefully halt progression in content relevant to the current expansion.
To curb this behavior, we plan to implement a hotfix in the coming days that will disable the ability to turn off XP gains on characters level 110 or higher. Additionally, any character of that level who already has XP disabled will find it automatically re-enabled the next time they log in.
We’ve been thinking about this plan more today and agree that there are probably better ways to approach this issue. We’re going to hold off on this for the time being while we discuss.
e: At least they got a warning about it though. Separation received no such treatment.
Oh wow. You don’t see that very often.
Or simply turn Xp on and que for bgs. You can eat up the Xp gained or leave before the bg is finished.
They ended xp off for 110 months ago. That guy probably just doesn’t have BFA yet.
Are you 100% sure about this? I’ve got two 110s that currently have their XP turned off simply because I don’t want to level them and they’re not getting any “forced xp” when I do things.
Are you 100% sure about this? I’ve got two 110s that currently have their XP turned off simply because I don’t want to level them and they’re not getting any “forced xp” when I do things.
No I was wrong. They announced it, then reversed their decision.
I just saw the previous poster’s post of the blue post. Thank Sylvanas! I was about to get worried there for a minute. I want to be able to do Legion endgame stuff at level, damnit!
Cheerios!
Now I’m confused too. I read about this on Wowhead as part of the 8.1.5 patch notes, but I can’t find any details on the official patch notes. Maybe this never happened.
I think they saw the error of their ways before it was too late…for once.