This is actually a massive difficulty adjustment for many encounters, which should not happen in classic.
Blizzard, please limit this change to retail. Don’t screw with the classic APIs that have been in the game for over a decade.
This is actually a massive difficulty adjustment for many encounters, which should not happen in classic.
Blizzard, please limit this change to retail. Don’t screw with the classic APIs that have been in the game for over a decade.
about as helpful as this was.
Kinda doesn’t. They can remove DBM but they need to work on how raid mechanics present themselves. Ion himself has talked about this and how they want to improve this to make addons less necessary
To all the players saying advocating for this change based on the reasoning that the game should be harder:
Players spent WEEKS testing encounters in ICC to ensure they were fine-tuned to the exact difficulty that was present in the original release of the raid. Now Blizzard chucks an absurd API change that steps up the de-facto difficulty by a large margin on many fights. This effectively negates all of that tuning. How is this a sensible change?
Range indicator to get a radar to show distances between people. OK
Bite Indicator which weighs damage meter and proximity to auto assign bite targets for you. Not OK (proximity relies on the range API)
This change makes perfect sense in retail, where Blizzard will be designing encounters around the fact that players no longer have the ability to check their range with addons. In retail, Blizzard has the ability to add visual cues to future content that can indicate player range, which is what they plan to do (and already do to an extent).
That is NOT the case in classic. We’re mid-way through the last raid tier in the expansion. Blizzard will NOT be re-visiting ICC encounters and adding visual effects to achieve this goal. The encounters are set. This change is being made for reasons that literally do not apply to WoW Classic.
is this like
/range 10 command? that would show me who is in range or not?
afaik it does not affect range indicators on Vuhdo/healbot/other healing addons.
Yeah, “/range x” is a DBM function to pop up a radar.
The fading of unit frames (or highlighting red, or w/e) is based on a different API which I don’t think is affected.
Range can figure out where in relation someone else is to you. The unit frames range indicator just says “they are somewhere within 40 yards, but I’m not sure if they are north or south of me”. So Vuhdo’s out of range arrow should stop working, but not that they are out of range of your spells.
I think community mods can make any game better but with limits. A game developer shouldn’t have to rely on the community but it’s absurd to expect a company to make a perfect game for everyone. That’s were the community can take it to the next level with quality of life changes that make the game more fun and customizable for the individual. A game without any kind of mod support won’t last long. Its up to blizzard to draw the line at what’s acceptable. I just think they are wrong in the case.
I was just referring to the combat based addons. UI addons and stuff is fine in my opinion.
FF14 doesn’t allow addons and it does fine. Yeah, some people have worked around that, but I believe that the majority of raiders aren’t using any combat addons to help out with a fight.
Hopefully this will be addressed and adjusted for non-retail versions but probably tricky due to shared API.
While I don’t disagree that this sort of functionality makes the encounter easier, even in the case that you point the difference is hardly substantial. Having the raid lead watch the damage meter and call out who to bite is like 90% as effective. We’re probably talking about a <5% DPS loss, and probably more like 2-3%. This comes nowhere near trivializing the encounter.
Blizzard’s sledgehammer approach, which breaks a fundamental tool that players have been using since inception, because an addon makes an encounter or two 2-3% easier, is asinine.
It’s not that tricky. It’s actually trivial, and probably requires than 5 lines of code on Blizzard’s end. There are literally dozens of instances where an API call is implemented for Retail and not for Classic, and vice versa. It’s not hard, conceptually, design-wise or in terms of implementation. They do it all the time.
I confirm you that if i dont have /range available, i will be a friendlyfire bomb hahaha
To highlight why this change is bad, consider the Deathbringer Saurfang fight.
Its called eyeballs. Use them.
but where did blizz confirm this?
Show me the mechanic/feature Blizz put in to be aware that you might be too close to someone. Oh, that’s right, you can’t because there isn’t.
I’d argue this function is needed, because the game doesn’t actually indicate if you are closer than 8 yrs after Lana’thel fears you, but will absolutely kill you if you are even slightly too close…
And there’s no in game indication of that.
The add-ons give info that would be in a well designed encounter.
YOUR EYES.
You dont need an addon lol. You know how far 10 yards is or 15 yards. You have played and did fights long enough.