Switching from another bot
Bring your existing bans to Modhelm. Take them over from Roblox, import a CSV or JSON file from your old admin system, and what happens with Bloxlink or RoVer links.
3 min read
When you move to Modhelm you don't start from zero. Your bans come along, so priors, unban requests and cross-game bans work from the first day. You import them once under Settings > Import bans in the dashboard. Only admins of your server can do this.
Two ways to import
| Way | Use it when | What happens in Roblox |
|---|---|---|
| Take over from Roblox | Your bans already live in the Roblox ban list (Open Cloud or the Creator Dashboard) | Nothing. Modhelm only reads them |
| Import a file | Your bans are in an admin system, a DataStore, a spreadsheet or a Trello list | Nothing by default. You can switch on that the bans are also set in Roblox |
You can use both, one after the other. A player who already has a ban in force in Modhelm, or was imported before, is skipped.
Take over bans from Roblox
- Connect your games first, each with an API key that can read bans (see Connect a game).
- Open Settings > Import bans. The card Take over bans from Roblox lists your games and whether their key works.
- Click Take over. Modhelm reads the active bans of every game with a working key and saves them as priors.
The import runs in the background, so you can leave the page. Each game shows how many bans were checked and imported. Ended bans are kept as priors that are no longer active, so your team still sees them.
Import a file
Most admin systems (Adonis, HD Admin, your own DataStore, Trello lists) can export their bans. Export them as CSV or JSON and drop the file on the card Import a file. Files can have up to 50,000 rows and 12 MB.
Before anything is saved you see a check: how many rows can be imported, how many are permanent, temporary or warnings, which rows have errors and the first rows of the file. Then you choose which games the bans apply to and start the import.
Columns
Put a header row with these names in the first line. Other columns are ignored.
| Column | Content |
|---|---|
roblox_user_id or username | Who is banned. Usernames are looked up on Roblox first |
type | perm, temp or warn |
duration or expires_at | For example 7d or 12h, or an end date like 2026-12-31 |
reason | The reason the player sees in Roblox, up to 400 characters |
reason_private | A note only your team sees |
moderator, created_at | Who banned and when (optional) |
Without a header row the columns are read as user ID, reason and duration. JSON works as a list of objects with the same names, or as an object with a bans list.
roblox_user_id,type,duration,reason
156,perm,,Exploiting: fly hacks
4815162342,temp,7d,Spamming the chatAlso ban in Roblox
The switch Also ban in Roblox is off by default: the bans are only stored as priors. Switch it on when your old system kept the bans outside of Roblox and you want them to take effect in your game now. Modhelm then bans every player in Roblox, about 8 per second per game, and you can watch the progress.
Bloxlink and RoVer
Accounts that members linked with Bloxlink or RoVer can't be imported. Their APIs only answer for one member at a time and have no export. Members verify once with Modhelm instead. The verification works across the whole network, so a member who verified for another server is already known on yours. See Verification.
After the import
- Check Bans in the dashboard: the imported bans are there with their reason and end date.
- Turn on the appeal rules you want (see Unban requests). Imported bans count like any other ban.
- Remove the ban commands of your old bot from your server, so your team only uses one system.