Skip to content

Your game's announcements

Coming soon

Announcement rules are set by talking to the agent, not in a form.

The bot does not post anything on its own initiative, and does not follow any schedule. An announcement goes out when your game’s code signals an event — a boss defeated, a season opened, an update deployed — and a rule says what to do with it.

  1. Your game signalsYour game’s server code sends a named event, with a few values.
  2. A rule matchesIt sets the channel, the message, the minimum interval and the conditions to meet.
  3. The message goes outBy itself, or after your approval, depending on the mode you chose for this rule.
From a game event to a message on your server. Nothing goes out without a rule you have created.

There is no form to fill in. The Discord section has its own agent: at step 3,

Start the agent, you choose the AI tool and click

Start the agent, then describe in plain language what you want in its terminal. The agent creates and changes the rules. It works with your AI account and uses its quota: Community does not provide the AI. The step says “Running · talk to it in the terminal” while it runs.

A rule always has:

  • an event, by its name, the one your game’s code sends;
  • a channel on your server where the bot is allowed to post;
  • a message, into which the event’s values are inserted;
  • a minimum interval between two sends of this rule, from one minute to seven days;
  • optional conditions on the event’s values: announce only above a certain score, for example;
  • optional start and end dates, for a seasonal rule.

Three settings apply to the whole game, and are also set by asking the agent: the bot’s language (French or English), the tone of its messages — “Clear and welcoming.” by default — and the maximum number of messages per day, between 1 and 24, 4 by default.

Mode What happens
Auto send The message goes out by itself as soon as the event arrives and the conditions are met.
To approve The message waits for your approval in the conversation with the agent. If you do not reply within one hour, it is cancelled.
Paused The rule exists but triggers nothing.

As soon as a server is linked, the section shows the Game events → Discord table: one row per rule. Rules are changed with the agent; only resuming a channel after a server change is done directly in the table. On the left, the game event: the rule’s name, the technical name of the event as your code sends it, and “Last received:

date” or “No event received yet”. On the right, the channel where the bot announces, and the mode: “Auto send”, “To approve in the conversation” or “Paused”. The header counts the events tracked and shows the date of the last one received.

Below it, Latest announcements lists the bot’s latest messages with their status — “Sent”, “To approve in the conversation”, “Waiting to send”, “Sending…”, “Failed”, “Cancelled” or “Uncertain result, check Discord” — their channel and an excerpt.

If a rule shows “Channel to choose”, use its selector to assign a channel the bot can access on the new server. See Unlink and reconnect.

Adding a row, changing a channel you have already chosen or pausing a rule takes one sentence to the agent. As long as there is no rule, the table shows “No event wired yet” and “Tell the agent what to announce: a boss defeated, an event starting…”

As long as your game sends nothing, no announcement can go out: this is the most common cause of a silent server. The wiring is done with the Discord agent, which installs the event sender in your game’s server code and stores the event key in the secrets of your Roblox experience.

For this, your Roblox Open Cloud key saved in the settings must have the Secret Store, read and write permission on this experience. This is step 2 of the Discord section,

Allow your Roblox API key: its status says “To do before launching the agent”, “Missing permissions on the API key” if the agent tried and Roblox refused, then “Game wired” once the event key is stored. The Open Settings button takes you straight to the key field. Add the permission in Creator Hub, then tell the agent to try again. See Link your Roblox account and your Open Cloud key.

The bot adds a single command to your server: /evenements. It lists the events tracked and their next dates, in the language set for your game.

Three things to know:

  • The reply is private. Only the player who types the command sees it; it does not clutter the channel.
  • It respects access. An event attached to a channel this player cannot see does not appear in their reply.
  • It triggers nothing and does not count toward your daily message limit.

If the server is no longer linked to a game, the command replies “This server is not linked to an available game.”

  • They do not relay your wiki. Publishing a wiki page sends no message on Discord. The two services are independent; see The wiki for your game.
  • They do not mention anyone. Mentions are disabled in all the bot’s messages, including those written in your template: no @everyone, no role, no member.
  • They do not create a native Discord event. The dates announced are text, not events in your server’s calendar.
  • They do not catch up on missed messages. An event skipped because the minimum interval had not passed is not replayed later.

My game sends events, but nothing appears on Discord. Check in this order: does the rule’s line show a “Last received” date? Is the rule “Paused”? Is the channel still accessible to the bot? Has the daily limit been reached?

The table says “Channel unavailable”. The channel is missing or the bot can no longer access it. Ask the agent to point the rule to another channel.

Can I have the bot post manually? Yes: ask the agent. The message is sent like a regular announcement and counts toward your daily limit.

An action says “Uncertain result, check Discord”. The result of the send could not be confirmed. Look at the channel concerned on Discord before running anything again, so you do not publish twice.