Range 10 WOW Classic
Closed this issue ยท 9 comments
Describe the bug
Do you have an error log of what happened?
To Reproduce
Screenshots
Did you try having DeadlyBossMods as the only enabled addon and everything else (especially something like ElvUI) disabled?
Which version of DeadlyBossMods are you using?
Was it working in a previous version? If yes, which was the last good one?
Additional context
Good afternoon!
Range 10 is currently not working for the WoW Classic version of the game. Could you check this?
it's not supported by any game version, blizzard blocks it, this cannot be changed. inside instances in combat it throws protected function fault. it technically works OUT of combat, but since out of combat isn't very useful and misleading I just have to globally disabled in instances. every time you try though it should clearly explain this in game though.
i think it'd confuse users if i enabled using it OUT of combat in instances only to auto hide/disable it soon as boss is pulled, and that's why I just disable it entirely in instances.
It worked when we were in a boss fight, but it doesn't work now. It's specifically during a fight when we enter the command /randge 10
that command should do nothing during a boss fight in classic. not since patch 1.14.0 when blizzard disabled range check apis. if you're thinking back 4-5 years to classic launch that's different.
Perhaps an update disabled this feature. I've never had any issues with the "/range 10" command. However, it's currently disabled for these particular bosses (Sapphiron and Kel'Thuzad.) in the classic version of the game.
I'm saying range command from DBM has been disabled since patch 1.14.0 and it cannot be enabled by dbm or any other addon in combat in instances. blizzard blocks it. there is no way you've had a working range finder in combat from ANY addon in last year and a half at least
it can only be used outdoors