-
Americano for 40 to 64 players: perfect rotations from finite fields, and why 48 still resists
The free Americano builder now has perfect rotations for 40, 41, 45, 49, 53, 56, 61 and 64 players. A short proof explains why 48 and 60 need another method.
-
Americano with 10, 14 or 18 players: the best rotation when a perfect one can't exist
With 4k+2 players no rotation can partner every pair once. The free Americano builder now plays the provable best: one missed partner each, no repeats.
-
A bowling league's weekly sums: averages, handicaps and standings from typed score sheets
The free bowling league scheduler now turns typed score sheets into averages, handicaps, points, standings and position-round pairings, in the browser.
-
Fair teams from a sign-up list, and a page that says when they cannot be fairer
Paste players with a rating and get teams with even sizes, an even coed split and friend requests kept, plus a floor that shows when no split is fairer.
-
Free agents placed like a balanced draft: tag questions and a roster cap on a self-hosted league page
The league page's /join free agents now go through the balanced-teams search: shortest rosters first, women and goalies spread, strength evened.
-
Late sign-ups onto teams you already announced, without reshuffling everyone
The balanced team generator now places late sign-ups onto announced teams. Letting two players switch closes most of the gap a full redraft would.
-
A rotating-partner night where everyone partners everyone once: whist designs in the Americano builder
The free Americano builder now uses whist designs: every pair partners exactly once and faces each other exactly twice. Where it helps, and where it doesn't.
-
Pool play into a bracket without the rematch: crossover seeds, searched exactly
Pool play now seeds the knockout crossover-style. Seeding by record alone could put poolmates together in round one in 29 to 86% of random draws.
-
The bowling schedule was looking up the same numbers 144 times a week
A small closure inside the bowling lane polish took 57% of the time. Inlined, a 24-team season builds in 1.5 s instead of 4.4 s, with the same lanes.
-
Two agents, one hotspot, and a walk that cannot finish
Two sessions sped up the same bowling lane polish at the same time. The part only one of them touched, a random walk on unbalanceable seasons, ran 45% faster.
-
A bowling schedule that takes seven seconds, without freezing the tab
The bowling league page's slowest season used to lock the browser for 7.3 s. Moving the lane search into a Web Worker cut the longest stall to 53 ms.
-
A play-off bracket that fills itself in, and the one rule that matches a line to its game
The league schedule generator's bracket stopped at seeding. Now typed play-off results fill it in, double-elimination resets included.
-
A sub list for the whole league, matched to the teams that are short
Players free on a match night put their name down once; the organiser sees them beside every short team and places one with a click.
-
When five bowling teams avoid the same lane pair, change who plays whom in week one
The free bowling schedule maker refused some seasons with five or more lane limits that a different round-robin order can play. It now finds that order.
-
A bowling schedule the SAT solver called impossible, solved by moving two teams in the draw
A lane-limit season a SAT solver proved impossible had an answer once the two limited teams took other places in the round robin. What it means for organisers.
-
Five bowling teams that can't use the wall pair: why the first legal schedule isn't the fairest
With five or more bowling teams kept off a lane pair, comparing several legal dealings instead of taking the first lifts fully even seasons from 37 to 42 of 48.
-
Bowling lane limits, solved once per shape: why a team's name doesn't matter to the lane rotation
Bowling lane limits on hard seasons, solved by SAT once per limit shape and fitted to any league by renaming teams: 60 of 112 seasons in target became 106.
-
Bowling lane rotation: the week order does not matter, and a timeout becomes a proof
Solving a bowling league's lane rotation as counts per round, not week by week, turns solver timeouts into instant proofs and two new even seasons.
-
Bowling lane rotation: a random walk and a SAT solver close the last six uneven seasons
The free bowling league schedule maker now rotates lane pairs as evenly as possible in all 36 measured seasons, up from 30. How a walk and a SAT solver did it.
-
Bowling lanes: an even split, and never the same pair two weeks running
The free bowling schedule now cuts back-to-back weeks on one lane pair from 392 to 148 over 36 seasons, without making any team's lane split less even.
-
Bowling league schedules: keeping a team off a lane pair without breaking the rotation
The free bowling schedule maker now keeps a team off a lane pair every week as a hard rule. Measured on 142 seasons against the usual hand fix.
-
44 bowling league seasons where no lane rotation can be even, proved by a SAT solver
Some bowling seasons can't give every team its even share of lane pairs. A SAT solver proved 44 of them; a season as long as the lane pairs is the usual one.
-
League notices where players already look: a dated message on the schedule page, emailed if you want
The self-hosted league page now carries organiser notices: for everyone or one team, with an end date, optionally emailed to each team's contacts.
-
Who hasn't answered yet: league rosters, an answers CSV and one reminder email to a short team
The self-hosted league page now knows each team's roster, shows who has not answered, exports every answer as CSV and emails a team that is short two days out.
-
Promotion and relegation for a rec league, without retyping every division
The multi-division schedule page now moves the top teams up and the bottom teams down into next season, and flags the places a table cannot decide.
-
Free agents in a rec league: players with no team, placed on the short rosters
A self-hosted league page now takes free-agent sign-ups and suggests a team for each: smallest roster first, experience spread, friends kept together.
-
Rec league reschedule requests: one captain asks, the other agrees, the organiser clicks once
Captains ask to move a game to a later date, checked against the season at once; the other captain agrees, and the organiser approves with one click.
-
Rec league scores confirmed by both captains, with no organiser step
Each team gets a captain link. When both captains report the same score it goes into the table; when they differ, the organiser sees both.
-
Team sign-ups for a rec league: a cap, a waitlist and your own payment link, self-hosted
A self-hosted league page now takes team sign-ups: one public link, a team cap with a waitlist, a fee on your own payment link, one-click approve.
-
Rec league waivers: the hard part is who has not signed, so the league page now lists them
The self-hosted league page now takes player waivers: your own text, versioned by hash, guardians for minors, and each team's unsigned players listed.
-
Sportsmanship ratings for a rec league, and why the table also shows how hard each team marks
Captains rate the other team after each game from their captain link; organisers sees averages, low ratings with comments, and which teams mark everyone hard.
-
Tell each team only its own moved games: schedule-change emails for a self-hosted league
Saving a rainout or withdrawal on the self-hosted league page can now email each affected team one list of only its own moved, cancelled or added games.
-
When two captains want different slots: keeping a league's time requests, and naming the impossible ones
A free league scheduler now keeps every early-slot and court request a night allows, and names the requests no schedule can keep before the season is sent.
-
Who's playing on the night: availability and short-handed teams on a self-hosted league page
The league page players already open now takes In, Maybe or Out per game and tells the organiser which teams are short of players before the night.
-
A 43-team league with every court busy in every slot, and nobody waiting
43 teams on 7 courts and 9 time slots went from 1,073 waits to none. The search was the same one that stalled yesterday; it just got 2.7 hours.
-
A 47-team league: from 5 wait-free nights to 13 of 16, and why a longer budget did worse
A neighbourhood search took a 47-team, 8-court season from 5 to 13 wait-free nights. Every failed repair ran out of time, yet 900 s repairs did worse than 300 s
-
A rained-out game should not leave a ghost in your players' calendars
The league schedule generator's calendar ids now name the fixture, not its date: 1,139 leftover ghost events after rainouts in our test leagues went to 0.
-
A shorter league season gave the bottom team the top ten: fixing strength of schedule
Cutting a round robin short handed the last-listed team the ten strongest opponents. Relabelling teams brings each tested league within 0.6 seed places of even.
-
A symmetry that breaks on a full night: what 49 teams on 8 courts did not teach us
Fixing a second symmetry should have cut the solver's search for a 49-team, 8-court league. On every fully booked size it made the night impossible to lay out.
-
A bowling league schedule where every team gets every lane pair evenly, and where the search still falls short
A free bowling league schedule maker: lane pairs rotated evenly over a repeated round robin. Even in 30 of 36 measured seasons; SAT shows the other 6 can be.
-
Build the season fairly, then load it into TeamSnap or SportsEngine in one upload
The free league schedule generator now writes TeamSnap's and SportsEngine's own schedule import files, columns copied from their published templates.
-
Nine trials in ten never needed to leave the module: 30-team leagues join the page
Counting first showed most of a schedule search's tables were copied out of WebAssembly and thrown away. Keeping them in cut the step 34%.
-
Stopping a refused trial early: why a lower bound did not speed up 30-team league schedules
A search for 30-team round robins refuses most moves by one to five breaks, so bounds that stop a trial early saved 6% of steps and no time.
-
When a schedule search stalls: 47 teams, five runs, no climb past 13 of 16 nights
Five resumed searches spent 26,870 core-seconds on a 47-team, 8-court season and none got past 13 of 16 wait-free nights. What that tells the next attempt.
-
29 and 35 team leagues with no waits: re-dealing two nights at a time
29 and 35 team leagues, three games a night, used to leave hundreds of waits. A search that re-deals two nights at a time with SAT got both to zero.
-
A 41-team league with no waits: the last night was impossible, so we changed who plays on it
41 teams, 7 courts, three back-to-back games a night. One night's pairings could never be laid out. Re-dealing it with the short last night fixed the season.
-
A 41-team league, 13 nights of 14 wait-free, and a search that can pick up where it stopped
A neighbourhood search got 41 teams on 7 courts to 13 of 14 wait-free nights. Two fixes made that possible: the search keeps its own layouts and can resume.
-
Wait-free nights for 33 to 63 team odd leagues: one night laid out is the whole season
Odd leagues of 33 to 63 teams on nine time slots went from thousands of waits to none, because one solved night repeats as the whole season.
-
We cut 17 seconds from two test files and the suite got 2 seconds faster
Two league-scheduler test files lost 17 s of repeated searching. The whole suite moved 2 s, within noise, because it was already close to CPU-bound.
-
Flip every host: a free factor of two in the break floor, and why 30 teams still wait
Swapping home and away for every game leaves a season's breaks unchanged. The schedule generator now uses that to halve its tables. 30 teams are still too slow.