Skip to content
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

Request: Trigger change: Sphene Ex #507

Open
Flavescent opened this issue Nov 19, 2024 · 2 comments
Open

Request: Trigger change: Sphene Ex #507

Flavescent opened this issue Nov 19, 2024 · 2 comments
Labels
enhancement New feature or change to existing functionality fix-me Bug report validated or feature request planned

Comments

@Flavescent
Copy link

Feature(s) Requested

In the ice phase of the Sphene Ex fight, the player is only told to move either west or east across the bridges:

    west: {
      en: 'Spread West, stretch tethers',
    },
    east: {
      en: 'Spread East, stretch tethers',
    },

But for commonly played strats, more info is required that I find difficult to take in at a glance visually:

  • It matters whether the player is tethered to the bottom icicles (these players move first across the bridge because the bottom icicles appear first) or to the side icicles (these players move second across the bridge)
  • For the "fixed bridges" strat, it also matters whether the player is tethered to an outer bottom icicle (these players use the north bridge) or an inner bottom icicle (these players use the south bridge).

I'd appreciate it if this information could also be imparted by Cactbot. For example:

  • Side icicle: "Spread East/West, go second, stretch tethers"
  • Outer bottom icicle: [Toggleable: "Upper bridge"] "Spread East/West, go first, stretch tethers"
  • Inner bottom icicle: [Toggleable: "Lower bridge"] "Spread East/West, go first, stretch tethers"
@Flavescent Flavescent added enhancement New feature or change to existing functionality needs-review Awaiting review labels Nov 19, 2024
@wexxlee
Copy link
Collaborator

wexxlee commented Nov 19, 2024

I think this is doable, but the "bridge" portion of the callouts probably should be a config option.

I think the "fixed" strat I've seen in PF (someone jump in if I'm wrong plz) is that inside S tethers use the lower bridges, outside S tethers use the upper bridges, and the east/west tethers use the bridge that's horizontally aligned to their tether (e.g. the north-most side tethers use the upper bridges). Assuming that's right, the config options could be 'Don't call bridge' or 'Fixed (inside lower, outside upper'. I think we could probably (?) default to Fixed based on PF prevalence, but I don't feel strongly if people think the 'don't call' should be default.

Are there other strats that should be included? (I've seen the line-up prio strat, but I'm not wild about trying to grab live player position data to prioritize - that seems like asking for trouble).

@wexxlee wexxlee added fix-me Bug report validated or feature request planned and removed needs-review Awaiting review labels Nov 19, 2024
@wexxlee wexxlee changed the title Request: Timeline change: Sphene Ex Request: Trigger change: Sphene Ex Nov 19, 2024
@valarnin
Copy link
Collaborator

Yeah, I looked at this as a few potential changes:

  1. Add "first" or "second" (can count tethers, if tether count is <= 4, you're first?)
  2. Maybe, add which icecicle you're tethered to:
    a. SW Outside
    b. SW Inside
    c. ...
    d. W N
    d. W S
  3. Add a strat option which would override the callout to be "NW Bridge, First, Stretch Tether" or something like that

So assuming you're tethered to SW inside icecicle:
With no strat selected, you would get something like Spread West, Stretch Tether, First, SW Inside icecicle.
With the strat selected, you would get NE Bridge, First, Stretch Tether.

(feel free to ignore if this makes no sense, I'm a bit mentally fried tonight)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or change to existing functionality fix-me Bug report validated or feature request planned
Projects
None yet
Development

No branches or pull requests

3 participants