WowAce.com

Grid

75 - GridStatusAggro Acting Differently

What version of Grid are you using?
Version: 1.30000.2009011501

What version (and language) of WoW are you using?
EN-US

What were you doing when the problem occured?
Raiding

What happened?  What did you expect to happen instead?
While raiding, I am used to the 'Aggro Alert' corner lighting up when mobs turn to someone in my raid to cast a debuff. It's a small peeve, but one that allowed me to dispel debuffs efficiently and pre-Cleanse people so they had not noticed even having the debuff. This was working in previous versions of Grid correctly (and according to people who have not upgraded still works), but my new version is not acting in this way.

User When Change
Phanx Sep 13, 2009 at 10:10 UTC Changed status from New to Declined
Renew Jan 30, 2009 at 21:26 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 8 comments
  • Avatar of triarchelon triarchelon Mar 26, 2009 at 19:52 UTC - 0 likes

    I am having problems with the aggro alert as well. This is on the PTR. Frequently the aggro alert will remain even after nothing is targetting me. I am pasting the error message I got from Swatter below. Please note that after I got this message I disabled ora2, xperl, and bigbrother but the problem persisted unless I disabled the aggro alert on Grid. I still need to try using only Grid and no other addons to see if it is conflicting with anything, but the PTR went down.

    (One other addon problem, likely unrelated to Grid, but posting it just in case: when using xperl I am unable to right click my frame (or anyone's) and select options like focus, etc. It just doesn't show up at all and gives an error message about not being able to find a region named menu.)

    Date: 2009-03-26 14:19:25 ID: 1 Error occured in: Global Count: 1 Message: ..\AddOns\Grid\GridStatusAggro.lua line 159: attempt to compare number with nil Debug: ...rface\AddOns\oRA2\Libs\AceAddon-2.0\AceAddon-2.0.lua:25: ...rface\AddOns\oRA2\Libs\AceAddon-2.0\AceAddon-2.0.lua:23 ...rface\AddOns\oRA2\Libs\AceAddon-2.0\AceAddon-2.0.lua:1055: ManualEnable() ...rface\AddOns\oRA2\Libs\AceAddon-2.0\AceAddon-2.0.lua:983: ...rface\AddOns\oRA2\Libs\AceAddon-2.0\AceAddon-2.0.lua:976 [C]: ? ...AddOns\BigBrother\libs\AceEvent-2.0\AceEvent-2.0.lua:260: TriggerEvent() ...AddOns\BigBrother\libs\AceEvent-2.0\AceEvent-2.0.lua:910: ...AddOns\BigBrother\libs\AceEvent-2.0\AceEvent-2.0.lua:903

    AddOns: Swatter, v5.3.4105 (DingoIII) Acheron, v Altoholic, v3.0.008b Bartender4, v4.2.6 BigBrother, v BonusScanner, v4.4 clsaver, v3 DBMCore, v DebugLib, v5.1.DEV.130 FuBar, v FuBarExperienceFu, v1.1 $Revision: 65606 $ FuBarGarbageFu, v2.0.$Revision: 79607 $ FuBarMoneyFu, vv1.2 Grid, v1.30000.2009021101 GridManaBars, v0.89 GridSideIndicators, v0.5 GridStatusHots, v3.1 GridStatusMissingBuffs, vv3.00.03.04 release ItemPriceTooltip, v88 Omen, v3.0.6 oRA2, v2.0.$Revision: 628 $ Panda, v3.0.9.18 Prat30, v3.0.5 Prat30Libraries, v Quartz, v1.0 RatingBuster, v Recount, v SmoothDurability, v Stubby, v5.3.4105 (DingoIII) TipTac, v09.03.22 TipTacItemRef, v09.03.12 TipTacTalents, v09.03.19 XPerl, v3.0.2a XPerlArcaneBar, v XPerlParty, v XPerlPartyPet, v XPerlPlayer, v XPerlPlayerBuffs, v XPerlPlayerPet, v XPerlRaidAdmin, v XPerlRaidFrames, v XPerlRaidHelper, v XPerlRaidMonitor, v XPerlRaidPets, v XPerlTarget, v XPerlTargetTarget, v (ck=3fb)

  • Avatar of Renew Renew Feb 20, 2009 at 13:28 UTC - 0 likes

    Having it as an option to turn back on would be appreciated. It actually is a very major part of why I loved Grid.

  • Avatar of warbaby warbaby Feb 19, 2009 at 00:50 UTC - 0 likes

    I separated the former GridStatusAggro, and modified LibBanzai for the new grid GUID version. There's a GridStatusBanzai module here:

    http://filebeam.com/b621340f7773528c298d419a6c10faa8

    Choose "Banzai Alert" for the expected indicators like "Border" or "Corner"

    I'm trying to start a new project. You may want to test it before that.

  • Avatar of michaelselehov michaelselehov Feb 17, 2009 at 08:25 UTC - 0 likes

    CPU performance is a significant issue but sometimes one can sacrifice it for the sake of better raiding. Is it possible to make it an option?

  • Avatar of Laren Laren Feb 16, 2009 at 07:06 UTC - 0 likes

    Due to this change the aggro status became very unreliably for me. Even in 5 mans it takes way too long now until the aggro status actually shows someone have aggro, be it the tank or someone who passed the tank in threat. Can't it be made an option to actively scan the targets for those who have some CPU cycles to spare?

  • Avatar of Phanx Phanx Feb 06, 2009 at 19:49 UTC - 0 likes

    I wouldn't mind seeing an option to keep using Banzai. As a healer, I also found it very useful to see when the boss turns around and targets someone for an RST abiltity before whatever nasty thing it's about to do actually happens. I think it was worth the CPU usage. It's not worth using an old version of Grid to get, though.

  • Avatar of cerbul cerbul Feb 02, 2009 at 07:35 UTC - 0 likes

    Same problem for me, the agro "sign" wich helped alot to prevent damage is working on delay now. Was really much more useful as was before, as agro "sign" was up in the verry moment when the mob targets player.

  • Avatar of Pastamancer Pastamancer Feb 02, 2009 at 03:18 UTC - 0 likes

    GridStatusAggro changed from using Banzai to using the Blizzard threat events. It will show you aggro from mobs that nobody is targeting but it won't show you those temporary target switches for the random secondary target abilities. This is by design and is intended to recue CPU usage since banzai would scan the target of every party/raid member serveral times per second.

  • 8 comments

Facts

Last updated
Mar 30, 2012
Reported
Jan 30, 2009
Status
Declined - We decided not to take action on this ticket.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
1

Reported by

Possible assignees