Community servers are for experiments and groups.

When to use a community server

Use one when you want more control than an official queue provides. Friend nights, map tests, private tournaments, creator sessions, and teaching rounds.

Community sessions don’t replace official progression. They’re for flexibility.

Private by default

A private community lobby is the safest starting point. Invite the people you want, test maps or sandbox settings, and keep the session out of the public community server list until you are ready.

Public community lobbies should have a clear name and owner identity. Players need to know that the lobby is user-hosted and may not behave like an official server. If the server appears in the community list, set expectations up front: casual test, tournament warmup, map review, or custom chaos.

Setup concept

The community server package hides as much busywork as possible. The setup wizard creates configuration, checks the runtime, installs or links what it needs, and can help expose a stable public URL.

Normal path: download the server ZIP from the in-game server browser flow, extract it, install Node.js 20.19 or newer, run the setup command, and start the server.

What players should expect

Official servers are hosted by Fister and are the best path for public matchmaking, account progression, moderation review, and stable region selection. Community servers are hosted by players. Ping, uptime, settings, and moderation depend on that host.

If a community lobby feels laggy but official servers are clean, the issue is usually the host machine, route, or tunnel. If both are bad, check the troubleshooting guide before reporting.

Owner responsibilities

Community hosts control their environment. Choose who joins, watch for abuse, keep the package current, and set expectations for casual, experimental, or competitive sessions. Public servers still need moderation.

When something breaks, capture the exact command output, browser URL, and whether the issue appears on official servers too. Speeds up support.

Hosting checklist

• Install Node.js 20.19 or newer.
• Extract the community server ZIP into its own folder.
• Run the setup wizard from a terminal inside that folder.
• Use a stable URL or tunnel flow if players outside your network need to join.
• Keep private lobbies private unless you actually want strangers joining.
• Name public lobbies clearly so players understand the theme or event.
• Keep the package current when public game updates change server behavior.