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.
I too came from AgUF, and I wish ShadowedUF had been around when I first started playing. I've only found one or two things that are harder to do with SUF, and many things that are easier or more flexible.
The whole time I was playing with AgUF and Grid, I was wishing that AgUF and Grid had more in common. With SUF, you can go so far as to make party frames look like raid frames, or raid frames look like party frames, there's very little that works for one and not the other. Which makes it very easy to configure indicators for healing that look the same either way, rather than looking for one thing in one mode, and something else in the other mode.
Actually, you can get the PB4 targets to work, you just need to specify the "Main Tanks" filter (not sure if that's what it's actually called, servers are down so I can't check).
Take a look at Visual Heal, I believe it does exactly what you're asking for. While I'm healing someone else, I get a popup health bar that shows how much incoming healing that target has, both from me and from other people, provided they have HealComm-3.0 installed.
Why it isn?t clickable ?? Any technical reason behind that ??
Yes. Basically, you need a secure frame to target anything, to cast a spell, etc. There are very few things that affect actual gameplay that can be done without a secure frame. Add to this the fact that secure frames can't have their setup changed while you're in combat, and you end up with the results you see. Frankly, the current solution is as elegant as possible, in my opinion.
Basically, back when WoW 2.0 came out (a month or so before the expansion), Blizzard updated the programming API to make it impossible for an addon to decide what to do with a click at the time of that click, because we were starting to see some fairly complex scripting addons that would do nearly optimal spell rotations with the player themselves just pounding a single key. Blizzard wanted to avoid that, so we got the secure frames API we've got now.
I find that since 2.4 and the post-2.4 update, it works intermittently. I'll have to pay more attention to it to see if there's some pattern to what it isn't announcing.
Why is every new version incompatible with its previous version?
It hasn't been every new version. To the best of my knowledge (and I update daily) there have been two versions that broke compatibility since 2.4 went live, and both of those versions were incompatible because of bug fixes. In other words, they couldn't fix the bug and remain compatible.
What specifically isn't working for you? Vital Watch mostly works for me, or at least it did last night. The only thing it doesn't seem to to is clear the alarm before the end of combat.
I'm running unembedded, with all addons updated Monday, if I remember correctly.
I ran both for a while, and it seemed to work well enough. When enough people had switched, I dropped KTM, and haven't had a problem, but I don't raid that often.
I relog(or just reload the UI), then there are no keybindings on the buttons and the keys don't work.
If I go check the keybindings they are still present (ie. F4 for bandage and F12 for Heal).
If I set F4 to Bandage again, all my keydindings are working again.
I'm seeing this too. I have ctrl-M bound to the mount button, and ctrl-Q to the quest items button. When I first log in, it's as if neither of these keys are bound. Hitting them does nothing, and the shortcut doesn't appear on the button.
I open the keybindings window (off of the options menu pulled up with the esc key), and the keybindings are still there. However, as soon as I close the window, even without changing anything, the shortcuts will appear on the buttons, and hitting the hotkeys will work, and will continue to do so until I log out or /reloadui.
If I had to guess, I'd say it looks like Autobar isn't doing the initial setup on the keybindings, but is only doing it when the user goes into the keybindings window and Autobar gets told that something has changed.
I'm not getting any errors for any addons. I'm running unembedded, with a boatload of addons (about 80-100 directories, I think, though a lot of those are multi-directory addons like cartographer and such).
It started earlier this week, the 23rd or 24th if I remember correctly.
Another vote for showing quests that we haven't done yet, and one other suggestion, though I'm not sure how many other people have this issue.
How about the ability to see what dailies I've done on my alts? I realize most people have a life, but for those of us that don't, keeping track of which of my four lvl 70s have done which dailies would be nice. Heck, even just a popup that tells how many dailies each of them have done would be an improvement from nothing.
As I understand it, if you're running embedded libraries (if you don't know what that means, you probably are), and a library gets updated but not the program that uses it, WAU doesn't know that it has to update the program, which is how you'd update the library.
This may have changed in the last few versions, but I haven't heard about it having changed.
I tried it, couldn't figure it out (didn't seem to do anything), and went on to use something else in the meantime without disabling it. I then tripped over how it works.
Basically, it replicates one of the buttons from the standard actionbar (button 5 on bar 8 I IIRC). It didn't deal well with being active when I wasn't playing a hunter, and had a few other issues.
I'm using a different pet feeding program that has fewer issues (still not perfect), though I can't remember the name of it.
So I start a raid with four Superior Wizard Oils, each one with 5 charges. By the end of the evening I still have four Superior Wizard Oils, but with 2 charges, 3 charges, 5 charges, 4 charges...
It would be nice if AutoBar used the lowest-charge item when presented with multiples.
It's been my experience that Autobar will always use the first one it finds until that one is consumed (though it looks every time you activate it), so I'm not sure how you would end up at 2/3/5/4 unless you were moving them around so that it would find different ones first.
On the other hand, I do agree that this would be an improvement, just mentioning that as a possible workaround.
"As for people requesting blocking party invites based on level: Blizzard provides no way to put party-invites on-hold. As such there is no way to perform a levelcheck before deciding wether or not to show a party-invite."
I understand that issue, and I think I might know a way around it, though I'm not sure how much overhead would be involved. How about periodically issuing a who on all lvl 1, and just maintaining a list of them? That way, you don't have to do a who at the time the party invite comes in. As I said, without knowing how much overhead is involved, I don't know how often doing the who would be practical, but on my server, at least, there's never even close to 50 lvl 1 characters on. It's not perfect (higher polling intervals means less overhead, but a larger chance of getting spam from someone that just logged in), and the next logical step in the escalation is for the spammers to start leveling to lvl 2 before starting the spam.
This is, of course, assuming that the API can get results back from this type of who query without opening the same window the UI does.
0
The whole time I was playing with AgUF and Grid, I was wishing that AgUF and Grid had more in common. With SUF, you can go so far as to make party frames look like raid frames, or raid frames look like party frames, there's very little that works for one and not the other. Which makes it very easy to configure indicators for healing that look the same either way, rather than looking for one thing in one mode, and something else in the other mode.
0
0
0
Yes. Basically, you need a secure frame to target anything, to cast a spell, etc. There are very few things that affect actual gameplay that can be done without a secure frame. Add to this the fact that secure frames can't have their setup changed while you're in combat, and you end up with the results you see. Frankly, the current solution is as elegant as possible, in my opinion.
Basically, back when WoW 2.0 came out (a month or so before the expansion), Blizzard updated the programming API to make it impossible for an addon to decide what to do with a click at the time of that click, because we were starting to see some fairly complex scripting addons that would do nearly optimal spell rotations with the player themselves just pounding a single key. Blizzard wanted to avoid that, so we got the secure frames API we've got now.
0
0
Healer mode works fine for me, as long as you designate tanks. Haven't tried AoE mode yet though.
0
It hasn't been every new version. To the best of my knowledge (and I update daily) there have been two versions that broke compatibility since 2.4 went live, and both of those versions were incompatible because of bug fixes. In other words, they couldn't fix the bug and remain compatible.
0
I'm running unembedded, with all addons updated Monday, if I remember correctly.
0
0
I'm seeing this too. I have ctrl-M bound to the mount button, and ctrl-Q to the quest items button. When I first log in, it's as if neither of these keys are bound. Hitting them does nothing, and the shortcut doesn't appear on the button.
I open the keybindings window (off of the options menu pulled up with the esc key), and the keybindings are still there. However, as soon as I close the window, even without changing anything, the shortcuts will appear on the buttons, and hitting the hotkeys will work, and will continue to do so until I log out or /reloadui.
If I had to guess, I'd say it looks like Autobar isn't doing the initial setup on the keybindings, but is only doing it when the user goes into the keybindings window and Autobar gets told that something has changed.
I'm not getting any errors for any addons. I'm running unembedded, with a boatload of addons (about 80-100 directories, I think, though a lot of those are multi-directory addons like cartographer and such).
It started earlier this week, the 23rd or 24th if I remember correctly.
0
How about the ability to see what dailies I've done on my alts? I realize most people have a life, but for those of us that don't, keeping track of which of my four lvl 70s have done which dailies would be nice. Heck, even just a popup that tells how many dailies each of them have done would be an improvement from nothing.
0
This may have changed in the last few versions, but I haven't heard about it having changed.
0
Basically, it replicates one of the buttons from the standard actionbar (button 5 on bar 8 I IIRC). It didn't deal well with being active when I wasn't playing a hunter, and had a few other issues.
I'm using a different pet feeding program that has fewer issues (still not perfect), though I can't remember the name of it.
0
It's been my experience that Autobar will always use the first one it finds until that one is consumed (though it looks every time you activate it), so I'm not sure how you would end up at 2/3/5/4 unless you were moving them around so that it would find different ones first.
On the other hand, I do agree that this would be an improvement, just mentioning that as a possible workaround.
0
I understand that issue, and I think I might know a way around it, though I'm not sure how much overhead would be involved. How about periodically issuing a who on all lvl 1, and just maintaining a list of them? That way, you don't have to do a who at the time the party invite comes in. As I said, without knowing how much overhead is involved, I don't know how often doing the who would be practical, but on my server, at least, there's never even close to 50 lvl 1 characters on. It's not perfect (higher polling intervals means less overhead, but a larger chance of getting spam from someone that just logged in), and the next logical step in the escalation is for the spammers to start leveling to lvl 2 before starting the spam.
This is, of course, assuming that the API can get results back from this type of who query without opening the same window the UI does.