Anti-Alt
Automatic protection against alt accounts and ban evasion
Alt accounts are secondary accounts typically used to evade an active ban or to remain anonymous on the server. The Anti-Alt module automatically analyses every new join and responds based on the risk level: from a silent log entry, through quarantine with verification, up to an immediate kick or ban.
How detection works
On every join, TeraOne checks several attributes of the new account and calculates an internal risk score. Depending on the score, a configured action is taken. The exact signals and their weighting are deliberately not documented — this way they cannot be systematically circumvented.
Actions by risk score
You configure thresholds with corresponding actions. The default configuration uses three tiers:
| Action | What happens |
|---|---|
log | Silent notification in the mod channel, no intervention |
quarantine | User receives the quarantine role, write access restricted |
quarantine_then_verify | Quarantine + verification challenge is sent |
timeout | Discord timeout for a configured duration |
kick | User is immediately removed from the server |
ban | User is immediately banned (temporary or permanent) |
Verification flow
In quarantine_then_verify mode, verification works as follows:
- User joins — score exceeds threshold → receives quarantine role
- Bot sends verification message (channel, DM, or both)
- User clicks the "I am not a bot" button
- Optional: time gate — user must wait N seconds before the button becomes clickable
- Optional: captcha — user must solve a captcha (up to 3 attempts, configurable)
- Optional: mod approval — a Moderator must manually confirm
- On success: quarantine role is removed, user is fully active on the server
- On too many failed attempts: kick
Setting up the quarantine role
The quarantine role itself has no special behaviour — you restrict it through channel permissions. Recommended configuration:
- In all regular channels: send messages = DENY for the quarantine role
- In the quarantine channel: read messages = ALLOW, send messages = DENY
- Optional: make all other channels completely invisible to the role
Raid shield
The raid shield detects mass joins: if N users join within X seconds (default: 10 joins in 60 seconds), a lockdown is triggered. All recently joined users are automatically quarantined and no new joins are let through unchecked.
Default lockdown duration: 30 minutes. After that, the shield lifts the lockdown automatically.
Moderator notifications
Every flagged case appears as an Embed in the configured mod channel. The Embed shows: username, account age, which signals triggered, current status, and three action buttons: Approve (release user), Remove (kick), and Ban.
Frequently asked questions
- Can I disable or adjust the detection signals?
- In the dashboard you can toggle the available detectors individually (account age, no avatar, name blacklist, cross-server bans, etc.). The exact score values remain system-managed.
- What happens if Anti-Alt blocks a legitimate new user?
- In quarantine_then_verify mode the user can complete verification and then becomes fully active. If that fails, a Moderator can manually approve them via the mod channel.
- Does Anti-Alt work if the user is on a VPN?
- Anti-Alt evaluates account attributes, not connection attributes. A VPN alone does not trigger a flag.
- How long is case data stored?
- All cases remain permanently visible in the dashboard — for audit purposes and to identify patterns.