Skip to content

raidboss: r12s p1 blob safe spots#1017

Open
Legends0 wants to merge 12 commits intomainfrom
r12s-p1-blob-safe-spots
Open

raidboss: r12s p1 blob safe spots#1017
Legends0 wants to merge 12 commits intomainfrom
r12s-p1-blob-safe-spots

Conversation

@Legends0
Copy link
Collaborator

My only comment about it is the curtain call contains two outputs. I had a hard time thinking about a configurator to prefer certain locations, so left it at calling both.

Melee probably would prefer a call that just has northwest or northeast while range would prefer whichever is the shortest distance from them, typically I find this is just the side they are on rather than cutting across east/west.

@cactbotbot
Copy link
Collaborator

cactbotbot commented Feb 23, 2026

@Legends0 Thanks for your contribution! 🌵🚀

@github-actions github-actions bot added raidboss /ui/raidboss module needs-review Awaiting review labels Feb 23, 2026
@Legends0 Legends0 changed the title raidboss: r12s p1 blob safe spots in act 1, curtain call, and slaughtershed raidboss: r12s p1 blob safe spots Feb 23, 2026
Using OverlayPlugin to get player position at time of tether break to tell relative safe spot.
@Legends0
Copy link
Collaborator Author

Legends0 commented Feb 23, 2026

Tested a pull.. I think the curtain call one called wrong (using the config option ns) and the act 1 feels kind of late when it's on the stack call. The data for act 1 is available earlier, just need to find a window to sneak an infotext i suppose.

EDIT: New trigger there for earlier call is good.

It was calling opposites.
Sounded superfluous to have plus ${dir} for the stack
@Legends0
Copy link
Collaborator Author

The slaughtershed call now that it includes direction with the stack/spread I think needs to be merged in some way with the followup dodge. I do find that it calling a Left/Right or KB info at same time as calling a safe spot makes it easy to quickly misunderstand the direction to go at the moment.

@Legends0
Copy link
Collaborator Author

Legends0 commented Feb 25, 2026

In doing the merge of slaughtershed triggers there, I removed the individual triggers. If they need to be added back it will require a different approach I think.

Additionally, not sure if these should all be set at alert. It may make it harder to adjust to the uptime knockback strat if they are all alert... perhaps the uptime knockback strat should downgrade those to info or the raptor knuckles triggers should just be info.

was moved to be located around where it would fire
Probably better to help distinguish it from the KB direction calls and due long text.
Earliest this could be done is at same time as Slaughtershed StartsUsing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-review Awaiting review raidboss /ui/raidboss module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants