Skip to content

Event log

The event log is a server channel where CivBot records the actions of players and moderators in gatherings and games. A moderator turns it on, and people read it to find out who kicked whom, who cancelled a gathering or who scrapped a game.

What you need

Before you start, you need four things:

  • Moderator permissions — the log can be turned on by the server owner, a member with the Discord “Administrator” permission or a member with the server's moderator role; see Players, moderators and admins.
  • A channel — a text channel on the server for the log; Discord channel permissions control who can access it, and the bot doesn't change them.
  • Bot permissions — in the log channel the bot needs the permissions “View Channel”, “Send Messages” and “Embed Links”.
  • The game panel — the server already has a game panel: you use it to create a trial game in step 3; see Game panel.

Steps

  1. Prepare a channel. Create a text channel for the log or pick an existing one. In the channel settings, give the bot the permissions “View Channel”, “Send Messages” and “Embed Links”. Check: the bot is in this channel's member list. Step 3 shows whether the bot can write there.
  2. Turn on the log. In any channel on the server, type /guild log_channel and pick the log channel in the channel option, for example /guild log_channel channel:#event-log. Check: the bot privately replies “Log channel set to #event-log successfully.”
  3. Check the first entry. The command itself writes nothing to the log: entries appear with events. Create a game on the game panel and immediately cancel the gathering with the 🗑️ button on the gathering card. Check: the log shows the entries “🎮 Game Created” and “🗑️ [Gathering] Game Cancelled”.

What else you can set up

A server has one event log. To move it to another channel, run /guild log_channel with the new channel. New entries appear in the new channel, and old ones stay in the previous one.

To turn the log off, run /guild log_channel without the channel option. The bot privately replies “Log channel cleared successfully.” There will be no new entries, and the ones already sent stay in the channel.

What the bot logs

The bot logs eight kinds of events. Each event is a separate message in the log channel.

Event When it appears What the entry contains
“🎮 Game Created” A player created a game on the game panel “@Orion created game”, where “game” is a link to the gathering card; the game's type and mode
“➕ Player Joined” A player joined the gathering Who joined, the list “Were in lobby (2):” if someone was already in the gathering, and the line “Total: 3”
“🚪 Player Left” A player left the gathering Who left, the list “Remaining (2):” if someone is left in the gathering, and the line “Total: 2”
“❌ Player Kicked” A game participant or a moderator kicked a player with the “Kick” button Who kicked whom: “@Orion kicked @Kai”
“🗑️ [Gathering] Game Cancelled” A game participant or a moderator cancelled the gathering with the 🗑️ button Who cancelled the gathering: “@Orion cancelled the game”
“🗑️ [Game #248] Game Cancelled” A game participant or a moderator scrapped the game with the “Cancel game” button in the game thread Who scrapped the game and the line “Reason: …” if a reason was given
“🔄 Players Swapped” Two FFA players swapped slots by mutual request “@Orion and @Vega swapped slots” and a “Go to game” link to the game card
“📣 Gathering Notification” A game participant or a moderator sent a notification with the “Notify gathering” button Who sent it, a line like “Patch FFA6 · 4/6”, “Channel: #…” and a “Go to game” link to the gathering card

The entry calls a scrapped game “cancelled”, and the game number is in the title. The bot shows the reason for scrapping only in the log. See Scrapping a game.

The bot writes the log in the server's primary language in Discord: Ukrainian, Russian or English. If the server's primary language is another one, the log is in English. See Bot language.

Entry layout

All entries follow one pattern:

  • Time — the first line under the title, accurate to the second. At the bottom of the entry there is also a date with a time. Discord shows both in your time zone.
  • Who did what — the main line with mentions of players; mentions in the log notify nobody.
  • Game — the last line: the type and mode in capital letters and the game creator, for example “PATCH FFA | Creator: @Orion”.
  • Stripe color — green for game creation and joining, orange for leaving, red for kicks and cancellations, blue for slot swaps and notifications.
  • Avatar — at the top right: that of the person who took the action, and in a kick entry, that of the kicked player; the slot swap entry has no avatar.

A game gets its number at the start, so gathering entries don't have one. In entries about a started game, the number is at the beginning of the last line: “Game #248 • PATCH FFA | Creator: @Orion”. In the “🎮 Game Created” entry, the last line has only the type and mode, with no creator: the creator is named in the main line. Instead of a line with the creator, the “📣 Gathering Notification” entry has a line like “Patch FFA6 · 4/6”: the game type, the mode and the largest number of players it takes (FFA6 is FFA for up to 6 players), then how many players have already joined (4 of 6).

What the log doesn't include

The log contains only the events from the section What the bot logs. The bot doesn't log:

  • a game start, with or without a draft;
  • finishing a game with /game finish or on the site;
  • a gathering that disappeared on its own because nobody pressed its buttons for 3 hours;
  • ready marks, bans, nation picks and Steam links;
  • refreshing a game with /game refresh.

Look for a started game by its thread in the game history channel: the game card in the thread shows its state (“In progress”, “Finished” or “Scrap”). See Game thread.

What can go wrong

  • The log is empty. The /guild log_channel command itself writes nothing to the log: the first entry appears with the first event, for example when a game is created. If games have been created but there are no entries, the bot lacks the “View Channel”, “Send Messages” or “Embed Links” permission in the log channel. Give the bot these permissions in the channel settings. You don't need to repeat the command: entries will appear from the next event.
  • Entries suddenly stopped appearing. The log channel was deleted, the bot lost its permissions there, or someone turned the log off by running the command without the channel option. Give the permissions back to the bot, or run /guild log_channel with the channel you want.
  • The bot replies “Moderator role not set. Please contact server administrator.” The server has no moderator role, and you don't have the “Administrator” permission. Ask a server admin to set the moderator role and give it to you. See Players, moderators and admins.
  • The bot replies “You are not moderator.” The server has a moderator role, but you don't have it, and you don't have the “Administrator” permission either. Ask a server admin to give you this role.
  • The gathering disappeared, and there is no cancellation entry. If the game started, look for its thread in the game history channel: a start isn't logged. If nobody presses a gathering's buttons for 3 hours, the bot removes it on its own and doesn't log that either. The “🗑️ [Gathering] Game Cancelled” entry appears only when a gathering is cancelled with the 🗑️ button.
  • The log has no game start or finish. The bot doesn't record these events in the log. Look for the game thread in the game history channel.
  • Entries are in English or Russian. The log is written in the server's primary language in Discord, not in the language of your client. See Bot language.

This page was translated with AI and checked against the bot's terms.