On unordered splits, set a custom variable to show which split triggered it #145
Conversation
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
1 participant
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.
Resolves #144.
When not on Ordered splits, sets a custom variable
itemto the split name that triggered it.Intended to be used with the upcoming Custom Variable Columns feature (currently in the LiveSplit Development Version), in settings such as Randomizer or All Skills Shuffle, for splitting on major items in whatever order they come in, and filling in which items they were on the splits as they advance.
Currently a Draft PR because the Custom Variable Columns feature is not yet released on the current stable LiveSplit version 1.8.33. Once the next LiveSplit version comes out, I'll convert from a Draft to a Ready PR.