Ist TeraOne wirklich kostenlos?

Ja. Alle Module sind während der Startphase kostenlos. In Zukunft wird es optional Premium-Features geben, aber alle heute existierenden Module bleiben für bestehende Nutzer frei.

Welche Permissions braucht der Bot?

TeraOne fragt beim Einladen die Standard-Admin-Permissions an. Du kannst die Permissions im Discord-Rollen-Menü nachträglich reduzieren, wenn du nur bestimmte Module nutzt.

Kann ich Module einzeln aktivieren?

Ja. Jedes Modul hat im Dashboard einen eigenen Toggle. Aktive Module können jederzeit wieder deaktiviert werden, ohne dass Daten verloren gehen.

Wo werden meine Daten gespeichert?

Auf einem dedizierten Server in Deutschland. Nur die für die Funktion notwendigen Daten (Server-ID, Modul-Einstellungen) werden persistiert. Details in der Datenschutzerklärung.

Was passiert wenn ich den Bot entferne?

Beim Entfernen werden die Server-spezifischen Daten nach 30 Tagen automatisch gelöscht. Bis dahin kannst du TeraOne ohne Verlust wieder einladen.

Custom bot

Run TeraOne features under your own bot name

With a custom bot, TeraOne runs under your own Discord bot account — with your chosen name, avatar, and banner. To your community it looks as if your own bot provides all the features. The technical foundation remains TeraOne.

When is this useful?

You want branding: the bot should be called "GameServer-Bot", not "TeraOne"
You want Slash-Commands to appear under your bot's name
You run multiple servers and want a consistent brand identity

Requirements

A Discord account (no separate developer account needed — just registration in the Developer Portal)
The bot must be invited with Administrator permissions

Step-by-step setup

Step 1: create a Discord application

Open https://discord.com/developers/applications and click "New Application". Choose a name (this also becomes the default bot name). Click "Create".

Step 2: generate a bot token

Open the "Bot" tab in your application. Click "Reset Token" and confirm. Copy the token immediately — it is not shown again.

Never share the token. Anyone who knows it can fully control the bot. If it leaks: immediately click "Reset Token" in the Developer Portal and enter the new token in the TeraOne dashboard.

Step 3: enable Privileged Gateway Intents

Still in the "Bot" tab, under "Privileged Gateway Intents", all three Intents must be enabled:

SERVER MEMBERS INTENT → ON
PRESENCE INTENT → ON
MESSAGE CONTENT INTENT → ON

Without all three Intents, Leveling, AutoMod, Anti-Alt, and the welcome module will not work correctly. This is the most common setup mistake.

Step 4: name, avatar, and banner

In the "Bot" tab you can set the bot's username and avatar. In the "General Information" tab you can add an app icon and description. Banner and other profile details are set via Discord settings after the bot's first login.

Step 5: generate an invite link

Open the "Installation" tab. Under "Default Install Settings", make sure "guild_install" is enabled. Copy the generated install link (or create one manually with scope bot+applications.commands and permissions 8 for Administrator).

Step 6: invite the bot

Open the invite link in your browser, select your server, and confirm. The bot needs Administrator rights and the applications.commands scope so that Slash-Commands can be registered.

Step 7: enter the token in the TeraOne dashboard

Open Dashboard → Settings → Custom bot. Paste the token into the token field and click "Save". TeraOne starts the bot within a few seconds.

Step 8: wait for status "Online"

In the dashboard, the custom bot tab shows the current status. After saving the token, it can take up to 30 seconds for the bot to appear as online in Discord.

If the status still shows "Offline" after 60 seconds, check: are the Intents enabled? Is the token entered correctly (no leading or trailing whitespace)?

What the custom bot can and cannot do

Can: all TeraOne modules (Leveling, Moderation, AutoMod, Anti-Alt, audit log, welcome, reaction roles, YouTube, DayZ Killfeed) under your own name and avatar. Bot presence (name, status, activity) is exclusive to the custom bot — it does not apply server-globally.

Cannot: register custom Slash-Commands beyond TeraOne's own commands. If you want your own commands, you need a separate bot.

Token security

Treat the bot token like a password. Do not store it in public repositories or Discord messages.

On token leak: (1) Discord Developer Portal → your application → Bot → Reset Token. (2) Enter the new token in the TeraOne dashboard. (3) Check whether any unknown actions are visible under the bot.

Troubleshooting

Status stays "Offline": Check: is the token copied exactly (no leading/trailing whitespace)? Are all 3 Privileged Intents enabled in the Developer Portal? Does the bot have Administrator permission on the server?
"Invalid Token" error in the dashboard: Go to the Developer Portal → Reset Token → copy the new token → replace it in the dashboard. Old tokens become invalid immediately after a reset.
Slash-Commands do not appear in Discord: Discord can take up to 1 hour for global command registration after the bot starts. Also check that the bot was invited with the applications.commands scope.
Leveling grants no XP: MESSAGE CONTENT INTENT is probably missing. In the Developer Portal → Bot → Privileged Intents → Message Content → ON.

Frequently asked questions

Can I use the same custom bot token for multiple Discord servers?: No. Each Discord server in TeraOne has its own custom bot slot. You need a separate Discord application for each server.
What happens to the default TeraOne bot when I enable a custom bot?: TeraOne steps back: the custom bot takes over all functions on your server. The default TeraOne bot remains on the server but is inactive for your guild.
How many Slash-Commands does TeraOne register for the custom bot?: TeraOne registers the same Slash-Commands as with the default bot: /rank, /leaderboard, /streak, /ban, /kick, /mute, etc. Additional custom commands are not possible.