Limits of your game's Discord and FAQ
The caps below are technical limits, not offer quotas.
What the bot does not do
Section titled “What the bot does not do”- It configures AutoMod, but it does not replace your moderators: no kicks, bans, or deletion of other people’s messages. Discord applies the native filters.
- It does not read conversations. It does not receive the content of messages on your server.
- It does not answer anyone, except with the
/evenementscommand, privately. It never sends direct messages. - It does not manage your members: no roles given to players, no nicknames, no invitations.
- It does not give access to VibeStarter support. Your players have no way to reach us through this bot; you write to support@vibestarter.pro.
- It does not relay your wiki. No wiki publication triggers a message.
- It does not create native Discord events, and does not schedule anything in your server’s calendar.
- It cannot be removed from the app. It leaves the server by itself 30 days after unlinking or after Community ends without being resumed, or when you delete the project or your VibeStarter account; resetting does not make it leave. To remove it right away, go through Discord. See When the bot leaves your server.
- It does not act without Community. When Community ends for the game, it goes silent right away; the AutoMod rules already in place are still applied by Discord.
- It cannot be installed by someone else. The Discord account that authorizes must be the one linked to your VibeStarter account.
AutoMod protections
Section titled “AutoMod protections”The agent manages its own rules; it keeps those created by administrators and other bots. Rules with regular expressions or profile filters stay read-only. A change made directly in Discord may ask the agent to reread the rule before it continues. Avoid making changes at the same time.
Native blocks and alerts do not count against the game’s announcement cap. Discord sets its own limits on rules, shared with the rules already on your server. If a limit is reached, the agent reports it without removing an existing protection. Timeouts require the matching permission and an explicit request.
Test the filters with an ordinary test account: privileged accounts, bots, and Discord exemptions do not behave like regular members. Filters do not guarantee that every abuse will be caught, and they can block a legitimate message.
| What is limited | The limit |
|---|---|
| Server per game | One only, and a server serves only one game |
| Bot messages per 24 hours | Between 1 and 24, adjustable, 4 by default |
| Announcement rules per game | 20 |
| Pending actions per game | 20 |
| Minimum interval between two sends of a rule | From one minute to seven days |
| Incoming events | 30 per minute per game |
| Wait for a “To review” approval | One hour, then the send is canceled |
| Message length | 2,000 characters |
| Servers connected to the service | A limited number at this stage |
The number of connected servers also limits sales: when all the bot’s places are taken, or owed to games that already have Community or a payment in progress, Community and the Starter pack are no longer sold until a place frees up. A game whose place is already owed is never refused.
These limits protect the service and can be adjusted; they are not commercial quotas. Access terms will be published on the Pricing page when Community opens.
The statuses shown, and what they mean
Section titled “The statuses shown, and what they mean”| What you see in the app | What to do |
|---|---|
| “Bot connected · N channels visible” | Everything is fine. |
| “Waiting for the bot: no sign for 3 minutes.” | Wait a minute. If it lasts, reinstall the bot. |
| “The bot was removed from the server. Reinstall it to resume.” | Someone removed it on Discord. |
| “The server is temporarily unavailable to the bot.” | A temporary incident on Discord’s side or the server’s side. |
| “Discord did not answer. Try again in a moment.” | Try again. |
| “This game changed owner: the link must be reviewed by our team.” | Write to support. |
| “Link this game to the project first.” | Link a place to your project, in the app. |
| “Plan required” | Community is not turned on for this game. |
| “Settings changed elsewhere and were reloaded.” | Another window changed the same thing. Check, then save. |
A refusal during installation does not appear in the app, but in the browser, under the title “Installation interrupted,” followed by its cause: Discord account different from the linked account, server already linked to another game, game already linked to another server, number of connected servers reached, link or confirmation expired. The details are in Install the bot.
Frequently asked questions
Section titled “Frequently asked questions”Who can install and configure the bot? The project owner, and only the owner. A collaborator accepted as an editor does not have access to this section.
Who pays for the agent’s work? You do, through your AI account: the Discord agent works with it, like a development agent, and uses its quota. Community includes the bot and its operation, not the AI.
What happens to the bot if I stop Community? It goes silent right away. You can unlink the server at any time; if Community is not resumed within 30 days, it leaves the server and the link is released. See When Community ends.
Can my players talk to the bot?
They can type /evenements, and that is all. The bot holds no conversations.
Can the bot edit a message I wrote myself? No. It can only edit or delete its own messages.
Can I see what the bot did on my server? Yes. Every action appears in your Discord server’s audit log, with a readable reason that starts with “VibeStarter action.”
Does the bot count /evenements toward my daily cap?
No. Only the messages it posts in a channel count.
Is this bot the same as the VibeStarter community bot? No: two different Discord apps, two different roles. See Discord and VibeStarter.