[WIP] raidboss: r12s initial triggers and timeline for p1 #964
+3,815
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
22 tasks
TODO: Find safe spots.
This appears to be more accurate and not require delay by just predicting what the boss is going to turn to.
There's also cleaves to avoid at this time, which possibly will be called a second or two before this.
Replication 4 Locked Tether 2 is replacing the Lindwurm Meteor trigger, however there are a lot of things going on that need to be resolved in a quick order. The duration has been set to 8, which is when the cast ends. Unsure on the limit to the room split, it looks like it's halfway through the Downfall cast, so maybe 3.1 to 4.6s extra after the meteor hit? I imagine there is some MapEffect or control for this. Immediately on tether snap, you have a few seconds to dodge clone cleaves. Technically you could try to position prior to this with risk that your tether hasn't yet locked in. Simultaneously with the cleaves is the big Aoe and room split. Also, there is a chance the tether you got was messed up and you end up with a different tether than you picked up but right now it's still reminding which tether you locked with which. The tether itself will probably get a trigger to address the 4rth vision so that detail could be dropped, the right clone order still needs to be checked and matched to the tether the player chose.
xiashtra
reviewed
Jan 26, 2026
xiashtra
reviewed
Jan 26, 2026
xiashtra
reviewed
Jan 26, 2026
Co-authored-by: xiashtra <91220277+xiashtra@users.noreply.github.com>
Co-authored-by: xiashtra <91220277+xiashtra@users.noreply.github.com>
Co-authored-by: xiashtra <91220277+xiashtra@users.noreply.github.com>
It's back and with the same timing from e8s.
Collaborator
Author
|
I've added a trigger for an uptime knockback call for Raptor Knuckles. This requires same reaction time as the e8s one, but was easily doable even just eyeing the timeline before I added this trigger. EDIT: |
compared to some more logs
this actually is the same issue report in p8s which should be fixed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These I have been working on. It is very much a work in progress, although I think most of these work. Some of the calls still need to be merged and some probably altered. The Cursed Coil orders could use some more tuning as there are some more situations that could use a trigger for, I'll write-up a rough idea of its timeline for it later.
Currently Cursed Coil and the Act 3 are very much following the common PF strategy at the time (Toxic Friends). I've heard there is an alternate strategy for Cursed Coil but not seen it, and I imagine there must be some alternate strat for Act 3, but the simplest to do for now was just to call out the layout TF is using. I may add a config to the Act 3 later to just default to replacing the directions with cards/intercard calls instead of all 8 positions.
Timeline is based on network log. I will soon be starting on P2 and P1 will start receiving minor adjustments from my end.