Skip to content

Conversation

@ImUnicke
Copy link
Collaborator

@ImUnicke ImUnicke commented Dec 7, 2025

We don't need a field that calls another field which runs a helper function to recurse upwards in hierarchy to repeat the process.
If we consolidate the ShouldExcludeFromTooltip base field to perform the recursion and let overrides of ShouldExcludeFromTooltip determine whether that recursion should persist if their own implementation is not met, we get the exact same logic flow without the multiple extra chained steps.

I just don't have a way to fully test the custom ShouldExcludeFromTooltip functionality in MoP Classic concerning the different dungeon 'Protocol X' buffs. If someone on Classic with high-level characters could:

  • Pull this branch
  • Run Parser for Classic (05 - Mists of Pandaria).bat
  • Go into a dungeon with/without the respective Protocol stuff active and verify that the tooltip on Encounters while within the dungeon matches what is expected

Then we can merge this in. The OnInit part of the FunctionTemplate change works fine, it's just the actual execution of the ShouldExcludeFromTooltip functionality while within a dungeon for an NPC with/without the respective Buff being active that I can't test myself.

…elper function to perform the same logic

[Parser] Adjusted Function Template 'GenerateShouldExcludeFromTooltipForBuffs' to work as expected
@ImUnicke ImUnicke requested a review from DFortun81 December 7, 2025 21:21
@ImUnicke ImUnicke self-assigned this Dec 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants