You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 14, 2018. It is now read-only.
It seems that this issue is known (The hint when starting the cut) and I think it would be preferable to be able to review the results of a tournament after it was completed.
The text was updated successfully, but these errors were encountered:
That is difficult simply because of the way cut is implemented. That would require a full rewrite of the cut system.
Currently we are using the tournament npm package which has that implemented sort of by default but it makes everything extremely difficult to serialise. I will eventually get along to writing this properly.
Sadly, I'm not familiar enough with JavaScript as of yet. I'll see if I can look into that some time in the future.
(On an unrelated note: I think you're doing a really good job here!)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It seems that this issue is known (The hint when starting the cut) and I think it would be preferable to be able to review the results of a tournament after it was completed.
The text was updated successfully, but these errors were encountered: