-
-
Notifications
You must be signed in to change notification settings - Fork 318
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
New "Boss Mod" triggers working with both DBM & BigWigs #4537
Conversation
These triggers will use BigWigs if installed If not installed they will use DBM BossMod Timer will always ignore "cast" timers for bigwigs also.. renamed all "id" fields into "timerId" to avoid confusion re-inverted timerId & triggerId for DBM TimerMatches
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good from a DBM compatibility point of view. Tagging @MysticalOS for cross-review.
don't existing bw triggers have type. or at least a checkbox for cast/not cast? i feel we still have to match this or auraa that rely on it won't move over to unified. i know bw doesn't support advanced typing so it can't really go beyond cd and cast but that's probably fine for now. if it helps i can also just add a simp type arg that just returns true/false in our handler for caatbar or not but looking at this code you basically have that anyways by string finding case "cast" already. if i'm mistaken this on this i'll correct post when i get home. family keeps forgetting my "stop scheduling shit on tuesday's" rule :/ |
Plan changed from
to
|
I feel that if there isn't parity with feature of old trigger, no one will use new one at all. The type option is used extensively in many of weak aura examples i gave that targeted BW triggers, cause they need to know whether it's a CD or cast bar and they do trigger off cast bars sometimes. I can understand no migration since that's extra work, but to ensure people even use the new trigger in future tiers, it has to do everything old one does, or they'd just always use old one. Parity to old BW trigger should be at base a minimum. I can understand why DBMs more thorough advanced typing isn't supported (cause BW obviously doesn't support it). but outs does allow very easily mapping to existing BW cast/nocast trigger mapping. |
It's not a problem of "extra work", we won't do anything that break previously made auras in the middle of an expansion. |
no i get that, that's why no migration. existing WAs shouldn't be changed now I agree. But i'm saying if 10.2 hits ptr, and someone is creating NEW auras, they're not gonna use the new trigger if it lacks features old one has. |
We can ask Ora to check on wago, but i think 99.99% of auras using these triggers doesn't use type options |
if that's case, we can table the "type" stuff for now until it's further simplified and streamlined. I just pushed DeadlyBossMods/DBM-Unified@491d8a5 to address the over complexity of DBMs type system. Whether or not BW does parity to it, at very least, it still makes it easier to parse ours. This summerizes down to simply
|
It doesn't necessarily have to be in this PR, especially if announce triggers are rarely used, but DBM Announce and Boss Mod Announce triggers could be improved by adding support for spellID / key and count, reducing or removing the need to use locale-sensitive messages as trigger options. DBM_Announce has spellID as 4th and count as 7th arg, BigWigs_Message has key as 2nd arg and count would need to be parsed from message similarly to BigWigs_StartBar. Also, not a new issue but BigWigs Message trigger has BigWigs Addon option to test against the first arg of BigWigs_Message, however the first arg is a table value (https://github.com/search?q=repo%3ABigWigsMods%2FBigWigs%20BigWigs_Message&type=code) which will never match the string-valued option. It should probably be removed, or test against |
announce triggers are heavily used on echo of neltharian for bomb assignments, specifically for hearts/bombs. But the interesting note of them is they used string matching even when spellid and count was available in the BW announce object. I intentionally changed DBMs strings to match perfectly so they'd work in a unified. but I also didn't realize that weak auras never actually added support for spellid or count in the dbm announce object (and thus not in the boss mod one either). I'd argue it's definitely used enough to warrant addition before merge, or at least a new PR put in immediately after (we can do that if it helps). |
The above bug would cause |
@Mitalie thanks for your review! I pushed a commit that should fix the issues you found |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found a few more things.
You can go ahead and mark my first review's comments as resolved - apparently I can't do that myself, it's restricted to the PR submitter and people with write access to the repository.
Anytime I see DBM.Bars come up in a lua error, it's cause they have a weak aura from like 2018 they haven't updated in years or something, usually the old timeline lol. |
Shouldn't exist in any sane setup
I'd also still love to see Count arg added to "BossMod_Announce" object since it's a single line of parsing it from text (similar to what you already do for BW object) and using the count arg DBM provides (no need to even parse it) Then it's a knock out of the park in full usability next tier |
Afaik BigWigs_Message event doesn't have a count arg, neither of the 3 message/announce triggers have a count option |
right, that's why all the weak aura packs in aberus were using string scanning on echo of nelth. if you look at any of popular packs they were scanning for msg match = "bomb (1)" "bomb (2)" etc. since there was no means to go "if spellid = 12345 and count = 4" on announce. but yeah if original objects don't even have it then maybe worth another separate PR/issue then and not this one. :), to add feature to both legacy AND this object. |
i have not seen a single aura for neltharion using announce/message triggers, only bigwigs/dbm timers, but i didn't look at all of them |
https://wago.io/Y2peTP20U |
Fortunately it had very few installs. So I'd call it a niche case, but it still exposes the design flaw of that currently this actually is the ONLY way to cherry pick specific counts (in announce object at least, timers support count). |
We can certainly add that, though it doesn't need to be part of this PR. So let's merge this first. |
Description
This PR adds new triggers working with both DBM & BigWigs, which fixes #4502
Boss Mod Announce
Boss Mod Stage
Boss Mod Timer
All code for DBM & BW triggers were moved from
Prototypes.lua
&GenericTrigger.lua
toBossMods.lua
New public function
WeakAuras.GetBossStage
It has a few deprecated functions kept for compatibility with custom code
Boss Mod Timer doesn't carry a "type" option, as both bossmod don't have common type options, and will always ignore matches for a cast bar.
Type of change
How Has This Been Tested