[BUG][Retail] Target marker icon on wrong unit

[mbattersby]

Issue description:

At one point raiding today the target marker icon appeared on the wrong unit. Another time it persisted on a unit despite having been cleared.

Screenshot shows the second one (icon on target unit frame, definitely no icon on them)

I don't know if this is an ERF issue or a Blizzard issue but I thought I'd mention it. It's never happened before that I know of and I've been using this addon for at least 2 years.

How to reproduce:

I have no idea.

Technical info:

• Addon Version: 3.13.7
• Client: Retail
• Client Patch Version: 11.0.0.55824

Additional context:

I have no other theories at this point,

Screenshots:

Lua error log:

No errors displayed.

[mbattersby]

Here is another screenshot where you can see it on my raid unit frame but not on my player frame or on my model.

Edit: just realised the markers do not show on player frame only target.

[brittyazel]

It's quite possible it's a combination of an ERF issue and an 11.0 issue. Blizzard broke A LOT of stuff in this latest patch, and us addon authors are still sifting through the wreckage lol. Though this one is odd, and I don't see where on ERF's end the issue would be, but I'll take a look.

My guild isn't raiding at the moment until the expansion launches, so finding raid groups to test this stuff on is hard to come by lol.

[brittyazel]

Do you know if there was an Lua error that accompanied this issue? Would you mind turning on Lua errors in case one pops up the next time this issue happens?

[mbattersby]

Definitely no lua error, I always have them enabled.

On Fri, 26 July 2024, 19:56 Britt Yazel, PhD, @.***> wrote:

Do you know if there was an Lua error that accompanied this issue? Would you mind turning on Lua errors in case one pops up the next time this issue happens?

— Reply to this email directly, view it on GitHub https://github.com/brittyazel/EnhancedRaidFrames/issues/125#issuecomment-2252391120, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJ5N35KLKE6FOPT4XFKZ2DZOIMLRAVCNFSM6AAAAABLP3SPTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJSGM4TCMJSGA . You are receiving this because you authored the thread.Message ID: @.***>

[mbattersby]

If I had to guess, I would suspect its happening when the raid group membership is changing. Perhaps there's some event it's not catching to rescan and it's stuck in the wrong place.

On Fri, 26 July 2024, 20:49 Mike Battersby, @.***> wrote:

Definitely no lua error, I always have them enabled.

On Fri, 26 July 2024, 19:56 Britt Yazel, PhD, @.***> wrote:

Do you know if there was an Lua error that accompanied this issue? Would you mind turning on Lua errors in case one pops up the next time this issue happens?

— Reply to this email directly, view it on GitHub https://github.com/brittyazel/EnhancedRaidFrames/issues/125#issuecomment-2252391120, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJ5N35KLKE6FOPT4XFKZ2DZOIMLRAVCNFSM6AAAAABLP3SPTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJSGM4TCMJSGA . You are receiving this because you authored the thread.Message ID: @.***>

[brittyazel]

Yeah that was my thought as well. I added a full re-scan of the target markers upon a change to the group roster, so if the theory holds, this issue shouldn't happen any longer. Let's reopen if it does.