Public content and Discord webhooks

Public content explains the rules, server features, events and available modules to players. A Discord webhook determines where and in what form this content is sent. These two things are separate: you can save the text without publishing, and you can set the webhook without changing the game server.

Webhook overview

On Discord webhooks, targets are grouped by type and language. Each tab shows whether the address is saved, whether the destination is active, whether it uses a regular message or an embed, and the state of the last synchronization.

1. Open the desired output tab.
2. Insert or review webhook URL. An empty value will delete the existing URL.
3. Optionally set the name and avatar of the sender.
4. Choose message or embed, color and image placement.
5. Turn on the target and save.
6. Use the available Sync action to check the delivery result.

Some targets additionally support automatic publishing or interactive bot connection. If the option is not displayed in the form, the given type does not support it.

Common appearance

In Webhooks Settings global footer and live status interval are adjusted. An individual webhook can override the global footer. The status interval can be set from 10 to 3600 seconds.

Live server status

On Server status one common webhook and one continuously edited embed message is used for each added server. For each server, you set publishing, title and text with abbreviations, color of online/offline status, image and optional list of players.

The list of player names is private by default and must be turned on consciously. Also set the maximum number of names. Disabling publishing will delete the relevant live message, not the server or its settings.

Where public content is edited

• Server Info and highlights,
• Discord info, map zones and server support,
• changelog, planned events and unexpected events,
• rules and Warzone, insurance, duels and Squad Wars information pages,
• voting.

Permanent information pages usually edit the same Discord message to avoid duplicates. Events can have multiple separate posts. The published vote is immutable; redoing it will create a new vote and the original votes are not carried over.

Public content is the communication layer. Saving rules, events or information text does not change game mechanics, server configuration or module behavior.

Example from Main

As of 1 September 2026, there were 161 supported targets in the register, of which 49 were active and configured. A global footer was set and the live status was refreshed every 30 seconds. Main had its own online and offline color, image and optional player list with a limit of 20 names. The status "needs sync", "never" or "failed" with an old or disabled target does not automatically mean a failure of active publishing - always open a specific tab.

When the content on Discord has not changed

1. Verify that you are editing the correct content type, language and server.
2. Check if the webhook is active and has URL saved.
3. See Sync status and last delivery result.
4. When the status is live, wait for the set interval.
5. If you just saved the content, use the publishing or Sync that the site offers.

Never insert the entire webhook URL into ticket. All you need is the name of the target, the time, the status and the displayed error message.