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

Build a "did you really mean to do that?" feature for adopting histories accidentally #756

Open
glacials opened this issue Apr 12, 2021 · 0 comments
Labels
feature Issues that are solved by adding new functionality for users

Comments

@glacials
Copy link
Owner

A lot of users start a new set of splits by downloading someone else's or by taking a set of similar splits they have (like for a similar category), then editing them to be what they want. They don't realize they are adopting all the histories from the set of splits they started with.

Then they upload them to Splits.io and because it's the first place they've seen their history clearly revealed to them, they think there's a bug with Splits.io that their histories are weird. It would be nice to have a feature that detects this at upload-time, and offers instructions for how to correct them (clearing split data in LiveSplit) or even offers to correct them automatically.

Examples:

This is the first time you've uploaded a run for this category, but your file has a lot of history inside it.
<show graph>
Does this look right?
The history for this run looks very similar to your <other category> run.
<show graph>
Did you <mean/want> to clear it first?
The history for this run looks very similar to <other player's> run.
<show graph>
Did you <mean/want> to clear it first?

Note that if we want to correct them automatically, we'll have to have a really good UX that instructs the user they must replace their local copy with the corrected copy, which I'm sure a lot of users just won't do anyway. For this reason it might be better to just tell them how to do it locally instead.

@glacials glacials added the feature Issues that are solved by adding new functionality for users label Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Issues that are solved by adding new functionality for users
Projects
None yet
Development

No branches or pull requests

1 participant