Skip to content

How we ran Kacky of The TKG on four servers

Kacky of The TKG, or KOTT, was the cup night of The Kacky Games 2026: one handcrafted map, a 25-minute qualifier, then a knockout that eats the field a few players at a time until one is left. 203 people turned up on 20 September 2026.

Here's how it ran, and the one part we got wrong.

One map, more players than a server holds

Our boxes take about 100 players before the game server starts fighting itself for processor time, and earlier Kacky Games nights told us to plan for 300.

Splitting the field across servers is easy. Making the result mean anything is not. If every server counts down on its own clock, whoever started first gets more time on the map, and on a Kacky map the first five minutes are pure discovery. That's not a rounding error, that's the qualifier.

So we ran four servers, but not four of the same thing. Three held the qualifier. The fourth sat empty and waited for the cup, because a cup host that also qualifies fills up with players who didn't make it, and the mode never moves anyone out of a slot: the people who earned a place would arrive to find the door shut. On the night the three qualifier servers held 92, 56 and 55 players.

One start, everywhere

The admin starts the qualifier once, and that command doesn't start anything. It writes a single decision naming the moment, five seconds out, when every server begins. Each controller reads the same decision and schedules the same instant.

Two rules keep it honest.

A server that can't make that instant doesn't quietly start late. It records the attempt as missed, and its run dies right there. A late server is worse than a missing one, because its times look perfectly normal and aren't comparable to anything.

And pressing the button twice changes nothing. The second press reuses the same decision, deadline and all, so a nervous admin can't move the start.

Every server seals its own result

Each server keeps its own ledger: every account that set a time, their first finish, their best lap, all measured from the start of the run rather than the clock on the wall.

When the 25 minutes are up, the server seals that ledger, and the whole night rests on the fact that a sealed ledger can't change. The controller then hands it to the platform, and hands it over again if the first attempt goes missing. The platform keeps the first sealed copy it sees and ignores the rest.

No ranking appears until every expected server has sealed. The platform is told which servers to expect, and it never infers that list from whatever turns up, because a server that crashed and sent nothing looks exactly like a server that was never meant to play. The empty cup host sealed too, with zero players. That's the proof it was there and heard the start.

One ranking out of three races

The merge is the easy part: every player keeps their best eligible time from any server. All 203 stayed where they joined, so nothing actually needed merging, but the rule is there for people who hop between servers hunting a free slot.

Top 100 went through as the single knockout division.

The knockout, and the gulag

The knockout is Cup of the Day with one Kacky addition. Same map, round after round, slowest out each time. Every fifth round is a gulag: the players already knocked out race each other and half of them come back. Once about five players are left the gulag stops, and the last rounds settle it.

31 rounds. Schmaniol won, ahead of SmithyTM.

Two things cost us time. The button that takes a player into the cup server didn't work, so people joined by hand or stayed to watch, and more spectators turned up than we'd planned for. A spectator holds a connection like anyone else, so some of that room was gone before the cup started. We also spent part of the evening on the gulag settings, because a default kept overwriting the values we set. We still don't know why.

What we got wrong

The qualifier was built so its result could never be lost. The knockout wasn't.

The cup mode keeps the final placings in memory and puts them on screen. It never sends them anywhere, and our controller never asked. When the night ended, the ranking that decided the whole event lived only in the memory of the people who watched it.

We rebuilt it from two things we did record: the round boundaries in the server log, and every lap time. In an elimination format a player stops driving when they're out, so the round holding their last lap is the round they left in, and the finishing order is that list reversed.

It's close. It isn't exact. Someone who crashes out of their final round sets no time and can read one round early, and two players who left in the same round can only be separated by their laps inside it.

Which is the lesson every event teaches again: a result that only exists on screen isn't a result. If you can see it, you can store it, and you store it while it's still true.

If you want the mechanism, KOTT under the hood has the mode script.