- Registered User
Member for 15 years and 3 months
Last active Fri, Oct, 4 2013 21:30:09
- 0 Followers
- 84 Total Posts
- 0 Thanks
Mar 10, 2008_ForgeUser259858 posted a message on [Request]Addon that 'pings' when a tracked ressource appears on the minimapdo the blips on the minimap have frames? is there no way to enumerate through them to see if they are visible?Posted in: Addon Ideas
Mar 6, 2008_ForgeUser259858 posted a message on Wanted to share something i came up with last nightPosted in: Lua Code DiscussionQuote from break19 »
Think about it this way. which is easier to upgrade, memory or cpu? so therefore which has higher priority? lower CPU usage should -always- trump memory.
except in this case, where results are cached, the speed penalty is only paid once -- so I would go with the reduced memory footprint.
Mar 1, 2008Posted in: Grid & Grid2Quote from Peragor »...if you wanted features that sorted people by their role, then we would need a more static and foolproof method of looking at peoples talent specs...
But even looking at talents specs isn't always enough -- although it's a great first guess. Just like looking at aura/stances/form/etc. isn't always accurate. I know some fights we have prot pallies or druid tanks heal. As a holy paladin, I've even been asked to heal a fight with righteous fury up to try and draw mobs to me away from squishes.
Unfortunately, I think this problem is always going to involve some manual sorting.
Feb 29, 2008After a quick look it appears LibBabble-Spell-3.0 is the only babble lib AutoBar uses. You'll need to download that. I'd suggest using WowAceUpdater to make sure you have up-to-date and complete packages for each of your Ace addons.Posted in: AddOn HELP!
Feb 29, 2008Posted in: LibrariesQuote from Ellipsis »
Not true in 2.4 - the new combat log events will tell you the spell name that failed along with the reason for its failure (line of sight, out of mana, out of range, ...). Though I agree that the code to communicate these events probably doesn't belong in LHC.
My thought was that much of the code for doing this was already in LHC -- ie. LHC is already sending a message for every heal that fails (for what ever reason - canceled, interrupted, error, etc.) and I thought it would be a straight forward and useful extension to add a parameter to the message indicating why the heal was stopped if it was known.
Feb 28, 2008Would it be possible to add a report to show "what" a person dispelled?Posted in: General AddOns
I was thinking in the top half of the report, it would list each debuff that was dispelled by the selected person and how may times it was dispelled. Clicking on a debuff in the top half would cause the bottom half to refresh listing the people that had been dispelled of that debuff and how many times.
Dispelled What Report for PaladinA
Holy Fire 9
*Blind 5 <- selected
If this already exists as a feature in Recount, can you tell me how to access it?
Feb 28, 2008Posted in: Grid & Grid2Quote from ackemaan »...Yesterday it hit me that if you could ad ppl lost out of sight (around corners etc) and make it like out of range it would be so cool. Dont know if its possible but it would be a great!...
The only time (AFAIK) that you get any information about LoS errors is on a failed spell cast or ranged melee attempt. The module I'm working parses the error indicator that pops up and adds a timed duration alert to Grid for it (after the error occurs), which can be tied to an indicator.
I mainly use it in BGs when I am spamming heals in an area. The indicator, which I have set to stay visible for 8secs, reminds me this person was out of LoS (probably in a tower or bunker) even though they were in range, and I either need to move to find them, or ignore them in heals for a while. I sometimes miss the built in LoS error text message that pops up because I'm focused on my Grid frame, or I get confused about which of the 40 players I had LoS errors on 3 casts ago, and having an indicator pop up in Grid helps. I find it useful.
I've been trying to expand its usefulness by adding an alert on the target's Grid frame if the target has one. I think a player might like to know that a healer tried to heal him, but he was out of LoS -- especially if he's a tank. And since it would be configurable he could turn the indicator on or off as he saw fit.
Feb 28, 2008Posted in: Grid & Grid2Quote from Phanx »
Well, if you can't remove a debuff, why does it matter if you notice it immediately or not?
I used "debuff" as an example of an alert that a "non-healer" might be interested in. Raid leaders need to be able to get an overall picture of the health of the raid... who's dead, offline, stunned, or otherwise incapacitated by some random debuff or event. Who's got an explosive debuff that's gonna wipe the raid if they don't move, etc. They need to be able to "call audibles" to adjust for different conditions, etc. Grid helps them identify those conditions. And this is just one example of a non-healer using Grid.
Again, the flexibility that Grid brings with its alert system is one of its biggest strengths. Being able to configure the priorities of things you are interested in, how the alerts are displays (where, size, color, etc.) all helps. Having more options for alerting a user can only help - whether its to add "flashing" or "shapes" - or something else. Like Jerry's GridAlert addon which adds text and sound notification for changes in status.
The point is, what works best for you, may not be the best for everyone, and having options is a good thing in my opinion.
Feb 27, 2008Posted in: Grid & Grid2Quote from Phanx »... A redundant indicator on my Grid frames is just visual clutter distracting my attention from things that are actually important.
That's one of the great things about Grid -- it's configurability. Any indicators not important to you, can be disabled. What you think is unimportant, might be viewed as critical to someone else.
Quote from Phanx »... than it is to expect that every tank and healer is using Grid and that they'll notice an LoS indicator in time for it to make a difference.
Which is pretty much what I said below -- err above -- err previously. Tank's probably are not watching their grid frame much less there chat frame.
Feb 26, 2008Posted in: Grid & Grid2Quote from Phanx »
I would strongly object to any and all annoying flash effects in Grid.
I don't think he was saying make it the standard for all Grid users. I think he was saying add "flashing" as an indicator option... like color, size, etc.
I think Grid really shines for healers, but I know non-healers (like raid leaders, etc.) install it because it gives them so much information about the raid at a glance. These non-healers may not be focused so intently on their Grid frame as the healers, and may sometimes miss important debuff information, etc.
I have just the opposite problem. As a healer, I'm sometimes so focused on my Grid frame, that I miss things going on outside of it -- like error notifications for LoS, etc.
Feb 26, 2008Posted in: Grid & Grid2Quote from Phanx »
Personally I don't think it would be useful to communicate "heals failed due to LoS" to all other Grid users in general. As a Grid healer, I prefer to only see things that are relevant to me... knowing that "someone wasn't able to heal this target because they are out of his/her LoS" isn't really relevant to me.
It wouldn't display on everyone's grid... just yours and the target of your heals. Let's say PriestX is assigned to heal TankY. PriestX casts a heal on TankY, and it fails due to LoS.
On PriestX's Grid frame, an indicator would pop up (for a configurable duration) on TankY's square. This indicator would serve as an extra notification (and reminder) that TankY was out of LoS for our last cast.
On TankY's Grid frame, an indicator would pop up (again for a configurable duration) on PriestX's square. This indicator would serve as a very important notification to him that a healer (in this case PriestX) tried to heal him but he was out of LoS.
If you have ever done the Al'ar fight in TK then you know that tank positioning on the edge of the platforms in *critical* and there's not much the healers can do if the tank is out of LoS.
The whisper idea is a good one... having PriestX whisper TankY "I failed to heal you because you were out of Los". I would just be afraid he would not notice the whisper... but I guess as a tank he's probably not paying much attention to his Grid frame either.
Feb 26, 2008Would it be possible to add the reason the heal was ended to the HealComm_DirectHealStop() event? Like for LoS error or Range error or OOM error?Posted in: Libraries
I've been working on an addon which has a post-LoS error indicator:
If it's too late to modify HealComm_DirectHealStop(), could a new event be added? HealComm_DirectHealFailed()?
What I would like to do would be to have an alert pop up on the target of the heal spell if the spell fails due to LoS, or range, or OOM... giving the target a heads-up that a healer tried to heal them but failed, so that they can move, take a healthstone, re-assign healers, etc.
Feb 25, 2008would it be useful to have an addon message sent notifying the person that they are out of LoS of the person trying to cast the spell? i could then add code displaying the indicator on the target's grid as well.Posted in: Grid & Grid2
for instance, a healer tries to cast a heal on a hunter, but the hunter turns out to be OoLoS. on the failed cast, the healer will get an indicator on the hunter's frame that he is out LoS.
an addon message is sent, announcing that [hunter is OoLoS of priest].
the hunter, over on his UI and grid frame, when the addon message is received, will get an indicator on the priest's frame that the priest is out of LoS...
would something like this be useful? do tanks ever consider moving to be in LoS of their healers?
- To post a comment, please login or register a new account.