This is pretty ridiculous not being able to tell who is in range on my raid-frames…
10 Likes
Yea, is there some explanation for this somewhere? I’m just seeing the bugs now. Completely screws with my weakauras.
I don’t know…something about breaking addon functionality for raiding. I can’t imagine how simply being able to know your range to your raid members can be exploited after 20 years.
1 Like
This change is causing a lot of headaches for gameplay in our raid this evening. Custom nameplates which have worked for years are now breaking or causing visibility issues since addons such as Plater will decrease transparency of nameplates which are out of range-- meaning without this functionality your screen either gets flooded with visibile nameplates, or worse, something is nearby you and the visibility is faded so you don’t realize it.
It’s a pretty direct breaking of the first tenet of Usability Heuristics: “Visibility of System Statuses”, or “The design should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time”.
If our healers cannot tell if their target is in range of a dispel, or if their limited-range heals (hero class: evokers) cannot reliably heal their teammates, it’s a pretty direct detriment to the player’s interface design here.
11 Likes
There are two bosses back to back (the tree lady and the snake in the pit) where the raid has to split/spread out pretty far. Half the time I was casting on myself because players were out of range. I’ve tried to switch to the default raid frames…but after xx years of using an addon, it’s hard to adjust.
The range indicator, with enough know how, could be used by very smart add-on developers to build a GPS style addon similar to what we had on archimonde. Given fyrakk’s core heroic + mythic mechanic involves spreading with huge lines like mythic sylvanas they probably wanted to just be safe and lock off the ability to make something to solve it.
Trash change breaking a basic function of the game and many UIs. This needs to be reverted, if for no other reason than the accessibility aspect, much less a function of the game that has been in place for nearly 20 years. All because Blizz cant be bothered to come up with a more interesting raid mechanic than “spread x yards”.
3 Likes
This is honestly the most toxic hotfix I can recall seeing.
I cannot remember how long range checking has been around, but I believe we were using it in at least BC (?).
Entire UIs are setup with range checking as a fundamental requirement for display & function.
When things like that WotLK addon that drew zones all over the floor were removed, that was a reversion to a previous normal.
This is randomly killing what has been the norm for the majority of 19 years, halfway through an afternoon, without even an attempt at justifying, pre-warning or explaining the change.
I cannot believe how incredibly stupid every single element of this hotfix is.
IMO bad decisions are occasionally made, and that’s fine, these things happen… but… are the development team actually serious?
I’m genuinely tempted to go heal a BG for the first time in a decade just so I can boggle further at the stupidity of this.
4 Likes
As a healer it is really rough not having range checks…ElvUI already fixed their frames in the beta build so I am happy that is working.
How did they manage that if addons are restricted from accessing range info now?
I don’t know but the beta build is working for party frames while in combat. The problem before was as soon as you hit combat, range stopped working. I didn’t look at the diff changes.
Ah, seems like the Grid2 author has found a workaround as well. Guess I’ll have to see next time I do some M+
This doesn’t seem like a good change given range is untuitive and so different based on your player character from tauren to mechagnomes, knowing the hitboxes and differences of each is so untuitive for this game.
They should have at least added a baseline function for this given the nature of hitboxes can vary especially when the players have access to toys.
1 Like
Can still do a direct check of “can I use X spell on Y person?” as a range-finder surrogate. That’s the current work-around.
I stand by my original condemnation of everything about this change though.
(And obviously no help if you’re any class who has spells with different ranges, like… basically every melee?.. many of the utility spells?.. etc)
Yeah, like I said it’s pretty ridiculous. It’s such a basic function to restrict, and unless they want to actually put the time into making the default frames as customizable as an addon, they can’t go around doing crap like this with no notice.
So it doesn’t work in Healbot either? That’ll be frustrating.
I dunno, it seems to work in combat, but is always returning true for my mage:
/run if IsSpellInRange("Ice Lance", "target") then print( "Yes") else print("No") end
EDIT: Ok, never mind, it does work… for whatever reason a boolean named function doesn’t return a boolean. At least this is a decent workaround. Thanks for that info
1 Like