Sanctions
User Guide
This page explains the measures the TennoCore team may take when a server or a user does not comply with the bot's terms of use (article 13). It describes what you see if a measure concerns you, what exactly it blocks, and how to appeal against it.
The four measures
The scale is graduated: the measure is chosen in proportion to the breach observed.
| Measure | What it targets | Effect | Duration |
|---|---|---|---|
| Warning | a server or a user | No restriction. The measure is kept on file; in the event of a repeat offence, a heavier measure may be issued. | — |
| Module restricted | one specific module of a server | The module becomes unusable: its commands and its configuration page are unavailable. The other modules keep working normally. | with or without an end date |
| Suspension | a server or a user | Everything is cut off: bot commands and dashboard. For a server, the bot stays present; for a user, the measure applies across all servers. | with an end date in principle |
| User ban | a user | Like a suspension, across all servers, and with no end date. | permanent |
Banning an entire server is the final step and works differently: the bot leaves the server. It is described on its own page, Server ban.
How you are notified
- A direct message is sent as soon as the measure is issued. For a measure targeting a server, it goes to the server owner — they are the one who accepted the terms by adding the bot. For a measure targeting a person, it goes straight to them.
- That message states the measure, the server concerned where applicable, the reason, the module targeted if there is one, and the end date when there is one. In its footer it recalls the deadline for appealing.
- When the measure is lifted, a second direct message confirms that access has been restored.
- If your direct messages are closed, the message does not go out — the measure applies anyway. The information remains viewable in the dashboard.
What you see in Discord
While the measure is running, every command, button or menu concerned gets a private reply explaining the block: title of the measure, reason, module concerned and the planned lifting date (or the mention "No end date").
Features already configured also stop acting on their own: automatic reactions, welcome messages or the periodic tasks of the targeted module are suspended for the duration of the measure.
What you see in the dashboard
- A "Active TennoCore restrictions" card appears on the home page of the server concerned. It lists every active measure — warnings included — with its reason and its end date, and offers two buttons: Appeal and Terms of use.
- If you open a locked module, the configuration page is replaced by a screen explaining the measure. The rest of the dashboard remains usable.
- If your entire access is blocked (suspension or user ban), the same screen is displayed full-page on login, with the remaining time and the ways to appeal.
- A server's administrators see a "Members sanctioned by TennoCore" card listing their members who can no longer use the bot. The reason is not disclosed: it often concerns events that happened elsewhere. This measure does not exclude them from your server; what you do about it is up to you.
Appealing against a decision
Any measure can be appealed within 30 days of being issued:
- by email at [email protected];
- or from the TennoCore support server.
State the ID of the server concerned and the points you dispute. A reasoned answer is given within a reasonable time, in principle within 14 days. The measure is lifted if it turns out to have been unfounded or disproportionate.
The bot's assistance channel and the language selection remain accessible even under sanction, precisely so that this right can be exercised.
Good to know
- Expiry is automatic. At the end date, access is restored with no intervention: just reload the page. No action is needed.
- A restricted module is cut off everywhere, not just in the dashboard: its commands, its buttons on already published panels and its automations are disabled at the same time. A few purely web modules have no commands: there, the lock only affects the dashboard.
- The module name displayed is the one you see in the dashboard menu, never a technical name.
- A server suspension is not a ban: the bot stays in the server, its features are simply inert for the duration of the measure.
- A user ban is permanent and follows the person across all servers, including those where they are an administrator.
- A measure may target a person without targeting their server, and vice versa. The two records are independent.
- A warning blocks nothing, but it is recorded: it counts in the event of a repeat offence.
- The most serious breaches — unlawful content or activities — in principle lead to an immediate and permanent measure, with no prior warning.
- The full detail of the scale of measures is set out in article 13 of the terms of use.