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.
Adding set reporting features, starting with the core API operations and data structures required.
What remains to be implemented is the UI part, and more importantly, a way to actually track the current set's and player's IDs, because currently TSH does not have that (except the set ID, which is stuck in the closure of a lambda), which means it is impossible to actually perform the modifications (all my functions take IDs as parameters, but TSh doesn't reaaly have them anywhere) ; which is why this is still WIP.
here are the ideas i've had for that problem, the possible solutions, and the smaller problems they might introduce, if anyone wanna discuss them.
Auto-updating would most mikely depend on the SetManager : maybe it could simply keep the SetManager in its closure instead of having the set ID directly.