-
Notifications
You must be signed in to change notification settings - Fork 75
raidboss: oc add phantom job and level tracker #796
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
Conversation
Co-authored-by: valarnin <valarnin@gmail.com>
|
Some other code I was considering adding were some utility functions similar to conditions.ts, but I may just pull from them as needed: |
|
Well, that merge didn't do what I wanted it to do and ended up touching this other branch too. |
fa9fc2e to
d2b7284
Compare
|
I think that this doesn't carry over into Forked Tower. The data appears to be reset on entry or between boss seals. |
Not sure if something changed recently, but I tried more FT and the code I wrote to mask for bard in FT appeared to be working without needing to change job. |
jacob-keller
left a comment
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.
Even with the caveat that job data can be missing due to reloads and what not, this data should still be useful.
- Neo Garula and Crescent Berserker Damage Up for Phantom Time Mage - Forked Tower: Blood's Guardian Golem's Toxic Minerals for Phantom Oracle - Forked Tower: Blood's Tower Idol Ancient Aero II for Phantom Bard Additional example helper functions in comments.
Thanks for the feedback. I have gone ahead and added the few triggers I've had and rest of the examples before I noticed the approval. |
Note: Phantom Dancer has a single-target freeze time ability, Tempting Tango. It could be pre-held, but given the random chance every cast to get the right spell, can only be rolled once every 30s, and the current use case prefers aoe version where this is single-target, I am opting not to include it for now.
xiashtra
left a comment
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.
Some comments related to the new phantom jobs added in 7.4, but overall LGTM.
Thanks for the comments. I have added them and adjusted the existing functions to match. |
This works, but is not always reliable without a refresh of the job buff. Certain situations such as reloading the overlay cause the data to be undefined. Reloading into the instance I think refreshes the buff as does resurrecting or manually changing the phantom job. This should be kept in mind when designing triggers based on the role. Triggers in Forked Tower are setup to always call out if unable to determine phantom job or phantom job level due to severity of consequences of missing a callout. Includes some Phantom Time Mage Triggers for CEs and commented, example functions similar to what we have for Conditions for regular roles/jobs. --------- Co-authored-by: valarnin <valarnin@gmail.com> ca8fdb3
This works, but is not always reliable without a refresh of the job buff. Certain situations such as reloading the overlay cause the data to be undefined. Reloading into the instance I think refreshes the buff as does resurrecting or manually changing the phantom job. This should be kept in mind when designing triggers based on the role. Triggers in Forked Tower are setup to always call out if unable to determine phantom job or phantom job level due to severity of consequences of missing a callout. Includes some Phantom Time Mage Triggers for CEs and commented, example functions similar to what we have for Conditions for regular roles/jobs. --------- Co-authored-by: valarnin <valarnin@gmail.com> ca8fdb3
With the status effects now available I was able to get the job ids and level.
EDIT: This works, but is not always reliable without a refresh of the job buff. Certain situations such as reloading the overlay cause the data to be undefined. Reloading into the instance I think refreshes the buff as does resurrecting or manually changing the phantom job. This should be kept in mind when designing triggers based on the role.