Skip to main content

Operator guide

What running KOTT for your community actually involves — including the parts that constrain you. Worth reading before you commit, not after.

What you're agreeing to

  • You run an AssettoServer instance with the KOTT plugin installed. It talks to KOTT over HTTPS. The machine stays yours — we have no access to it, cannot start or stop it, and cannot read its files.
  • KOTT holds a killswitch. We can suspend a community for policy violations, abuse, or abandonment. A soft suspension lets in-flight races finish and refuses new ones; a hard suspension stops the plugin at its next heartbeat. You would normally hear from us first.
  • Lap times, race results and ratings flow through KOTT. Your server is the race host; we are the record keeper.
  • Your players are owed the plugin's source. The plugin is AGPL-licensed, and the in-game panel and /source already carry that offer. Don't strip them — that is what keeps you compliant.

What you get

  • Your own community page with your name, colours and logo, plus leaderboards and lap history for your drivers.
  • A ranking that is yours. Battles on your servers feed a skill rating scoped to your community — your drivers, your standings.
  • Verified timing and race judging. Laps are validated server-side; battle results are re-derived from the race trace rather than trusted from the client.
  • An operator dashboard for your servers, bans, crews, branding and plugin updates.
  • Discord integration for result notifications.

What you can run

Your licence permits Touge — one server that hosts cruising, solo timed laps and on-demand 1v1 battles together. Deliberately one server rather than three: splitting a community across modes leaves you with several half-empty servers, and an empty server reads as a dead community.

KOTT's global ranked queue is not included, and cannot be switched on from your side — it runs only on servers KOTT operates, for events. If you configure Mode: MATCHMAKING the plugin refuses to start and says so, which is deliberate: a server that boots and then silently never matches anyone is worse.

Licence and renewal

Your licence lasts a year and renews itself. Once inside 60 days of expiry, any successful heartbeat pushes it out again — so a server that comes online even occasionally never expires, and there is nothing to remember.

If a server stays offline long enough for the licence to lapse, the plugin enters lockout and you'll need a fresh bundle from your dashboard.

When KOTT is unreachable

The plugin heartbeats every ~30 seconds. If it can't reach us:

  • Six failures — degraded. Racing continues. Results queue locally and replay when the connection returns. Players see a banner.
  • 24 hours — locked. New races are refused; in-flight ones finish. This exists so a disconnected server can't accumulate results nobody can verify.

Planning downtime? Schedule a maintenance window from your dashboard first and the 24-hour rule is suspended for its duration.

Being listed publicly

Your community page works from the moment your server connects, and anyone with the link can reach it. Appearing in the public communities directory is a separate request you make from your dashboard, because that directory is curated. Declining a listing never affects your racing, and you can remove yourself at any time without asking.

Next

Install guide — the exact steps to get the plugin running.
Apply — tell us about your community.
Help — everything else, or reach us on Discord.

Connection lost

Reconnecting…

Reconnecting… the page will reload automatically.

The session was rejected by the server. A reload is required.