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

• 

  • Reply
  • #10

  Shefki Dec 13, 2009 at 03:32 UTC - 0 likes

  Marking as fixed per the user comment that it's no longer occurring.

• 

  • Reply
  • #9

  Shadoweric Nov 06, 2009 at 20:20 UTC - 0 likes

  Shefki, you can close this ticket. Not sure how or why but it works fine now. I made sure it wasn't a fluke either.

• 

  • Reply
  • #8

  Shadoweric Aug 14, 2009 at 12:14 UTC - 0 likes

  Alright. I haven't raided much, but so far, it seems a lot better. Still some quirks though. Yesterday, someone dead (marked as ghost after releasing) had the aggro border on.

  Would being in different zones affect this (dead or not)?

  EDIT: More comments: still getting some weirdness. Like everyone lit up with the aggro warning instead of just the tanks. Also someone in another zone again showing as having aggro.

  Last edited Aug 15, 2009 by Shadoweric
• 

  • Reply
  • #7

  Shefki Aug 03, 2009 at 03:01 UTC - 0 likes

  Hmm I have 90040 but yours is still fairly recent. If the changes I made didn't help try upgrading your LibBanzai and then let me know what the situation is. Thanks.

• 

  • Reply
  • #6

  Shadoweric Aug 03, 2009 at 01:51 UTC - 0 likes

  That returns 90035.

  Sorry for the late reply, I was away on vacation. Which also means I haven't updated any addon for close to 2 weeks, so that return value should be considered in that context. And I will try your changes and let you know.

• 

  • Reply
  • #5

  Shefki Jul 27, 2009 at 02:41 UTC - 0 likes

  I tried quite a bit of stuff to try and reproduce this. I still cannot do it. Can you tell me what this produces: /run local _,version = LibStub("LibBanzai-2.0"); print(version)

  I'm also pushing through some changes to the Aggro module that might help. Let me know if that fixes it as well.

• 

  • Reply
  • #4

  Shadoweric Jul 16, 2009 at 21:06 UTC - 0 likes

  Not every time, but almost.

  Even if it's not on join, it's never accurate outside of combat. Someone is always marked as having aggro even though nothing's going on.

• 

  • Reply
  • #3

  fyrye Jul 16, 2009 at 06:10 UTC - 0 likes

  Does it happen everytime you're invited to a raid or more so randomly?

  My 2cp: I had a similar issue with PB3 where a group member would join while I was in combat and would need to /script ReloadUI() in order to get them to show in the party. Something similar maybe happening to where when you join the raid someone or something may have you targeted, indicating you have aggro to the code, and when you join, it becomes corrupted somehow. Haven't looked at the PB4 code at all yet, so am unsure as to if there is a call refresh upon joining/zoning/leaving combat (since new frames can't be created while in-combat)

• 

  • Reply
  • #2

  Shadoweric Jul 13, 2009 at 03:22 UTC - 0 likes

  No I can't really. EDIT: I figured out how to attach my saved vars. For some reason, the option doesn't show when creating this comment, but is available after.

  What I can tell you is to make sure there is already more than one person in the group before you get invited.

  Tonight I paid closer attention to it. This time, I was raid leader, so I didn't get the weird aggro when inviting, but it's been all over the place all night. I actually have a screenshot of everyone in front of a boss, waiting to pull, nobody in combat, and every single border turned red. For everyone. I can send it to you if you want, but I'm not sure it will tell you much more than what I just said.

  I have also seen it tonight stay highlighted after a trash pull. Many times.

  I tried turning off the threat bar for my raid frame. For one, I can't see it anyway (bug or is it just me doing it wrong?), for second, I wondered if it had something to do with it. It didn't seem to help though.

  Name	Size	MD5
  PitBull4.lua	179.7 KiB	88a079d28604...

• 

  • Reply
  • #1

  Shefki Jul 08, 2009 at 22:28 UTC - 0 likes

  Can you provide instructions for duplicating this from a newly made profile. There must be some sort of set of options that are interacting to cause this. I can't seem to replicate this.