Skip to content

Skipping splits doesn't really work #2372

@cwainczak

Description

@cwainczak

Suppose this scenario:

  • Split 1 | 2:00
  • Split 2 | SKIPPED
  • Split 3 | Time it took from Split 1 to Split 3

Generally, the segment of a split is the time it takes to get from that split from the previous split. However, in this case, Split 3's segment time is the time it took to get from Split 1 to Split 2 and from Split 2 to Split 3.

This makes splitting difficult for games with inconsistent routes; if you go out of order for your run, your split times are out of sync. If we decide to skip Split 2 because it is more applicable to go to Split 3 first (but then have to go do Split 2 after; suppose it is a mission or something), we now put an incorrect segment time down for Split 3 (as Split 3 should be the time it takes to get from Split 2 to Split 3). This makes the feature of "Best Segments" completely obselete in a non-linear speedrun.

I would love if we can get a fix for this; it can be some specific type of skip, where the segment time for Split 3 becomes counted the moment Split 2 is skipped. So, if we need to skip Split 2, we can decide when to start counting time by skipping whenever is applicable, instead of always having to aggregate the bonus time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    duplicateThis problem has already been reported.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions