raidboss: OC North Horn Forked Tower: Magic Boss 2 Timeline - #1149
Open
Legends0 wants to merge 3 commits into
Open
raidboss: OC North Horn Forked Tower: Magic Boss 2 Timeline#1149Legends0 wants to merge 3 commits into
Legends0 wants to merge 3 commits into
Conversation
Legends0
marked this pull request as ready for review
September 7, 2026 14:23
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
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.
This is just the normal version, but has some of the branching support planned for extreme to prevent jumping into the normal timeline for extreme.
I created branches where location of the boss is going to be is known based on patterns.
This is also using AbilityExtra with a match on the x data, it seemed to work in my 6 logs I tested. I used
*to capture anything after the period in the match.28680.9 "--sync--" AbilityExtra { id: "C196", x: "600.*" } jump "oc-sword-dancer-throwing2-left"The tutorial was more complicated than the loop version. Seems they really threw a bunch of options in the tutorial but then for the loop stuck with a more limited pool of patterns.
I left some commented lines while we figure out what would be preferred for the
Turnspells. The commented lines are more of a hey this exists here too type of thing, but the visual output is already handled by the non-targettedTurnlines. The output right now is to show which row is going CW and which is going CCW. There is additionalTurnspells for those targetted, but differentiating that to the user didn't seem of value. TheTurnaboutspell is left in, but it doesn't have a whole lot of use.There's some stuff that could be done for Spin, but it's probably best left to a trigger.
I have not yet tested in game, but ran it through 6 of my logs and checked many fflogs pulls for some additional pattern matching.