- Fix a bug in
unscorable
not using lexicographical sort - #6 via @Kauhsa
- Fix a bug in
unscorable
not being strict enough - #4 via @Kauhsa
- Expose
FFA.Id
for consistency
- Bump tournament@3.1.0 for configurable logs
- Bump tournament to 3.0.0 for better serialization via
::state
and.restore
- Implement
_safe
for betterunscorable
check for safe history rewrites - Bump tournament to 2.2.0 for
_safe
- Bump tournament to 2.0.1
- Bump interlude to 1.1.0
- BREAKING upcoming now returns array of matches and never a partial id
- Partial ids for players in limbo can be gotten separately on ::limbo(playerid)
- Bump tournament to 2.0.0
- Remove
idString
but provide atoString
function for match ids natively - Remove hidden
::rep
from prototype - Bump to tournament 1.0.0
- Relaxed rules for number of players in a match (always allow 2 player matches now)
.invalid
returns better messages
- Documentation and coverage release
- Updated
tournament
to 0.21.0 so thatFFA
is anEventEmitter
- Limitless tournament no longer needs a single final
- TieBreaker supported
- Can use FFA as a different type of preliminary GroupStage with this
results[i].wins
now accounts for ties properly (bug)results[i].against
exists and counts sum(difference with winner)results[i].gpos
exists on final rounders for TieBreaker analysis
- Interface with tournament@0.20.0 for cleaner results implementation
- Interface with tournament@0.19.0 for multi stage support
sizes
andadvancers
now passed in as optional arguments- Use tournament@0.18.0 interface
- Using tournament@0.17.0 for better stats interface
- Rename
sum
tofor
for tournament consistency (maybe add against in future)
- Use group@0.1.0 for group algorithms
- Use tournament@0.16.0 interface
- refactor
score
to use Base implementation
- first release - factored out of tournament 0.14.0