Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

core: Fix contextual ping on suffix units #659

Merged
merged 1 commit into from Sep 20, 2023
Merged

core: Fix contextual ping on suffix units #659

merged 1 commit into from Sep 20, 2023

Conversation

p3lim
Copy link
Member

@p3lim p3lim commented Sep 20, 2023

No description provided.

@p3lim p3lim self-assigned this Sep 20, 2023
@p3lim p3lim requested review from Rainrider and ls- September 20, 2023 17:14
@p3lim p3lim merged commit 8739982 into master Sep 20, 2023
1 check passed
@p3lim p3lim deleted the fix-ping branch September 20, 2023 19:53

By default this wraps `C_Ping.GetContextualPingTypeForUnit(UnitGUID(frame.unit))`.
--]]
object:SetAttribute('ping-receiver', true)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just wanted to let you know that this line is breaking frames when they're spawned in combat.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to make it easier for me to test this, how did you encounter this? E.g. when did you get frames spawned during combat?

Copy link

@Meivyn Meivyn Oct 30, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was on a world boss and it broke when players joined the raid. Due to the fact that SetAttribute can't be called in combat.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants