WoW Classic Hotfix -- Raid Party XP Bug

This was documented day 1, you guys are imbeciles for only recognizing it now. Every major streamer was like “we are getting way too much experience for this raid group”.

Try playing the games you create on occasion you might do a better job retaining a player base.

1 Like

This wasn’t in the original game they screwed up xp scaling. It should have been fixed in beta since it wasn’t they should just roll people back because right now 60s control the economy completely.

1 Like

So the issue was just that there was a group bonus instead of a raid penalty? A hefty oof, but that doesn’t really change my point.

You’re still getting reduced XP per kill than you would as an individual because you’re in a large sized raid group, as intended and advertised. The catch is that instead of the raid penalty you still got the group bonus. This is completely a fault on Blizzard’s end and does not require any peculiar tricks on the player’s behalf to trigger this.

Net XP per kill individually is reduced. Net total XP across the group per kill is higher. Someone at Blizzard forgot to turn on raid penalties. There’s still nothing illegitimate about bringing 10 people to a 5 person dungeon.

Again, I’m not defending this nor am I on Blizzard’s side for taking so long to fix something that was known in advance. I still cannot possibly take the side that this was an exploit or that anyone should be punished for it.

We’re talking hours of difference, not days, they’d still be 60 regardless.

Rag may have died early today instead of later yesterday, very little would have changed

I’m not going to convince you otherwise you think people are allowed to be ignorant, I don’t.

People shouldn’t be punished for playing the game in ways that the game supports just because someone at Blizzard can’t do math.

The only time Blizzard should actively intervene is if the problem is so massively disruptive that it has long-term detrimental effects, or if the bug is something that requires a technique that directly implies exploitative intent (XP Potion).

Shaving a few hours off of leveling speed because raids weren’t flagged to have a penalty and, despite still yielding less XP per kill per player it is efficient XP/h, is simply not an exploit.

Not at all. It would have taken at least 2 or three extra days for them to level, as most of APES are not speed levelers.

They weren’t going that much slower in 5 man groups dude, 10 man was just simpler and actually less XP per person

Slower enough that the World First Rag was predicated on being using this raid exploit…

1 Like

Again you think getting triple xp total is less efficient, how does that make sense to you. Each individual person was gaining 90xp per time spent compared to 45. What logic are you following. Would 40 mans convince you? 40x22.5 at 8x speed = 7200xp compared to a 5man getting 375xp? How far is too far?

1 Like

Lol thats retarded

You mean their levels decreased by 10%?

Why would you make that so wordy?

According to your own math, unless I misread it multiple times, XP per kill per player is reduced per player in the raid. Which is intended.

As a group, any individual kill yields more cumulative XP as a group than the kill would have been worth solo, which is also intended.

By extension, this would have extended into raids if Blizzard had not deliberately created a penalty for participating in raids - which is seemingly what was not working, and by no fault nor action on behalf of the players.

The problem here was that Blizzard messed up how XP rewards are calculated in a raid group, which is Blizzard’s fault. You were still limited by the number of players that could enter a dungeon (which was 10, and is intentional), and the consequence of the miscalculation was that groups of 10 players in content tuned for 5 happened to yield more XP per hour overall than intended.

Indeed, I still would not have been convinced even if you could bring 40 players into a 5-person raid, because despite being hilariously overkill and clearly not what the dungeons were designed for, it still would have been a perfectly legitimate way to run the dungeon. Now, if you said that you couldn’t have 40 people walk into a dungeon but you could have a warlock summon them inside (can they even do that in Classic?) to bypass the 10 person limit, then I’d be in agreement.

Well, inb4 the second part of this exploit is found, which I guess I’ll keep to myself since blizz is clearly not suspending people.

What? I don’t even know what you are trying to say honestly.

World First rag was predicted to be week one before anyone knew this even worked.

This topic is not an exploit. Without knowing what you’re referring to, you might know something that is an exploit.

You could always report it in-game or make a post on the bug report board and immediately edit it out. They can view edits. I advocate for both.

They actually seem like they intend to fix problems with Classic. Meanwhile I’m still waiting for the Ret Paladin bug on live that allows me to put anything I can see in combat regardless of range or LoS indefinitely to be fixed despite reporting it constantly for the past year. Still surprised I don’t see it getting used in arenas especially during the drink-heavy meta, but I don’t think many people have found it yet somehow.

I was actually extremely impressed with the achievement, but now I wonder how many other guilds could have had an honest race with them if the exploit wasn’t used. It could have been an exciting event.

It’s the same exploit, therefore I know I won’t be suspended. Just an alternative way of doing it.

You tell people how to do the ret paladin thing, spread it around, it’ll get fixed fast.

Could a real beta prevented this, awful amateur launch? Or, did you REALLY need streamers and a paywall for beta and stress tests? Because you guys look completely lost, with the launch and game changing bugs…

2 Likes

Not sure how it can be the same exploit if the problem was just that raid groups were flagged incorrectly.

And yeah I’ve considered that, but I’ve turned this into an experiment to see how long Blizzard takes to fix a bug that is completely gamebreaking when it hasn’t been shown on stream or something.