Title says it all. Its been confirmed that in Classic, a realm transfer will have your raid lockouts transfer with you. This wasn’t hot fixed until sometime in 2012 (no official notes, only forums talking about the change.)
If they reverted it back to how it should be, could people then ring the AQ gong within 24hours? Why is this not in the #nochanges discussion?
So you can get 2 MCs and 2 BWLs in one week? Ha, thats a good one.
No changes.
You do understand you’re contradicting yourself, right?
You used to be able to reset raid lockouts when realm transferring in Vanilla. Its been changed in Classic however.
How often does this really come up? When prioritizing bug fixes, responsible software teams consider the risk to reward ratio. In this case, there’s no reason to potentially destabilize the code base to address a concern that will only come up a handful of times on any given account at most. You can survive one week without raiding on your new server. Also, to be honest, the current design feels right. The change you’re proposing sounds very much like enabling an exploit, and Blizzard has demonstrated time and again that they’re perfectly fine with #changes that prevent exploits.
i believe it was STARS in TOC (tier 9) that showed us why thats a bad idea…
Not the point.
That’s great you feel that way. However it’s not authentic to Vanilla.
No. I’m asking for it to not be changed. In Vanilla, your raid id would reset on transfer. It was something some considered built into the price. An extra raid along with the transfer for the total price.
Which is exactly pointing out to why it should be in Classic. Wasn’t changed until a ways down the road.
They allow the abomination that is spell batching, but rob people of an extra raid lockout after paying money in a fair amount of cases. Why do they only replicate the technologies that don’t benefit the players?
If they really considered it that way, they wouldn’t have hot fixed it. They don’t hot fix features. That’s typically reserved for exploits. You may not see it as an exploit, but since you’re not making the decisions at Blizzard, that’s irrelevant. They clearly see it that way. An exploit falls under the list of approved changes for Classic. You can raid again next week. It’ll be OK.
They kept it that way for all of Vanilla, TBC, and most of WotLK. It obviously wasn’t too much of an issue.
Sure. Great assessment. I just want the game to be authentic as it can be. “Warts and all.”
Again, not the point. I want them to be consistent in their message. This isn’t authentic to Vanilla.
This is clearly against the #nochanges attitude. Saying its an exploit is a bit overkill isn’t it? Considering you can only transfer once every 3months?
Why would they bothered to have hotfixed it if it wasn’t an exploit? You have yet to answer that.
Because a guild in Taiwan abused it in a world first race during TotGC. There are no world first raids in Classic thankfully.
In other words, a guild exploited it, and Blizzard woke up to the fact that it was an exploit. What’s seen cannot be unseen.
You’re only reading what you want to.
It was for a World First race. That of which does not exist in the ways of Classic the ways it did then.
The exploit got their attention because it altered the results of a world first race. That doesn’t make it any less of an exploit at any other time. Also, they still have world first races. In case you missed the big announcement:
Do you NEED to do the raid twice in one week? No you don’t. Wait a week then raid.
Go do research on what TotGC was and how a fresh lockout can alter that in a World Race.
How would getting a fresh raid lockout help in a World race in Classic? Your toon wouldn’t be done transferring by the time a raid is cleared.
Not the point. But great job anyways.
If there’s no race for world firsts in classic, then why was there streams and events dedicated to world first L60, and world first Classic MC when classic launched? Why did blizzard have a CM make a post here on the forums stating who won the race for first BWL clear? It sure seems like world first is a thing in classic. Check Warcraft logs, it even has a tab showing which guilds cleared which raids first.
It sounds like you’re the one reading what you want.
Regardless of any witty banter from random community members on the forums, if blizzard removed it then it was likely done to stop exploiting. If you’re getting multiple raid lockouts in a single week, or y happy that you can’t, many would argue that’s evidence of an exploit.
You should really understand a post before you comment.
Again. Blizzard removed the ability to cheese a second raid lockout in 1 week because it was an exploit. Regardless of who exploited it or when. They discovered an exploit and patched it out. Case closed.
It was an exploit in a raid that doesn’t exist in Classic.
What about the #nochanges?
They explained this before Classic released right here:
Additional improvements will include modern anti-cheat/botting detection, customer service and Battle.net integration, and similar conveniences that do not affect the core gameplay experience.
Fixing an exploit that does not affect the core gameplay experience falls into this category.