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

Fix Mage partybots not reapplying Arcane Brilliance. #2590

Open
wants to merge 1 commit into
base: development
Choose a base branch
from

Conversation

mserajnik
Copy link
Contributor

🍰 Pullrequest

This fixes Mage partybots not reapplying Arcane Brilliance unless it has expired on themselves.

As was pointed out, other party-wide buffs such as Prayer of Fortitude or Prayer of Spirit are cast again as soon as they drop off a single member and an argument could be made that that's not always desirable (because it's mana-inefficient).

However, I would argue that "always re-buffing" instead of "almost never re-buffing" is probably the better choice and with this PR, the behavior of Arcane Brilliance at least matches that of the other buffs. Ideally, this should be configurable in some way (e.g., have a toggle command to allow/disallow party-wide buffs so players can choose when they get used).

Proof

  • None

Issues

How2Test

  • Summon a Mage partybot that knows Arcane Brilliance
  • Wait for it to cast Arcane Brilliance, then remove the buff from yourself
  • Observe the Mage partybot casting Arcane Brilliance again (once he is finished drinking and has enough mana)

Todo / Checklist

  • None

@gajet5
Copy link
Contributor

gajet5 commented Apr 19, 2024

@mserajnik
Copy link
Contributor Author

@gajet5

Sorry, I missed your PR somehow; you should mark that it closes #2400.

@mserajnik mserajnik closed this Apr 19, 2024
@mserajnik mserajnik deleted the partybots-fix-arcane-brilliance-buff branch April 25, 2024 17:06
@mserajnik mserajnik restored the partybots-fix-arcane-brilliance-buff branch November 19, 2024 16:54
@mserajnik
Copy link
Contributor Author

I'm reopening this because @gajet5 closed his PR (#2510) and this is a tested fix for #2400.

@mserajnik mserajnik reopened this Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants