Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
The general purpose of a range check is to show who you can heal; if you're a sheep, you can't cast any heals, so it's reasonably accurate to show everyone as out of range of your heals.
I thought the general purpose of a range check is to show who's in range... :p
I've tried the alpha and works fine except one thing: when I'm crowd controlled (fear, sheep etc), everybody around shows out of range. This is very frustrating since I would normally use the time I cannot control my character to plan what I will do first when I'm back to normal again. Which, being as I play a healer, means most likely healing someone around, and not being able to tell at a glance who's in range is severely limiting the judgment of the situation.
Apologies if this is simply due to the range module overhaul, but I fear it's due to how the Blizzard API works, so I guess I just wanna highlight it early if that's the case and you have not noticed yet.
Seeing as the new Grid release exhibits the same behaviour as the alpha I highlighted before, I suppose it's intended?
I've tried the alpha and works fine except one thing: when I'm crowd controlled (fear, sheep etc), everybody around shows out of range. This is very frustrating since I would normally use the time I cannot control my character to plan what I will do first when I'm back to normal again. Which, being as I play a healer, means most likely healing someone around, and not being able to tell at a glance who's in range is severely limiting the judgment of the situation.
Apologies if this is simply due to the range module overhaul, but I fear it's due to how the Blizzard API works, so I guess I just wanna highlight it early if that's the case and you have not noticed yet.
The arrows for Sindragosa encounter look like a great idea, however my guild uses different positions for Frost Beacons (I'm assuming the xpos/ypos are consistent with the drawing in the Lua file). So my question is: how can I calculate custom coordinates to replace the defaults? I see the xpos/ypos being fractional less than 1 numbers, and I'm clueless how the coordinates on the ingame map relate to those.
Any help would be appreciated, thanks in advance!
Edit: after poking around in DXE files, I think I found how to do that. Coordinates shown on the ingame map are given by xpos * MapDims.IcecrownCitadel[4].w and ypos * MapDims.IcecrownCitadel[4].h, is that a correct assumption?
You should ask the author of RaidCooldowns to allow for custom spells (if those aren't allowed yet), and that's your problem sorted. Whether the addon has "cooldown" or "spell timer" in the name, it's still the same thing if all you want is spawn a bar when someone in raid uses a skill you want to track. DBM-SpellTimers itself was designed for tracking cooldowns, not buffs, but works for both.
Otherwise it's pretty easy to port DBM-SpellTimers to DXE, just replace the GUI integration and use DXE.Alerts:Dropdown() to fire off bars. Same goes for Big Wigs CommonAuras.
In my opinion this type of functionality has nothing to do with a boss mod addon, and just because DBM is bloatware doesn't mean that other boss mods should include all possible and vaguely related functions that really should be in a separate addon...
The only mods whose settings I did not redo from scratch are ag_UnitFrames and Bartender 4.
I know many people who had issues related to agUF, that disappeared when they replaced it with another unit frame addon. It was a great addon, I've used it myself since alpha until recently, but as far as I can tell the author doesn't play WoW anymore and it's been on life support for at least few months. That was the reason I replaced it with sUF, which I'd recommend if you look for something familiar having used agUF.
It might be totally unrelated issue, but you can give it a shot and see how it works out.
1) Changing any option results in the configuration window's size and position being reset. I'm guessing this is an AceConfig problem, not a DXE-specific problem, but it is annoying. Moving the window so that some portion of it is off-screen prevents it from happening.
This dooesn't happen for me, I tried changing a few options in various tabs and config window stayed where it was.
Can't comment on the other points since I only changed a few of the defaults and didn't experience any issues. I do agree though that the colours etc feel a little random from the outside, that's the only customization I've done on my side.
I've been raiding with DXE for the last 2 weeks, and I'm very pleased with it, especially the fact that you can customize every alert in so many ways. Thanks for your hard work!
One thing I noticed tonight doing Vezax is that the number of the next Surge is not shown. It's handy to have it if you are assigned to use cooldowns on the tank during specific Surges, but to be fair it's not something I'd consider an absolute must, can do with counting in my head, let alone it's old content. Just if sometimes you are bored, this is a nice-to-have bonus.
I could add a simple toggle that hides all raid warnings. Is that what you want?
Ideally this should only block messages (raid warnings, but whispers too) from other boss mods, I think BigWigs blocks everything that has "***" in the string (BigWigs_Plugins/BossBlock.lua).
I don't know if you consider this to fit in your vision about DXE, just saying that blocking all raid warnings will likely not be what people expect from this feature. :)
Another problem I noticed with r53: all the windows/trackers are reset once I reload UI. I deleted SavedVars (not a problem since I only have a couple of trackers defined for focus), then I defined a new tracker, reload UI, tracker gone. Window/tracker styles are still there, is just the actual trackers/windows that don't seem to be persistent.
0
I thought the general purpose of a range check is to show who's in range... :p
Anyway not gonna argue, I'll just use the plugin.
0
Seeing as the new Grid release exhibits the same behaviour as the alpha I highlighted before, I suppose it's intended?
0
Apologies if this is simply due to the range module overhaul, but I fear it's due to how the Blizzard API works, so I guess I just wanna highlight it early if that's the case and you have not noticed yet.
0
Nope, that was it, thanks for the help!
@Phanx: I may have chosen my words poorly, I was looking for what Greltok suggested.
0
0
(1) is already in, (2) would be very nice indeed.
0
Any help would be appreciated, thanks in advance!
Edit: after poking around in DXE files, I think I found how to do that. Coordinates shown on the ingame map are given by xpos * MapDims.IcecrownCitadel[4].w and ypos * MapDims.IcecrownCitadel[4].h, is that a correct assumption?
0
Otherwise it's pretty easy to port DBM-SpellTimers to DXE, just replace the GUI integration and use DXE.Alerts:Dropdown() to fire off bars. Same goes for Big Wigs CommonAuras.
In my opinion this type of functionality has nothing to do with a boss mod addon, and just because DBM is bloatware doesn't mean that other boss mods should include all possible and vaguely related functions that really should be in a separate addon...
0
I know many people who had issues related to agUF, that disappeared when they replaced it with another unit frame addon. It was a great addon, I've used it myself since alpha until recently, but as far as I can tell the author doesn't play WoW anymore and it's been on life support for at least few months. That was the reason I replaced it with sUF, which I'd recommend if you look for something familiar having used agUF.
It might be totally unrelated issue, but you can give it a shot and see how it works out.
0
0
This dooesn't happen for me, I tried changing a few options in various tabs and config window stayed where it was.
Can't comment on the other points since I only changed a few of the defaults and didn't experience any issues. I do agree though that the colours etc feel a little random from the outside, that's the only customization I've done on my side.
0
One thing I noticed tonight doing Vezax is that the number of the next Surge is not shown. It's handy to have it if you are assigned to use cooldowns on the tank during specific Surges, but to be fair it's not something I'd consider an absolute must, can do with counting in my head, let alone it's old content. Just if sometimes you are bored, this is a nice-to-have bonus.
0
Ideally this should only block messages (raid warnings, but whispers too) from other boss mods, I think BigWigs blocks everything that has "***" in the string (BigWigs_Plugins/BossBlock.lua).
I don't know if you consider this to fit in your vision about DXE, just saying that blocking all raid warnings will likely not be what people expect from this feature. :)
0
That solved it, the settings are persistent now, thanks!
0