This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
What version of Grid2 are you using?
r895-alpha and r894 alpha. This might have affected other version as of when 8.2 was released
What game client version (windows or mac) and language are you using ?
8.2 windows English
What steps will reproduce the problem?
When the "summon" status was introduced in version r850 at the end of last year, I assigned the "summon" status to an icon indicator. As of sometime between when 8.2 was released and now, the "summoned accepted" would get stuck shown on certain characters in a raid or party, and would not "go away" until a reloadUI would happen. I use Pitbull4 as well, and that shows the status and goes away properly.
Did you try having Grid2 as the only enabled addon and everything else disabled?
Yes
Was it working in a previous version? If yes, which was the last good one?
Uncertain.
Do you have an error log of what happened? If you don't see any errors, make sure that error reporting is enabled (`/console scriptErrors 1`) or install [BugSack](https://mods.curse.com/addons/wow/BugSack).
BugSack showed no errors.
This status is very simple, and this issue never happened to me. Could you provide any extra info that could help to know in which circumstances this issue can arise.
I know the status should be very simple, which frustrated me when i was opening up this ticket. I unfortunately can't give you any extra information because it's been very inconsistent in when it happens. I know it has happened at the summoning stone of Eternal Palace, Atal'Dazar, and King's Rest. I just used the summoning stone at Freehold, and that worked fine.
I think it's not bound to the "summon"-icon in general, because when I think about it, I've seen other icons "lock up" as well. I've seen the reincarnation-icon stay up even when being ressed, the combat-res icon indicating the person can res, and when he does, it stays up.
his is from what I remember, and like TS said, it disappears when you reload your interface until next time.
It's also not locked to a specific indicator, since I've seen it lock up with other indicators. I have an icon showing when people got the debuff "Treacherous Covenant". You get the debuff when you are at <20% hp, I think. This "locks up" sometimes, so people will still show as having this icon, when they shouldn't. No errors.
This seems to be an issue on blizzard's side. This happens in our raid about every-other week, and even non-grid / default users can see the bugged summoning icon on the raid frames. The issue doesn't go away until we give them a new summon.
I've seen the summon pending icon stay on other addons too, I don't think that one is related to Grid2 directly. I think it's something along the lines where the person gets a summon right as he accepted the previous one (some timing with a double summon?) or possibly if the person already got there themselves and the summon pending just stays behind. Might also be unrelated to that, but in those cases I've seen the pending stay until a reload, in that case other people can see it too.
I have seen icons that should be removed staying behind though as well, like for example debuffs that went away but still show on frames (like skmzarn said). One notable example I always seem to have this week, is Necrotic stacks on my frame, if I use dwarf racial and instantly get rid the debuff and all stacks, it still keeps showing my necrotic debuff with the previous amount of stacks (and an unlimited duration, no longer counting down), even when I can confirm that at that point nor do I have that amount of stacks, nor even have the debuff at that point. I think I've only seen this behaviour so far if the status is from a group of (de)buffs, haven't seen it yet where the (de)buff is added separately. In my case, I have a debuffs status with a couple affix debuffs (burst, grievous wound, necrotic wound) and assigned it to an icons indicator.
Debuffs code is independent from summon code, its not the same issue. One question, maybe the debuff glitch happen when you became out of combat ?
When combat ends, the game removes all combat debuffs (raidebuffs, some mythic debuffs, etc), but sometimes forget to send the event to notify this aura change. In combat there is not problem if some notification event is missing, because auras are changing a lot (new procs, hots, etc) so auras are rescanned several times per seconds.
Has someone noticed if the glitched debuff disappear when you apply/remove some new buff to your toon (for example a new HOT).
To post a comment, please login or register a new account.