Community setup
Finding your way around your community's pages, the getting-started checklist, creating a season, your servers and settings.
Your community's page is where you set up and watch everything your community runs. This page explains the checklist, the season form, the server list, the settings and who manages the community.
Finding your way
Open Organise in the top bar and select your community under Communities. Its page has:
- A tab bar: Overview (this page), Open servers, BoP, Members and Settings. Each tab is one click from the others.
- Public page, which shows your community as drivers see it. See Communities.
- All your communities, the back link to the Organise overview. See Organising.
A season's page, a server's page and a new single event are opened from the overview and have a back link with your community's name that leads back to it.
The getting-started checklist
A new community shows From a community to its first race at the top of its page. It has six steps. Only the next open step has a button, so the page always points at one thing to do.
| Step | Done when | Button |
|---|---|---|
| 1. Register a machine | Your community has a machine or a server | Register a machine |
| 2. Start the host agent on it | A machine or server has reported in | Open the setup guide |
| 3. Create a season | The community has a season | Create a season |
| 4. Add a series | A season has a series | Add a series |
| 5. Put races on the calendar | A season has races | Pick tracks |
| 6. Publish the season | A season is published or finished | Review and publish |
Steps 1 and 2 also count a server you run by hand with an API key. The checklist is about having somewhere to race, not about how. The page updates by itself when your agent first reports in, so you can leave it open while you set up the machine.
When all six steps are done, the checklist goes away.
For steps 1 and 2, see Machines. For steps 3 to 6, see Seasons and series.
Create a season
Use the New season card beside your seasons.
- Enter a Name, for example "Autumn 2026".
- Choose the Simulation if the platform offers more than one.
- Set Starts on and the number of Weeks (1 to 52).
- Optionally open More options:
- Weeks that count for standings: each driver's best weeks that count. If you leave it empty, all but a quarter of the weeks count, for example 9 of 12.
- Shown as: Season, Special event, Cup or Endurance.
- Select Create season.
bdr opens the new season's page so you can add a series.
Tip
For a one-off race, select + New single event instead. See Single events.
Seasons
The Seasons list shows each season's simulation, dates, number of series and status: Draft, Active or Finished. Select a season to open it.
Servers
The Servers card lists every race server of your community. Each row shows:
- A dot and status: Online (green) or Offline, and what the server is doing, for example Idle or Running.
- Simulation, region and mode, the time of the last heartbeat and the agent version.
- A clock warning if the machine's clock is more than 5 seconds off. Races still start on time, but it's worth fixing the clock.
Each server has three buttons:
- History opens the server's page. See Race servers.
- API keys lists the server's keys and lets you create or revoke them.
- Remove deletes the server and its API keys.
When your races run on your machines, bdr creates the servers it needs and names them pool-<machine>-.... They show up in this list too. You don't need to create API keys for them.
Select Machines on the Servers card to manage the machines themselves. See Machines.
To register a server you start yourself, open Running ACC by hand instead? under the season form. See Race servers.
Running now
Running now lists every split that has a server working on it, from the moment the split is given a server until it ends. Each row shows the series, split label, track, number of drivers, the server and its state: Assigned, Starting or Running. Select the series name to open the race.
If a split stays Assigned close to the start, its server has not reported back. Check the machine. See Machines.
Settings
Select the Settings tab on your community's page. Owners and admins can change:
| Field | What it does |
|---|---|
| Name and Description | Shown on the Communities page, your community's public page and your races. |
| Discord invite | A link like https://discord.gg/abc123, shown with your community so drivers can join. |
| Website | Shown next to the Discord link. |
| Server names | How your open lobbies and race servers are listed in ACC's server browser. See Server names. |
| Default webhook | The Discord webhook bdr posts to, for every topic that has no channel of its own. |
| A channel per topic | Optional webhooks for Reports, Race results, Bans, Machines, Open lobbies and Platform (ranked status, use of the platform's machines). Leave one empty to use the default, except Race results: results are only posted to a channel of their own. |
| What each topic posts | Every topic lists its messages, such as New reports, Verdicts, A banned driver on your open lobby or Restarted. All are on; untick what you don't want in Discord. |
The community's address (the part of the URL after /organizer/) cannot be changed.
To create a webhook in Discord, open the channel's Edit channel, then Integrations, then Webhooks, and copy the URL. After saving it, select Send a test message, or Test next to a topic, to check the channel receives it. Keep the URLs private: anyone who has one can post to that channel.
Each race split's result is posted to Race results once it is rated: a table of positions, gaps to the winner, best laps and the grid position with places gained (▲) or lost (▼), the fastest lap, and a link to the race. The grid comes from the split's qualifying result; without one that column is left out. Drivers without an account are shown by their initials.
Note
A series can still have a webhook of its own for its reports, under Splits, ratings and entry rules. Its reports go there instead of the Reports topic. See Seasons and series.
Server names
Under Server names in Settings you write how your servers appear in ACC's server browser: one template for open lobbies, one for race servers. Write any text you like, such as your Discord invite or what the server is for, and add placeholders in double braces:
{{community}} | {{track}} | ranked races and lap time records | discord.gg/abc | {{bop}}
| Placeholder | Open lobbies | Race servers |
|---|---|---|
{{community}} |
Your community's name | Your community's name |
{{track}} |
The track | The track |
{{car_class}} |
The car class, empty for any car | The car class |
{{name}} |
The lobby's own name | |
{{bop}} |
The Balance of Performance, empty for ACC's own | |
{{series}}, {{season}} |
The series and its season | |
{{split}} |
The race and split, such as #1042-1 |
The form shows what ACC will list as you type. A placeholder with nothing to fill in drops its part between the |, so a lobby without a BoP has no empty | | at the end. A race server's name always ends with its split if your template leaves {{split}} out: drivers find their split by it. Leave a template empty for the default: {{community}} | {{name}} | {{bop}} for lobbies, {{community}} | {{series}} | {{split}} for races.
A running lobby takes a new name once nobody is on it, or at once if you select Restart now on it.
Owners and admins
You become an owner of a community you create. Owners and admins can open this page and manage everything on it. See Organising for what each role allows.
The Members tab has your staff and your drivers: owners invite people onto the staff from the roster, and the invite link brings drivers onto the roster. See Staff.