When Something Does Not Work

First: /check

Before you go looking for anything, type /check. The bot then checks itself and tells you in plain words what is missing — with the solution next to it:

• missing permissions, named one by one
• roles that sit above the bot role (the most common reason for "it does not work")
• configured channels or roles that no longer exist
• channels the bot is not allowed to write in
• modules that are on but configured incompletely

Red dots stop something from working. Yellow ones are notices that could cause you trouble later on. After every change, run it again.

And if you only want to know what the bot can do at all: /hilfe.

The slash commands do not appear

Type / and wait a moment — Discord sometimes loads the list with a delay. If nothing comes up after that:

1. Is the bot really on the server? It should be in the member list.
2. Was it invited without the applications.commands scope? Then invite it again via the invite button on the start page — existing settings are kept.
3. Restart Discord (Ctrl + R).

"Diese Interaktion ist fehlgeschlagen" (this interaction failed)

That is Discord's standard message when the bot does not reply within three seconds. Usually it was a short hiccup — try again. If it happens permanently, the bot is offline; /status then gives no answer either. Have a look in the support Discord, it says there whether maintenance is in progress.

"Mir fehlen Rechte in #kanal" (I am missing permissions in #kanal)

The bot is not allowed to write in that channel or not allowed to embed links. Check the channel permissions for the bot role. Note: a denial at channel level overrides the server role.

The builder does not respond any more

After 30 minutes without a click, a builder session expires, so that nothing stays hanging in memory. /embed create opens a new one. Saved embeds are not affected by this.

An image is not displayed

The URL must point directly at the image file and start with https://. A link to an image gallery or a Google Drive preview is not enough. To test it: open the link in a new tab — if only the image appears there and nothing else, it is fine.

My server does not appear in the dashboard

The dashboard only shows servers on which you have Server verwalten (manage server) or Administrator. Log out once and back in — the server list comes from Discord and is cached briefly.

"Das ging zu schnell hintereinander" (that was too quick in succession)

The bot has a limit against abuse: 20 actions per person in 30 seconds, 60 per server, and at most 10 messages sent per minute. In normal operation nobody reaches that — the limit exists so that nobody uses the bot as a spam machine or takes it down for all the other servers. Wait a moment, then it continues.

After paying, the plan still says Free

The confirmation from Stripe takes a few seconds. Reload the dashboard. If it still says Free after five minutes, get in touch in the support Discord with the server ID — that can be put right by hand.

A custom command does not appear in the input field

After /befehl anlegen it takes about a minute until Discord suggests the new command. It works immediately, it is only not being suggested yet — type it out by hand once.

If it stays missing permanently, the bot was unable to register it with Discord. At the next restart it reconciles this automatically. The most common reason is a name with umlauts or spaces; only lower-case letters, digits, hyphens and underscores are allowed.

Reaction roles: nothing happens when clicking

Almost always the role hierarchy. /check tells you in one sentence. In the server settings, the bot role must sit above every role it is meant to grant.

Second most common reason: the bot lacks the Reaktionen hinzufügen (add reactions) permission in the channel. Then the message is there, but without emojis underneath.

Invites are not counted

Two possible causes:

1. The bot lacks the Server verwalten permission. Without this permission it is not allowed to read the invite list and counts nothing at all — without an error message.
2. Two people came in through different invites at the same time. Then it cannot be said who belongs to whom, and the bot deliberately counts nothing instead of crediting it to the wrong person.

Joins that happened before the module was switched on do not appear retroactively.

The bot does not congratulate anyone on their birthday

Check under /geburtstag setup whether a Kanal (channel) is entered — without it nothing happens, that is the only mandatory entry. Congratulations go out on the full hour you have set, in German time, so not immediately after the entry is made.

If the Servermitglieder (server members) intent is also missing in the Discord developer portal, the bot cannot look up members. The same applies to invites and to the join rules in the automations.

An automation does not run

New rules are paused on purpose. Open them with /auto bearbeiten and arm them with "Aktivieren" (activate) as soon as there are actions in them.

If it still does not run, switch on a Protokoll (log) channel under /auto setup. After every trigger it says there what happened — and what was skipped, for instance because a role is locked or sits above the bot role.

Twitch reports nothing

For Twitch the bot needs its own access (client ID and secret), which you create for free in the Twitch developer console. If it is missing, the bot says so when you enter the channel.

With YouTube it works most reliably with the channel ID (starts with UC…) instead of the name. And: a channel that is live at the moment you enter it is not reported retroactively — only the next broadcast is.