Loading your account…
ServerHelper

Ban one account and every alt it owns goes with it.

Server Helper links accounts by the IP they connect from. Ban a rule-breaker and every alt they own is blocked too, and it flags accounts being shared between people while it's at it.

The ban actually sticks

Ban a rule-breaker and their known alts go with them, and the address itself is closed, so the brand new account they make next has nothing to walk back in on.

Checked before they land

Every join is decided against your rules in the moment, without log scraping, polling, or anything to wait on.

VPNs and proxies turned away

Commercial VPNs, rented boxes and residential-proxy networks are recognised and blocked, with a separate list for the players you trust on one.

Run it from Discord

Fourteen slash commands, so your moderators never need the dashboard. Anything showing an address answers privately.

A record of every ban

Who banned who, why, and for how long, written into a channel you choose. Bans made on the dashboard and bans that simply run out land there too.

Nitrado in one click

Import every server with its RCON details found for you, install the mod and write the keys into their configs, then start, stop or restart them from here.

One cluster, one ban list · $15/month or $135/year · cancel any time

Welcome back

Log in to manage your cluster.

Enter the email you signed up with and we'll send a link to choose a new password.

Choose a new password for your account.

Three steps, then it runs itself

Server Helper is a small mod on your servers and a control panel here. The mod carries nothing but an API key: every rule lives on this site, so changing one never means re-cooking or re-uploading anything.

1

Add your servers

On Nitrado, paste an API token and every server is imported with its RCON host, port and password already found for you. On any other host, type them in once.

2

Install the mod

Add it to each server's mod list and give each server its own key. On Nitrado we do both for you, with a preview first and a backup of the config alongside.

3

Play

From then on every connection is checked against your ban list, your address blocks, your VPN rules and your whitelist before the player reaches the map.

Everything, on every server in the cluster

One pool of detections and one ban list shared across every map you run. An alt caught on The Island is known on Ragnarok before they finish loading.

Alt detection

Every join records the account and the address behind it. Accounts sharing an address are grouped for you automatically.

  • Pooled across the whole cluster, not per server
  • Busy addresses flagged for review, never auto-banned
  • Full history per account: every address, network and first/last seen

Bans that hold

Banning the account alone only closes the door you already know about. Blocking the address is what actually ends it.

  • Known alts on that address are banned with them
  • The address is closed, so a fresh account from it is turned away too
  • Addresses several people share are left alone, and you are told why
  • Unbanning reopens everything it closed, unless another ban still needs it

VPN and proxy blocking

Commercial VPNs, cloud and hosting networks, and the residential-proxy services built for exactly this kind of evasion.

  • A separate allow list for players you trust on a VPN. Unrelated to the whitelist.
  • Networks you can classify yourself when our list has not caught up
  • Never flags Starlink, GeForce NOW, Steam or the mobile carriers

Account sharing

Spots one account signing in from unrelated networks, likely a sold or shared login, and scores how confident it is.

  • Counts distinct networks, not just addresses
  • Weighs fast switches differently from a home IP that drifts

Whitelist mode

Only approved accounts can join. One switch for the cluster, with a per-server override when you want one map locked and the rest open.

  • Pre-wipe, without a restart: flip it on to shut the cluster and off to open it. No editing configs and bouncing every server to lock and unlock
  • Anyone already in-game is removed, not just blocked at the door
  • Also good for events and private testing

Live player list

Who is on each server this second, the address they are on, and whether they are already banned or flagged.

  • Kick or ban straight from the row
  • Click any address or account ID to copy it

Discord bot

Your moderators work where they already are. Fourteen slash commands covering everything the dashboard does day to day.

  • /online /lookup /lookupip /kick /ban /unban
  • /ipban /ipunban /ipbans for addresses
  • /whitelist /vpn /help and settings
  • Gated on Manage Server, or a moderator role you nominate
  • Anything showing an address replies privately, so addresses stay out of channels

Audit log

Point it at a channel and every consequential action is written there: who did it, where, and why. The answer to “who banned my mate?” stops being a guess.

  • Bans, unbans, blocked addresses, whitelist changes and expiries
  • Names the moderator, the channel, the reason and the length
  • Actions taken on the dashboard are logged the same way
  • So is a temporary ban ending on its own at four in the morning

Nitrado control

If you host with Nitrado, the tedious parts are done for you.

  • Import every server with RCON discovered automatically, including the port people usually get wrong
  • Install the mod and write API keys into each config, with every change shown first and a backup kept
  • Start, stop and restart from the dashboard, with live status

Set once, change any time

The mod's config file holds a single API key. Kick messages, the ban list, the whitelist and every rule live here.

  • Changes take effect on the very next join: nothing to poll or re-upload
  • No re-cooking the mod to change a setting
  • RCON passwords are encrypted and never shown again

One plan. Every server you run.

No per-server pricing and no player caps: a cluster is a cluster. Cancel whenever; your servers keep running, enforcement just stops.

$15
per month
$135save $45
per year

Both plans include every feature above, unlimited servers in your cluster, and the Discord bot. Create an account first. You can add your servers and look around before you subscribe.

ServerHelper
…
Server Helper isn't active on this account.
Manage mods & INI presets

Apply settings to selected Nitrado servers or your whole cluster. Preview first, then apply. Restart when you’re ready.

Servers

Load a server’s configured IDs or start with a saved preset.

Separate IDs with commas or new lines. Applying replaces the complete mod list on every selected server, in this order. An empty list removes all mods. Preview each server before applying.

Add/update and remove change only the keys you name. Replace full file uses the complete editor contents, including comments and repeated keys. Each target keeps its unique Server Helper API key. To remove a key, enter Key= (the value is ignored). Each file is backed up and checked after writing. Full-file presets can include passwords and other server-specific settings; review these before applying to other servers.

Start here: add a server to your cluster

Nothing else works until at least one server is linked. Every server you add shares one pool of detections and one ban list. RCON details are optional. Add them and the Ban button can kick players straight from your servers. The password is encrypted and never shown again.

Where do I find my RCON host, port and password?

On Nitrado you don't need to: use the import card below and it fills all three in for you.

On any other host, or by hand:

  • Host: the same IP players connect to.
  • Port: the RCON port, not the game or query port. Your host's control panel lists it; it is often the game port + 2.
  • Password: ARK's ServerAdminPassword, from your GameUserSettings.ini under [ServerSettings]. It is the same password you use for in-game admin commands.

RCON also needs RCONEnabled=True in that file. Once saved, hit Test RCON: it says plainly whether it connected, and what was wrong if it didn't. RCON is optional: without it the join check still turns players away, you just lose the instant kick for someone already in-game.

On Nitrado? Connect your account

One token covers everything on this page: it imports your servers with their host, RCON port and RCON password already filled in, writes each API key into the right GameUserSettings.ini, and powers servers up and down. Click Find my servers to check and save your token, encrypted on your account.

Where do I get a Nitrado API token?
  1. Sign in at server.nitrado.net.
  2. Click your username (top right), then My Account.
  3. Click Developer Portal.
  4. Click Long-life tokens.
  5. Give it a description: Server Helper does fine.
  6. Tick the service scope. That is the only one needed.
  7. Click Create and copy the whole token (around 100 characters).

We use it to read your servers and carry out the configuration changes and power actions you request. Clicking Find my servers saves a valid token automatically, encrypted on your account. You can remove the saved token using Forget it. If you'd rather not use one at all, add each server by hand in the card above instead.

Adds the Server Helper mod to each server's mod list and writes its API key into the config. Shows you every change first. Restart afterwards: both are only read at startup.

Your servers

live means that server has used its key recently. never contacted means it never has. Either the mod isn't installed, or the key in its config doesn't match the one here. Who is playing is read from each server over RCON and updates on its own.

What do I do with the API key?

It is the only thing the mod needs. Open that server's GameUserSettings.ini and add these two lines at the bottom:

[Serverhelper]
ApiKey=ipw_your_key_here

Each server gets its own key from its card below. That is how we know which of your maps someone joined, and it is what lets you set a per-server whitelist override.

The file lives at ShooterGame/Saved/Config/WindowsServer/GameUserSettings.ini. On Nitrado, reach it through Tools, then File Browser. Restart the server afterwards: the key is read at startup.

Everything else, including kick messages, the ban list, and the whitelist, is set here on the website and takes effect on the very next join. You never edit the mod, and you never re-cook it to change a setting.

Announce

Say something to everyone playing, over RCON. A chat line goes into the chat; a banner pops up on every screen for about 10 seconds. One line, up to 300 characters. A banner is sent as the server's Message of the Day, so it also replaces the message new players see when they join.

Kick messages

The wording players see when they're turned away. Set here, not in the mod. The only thing that goes in your server's config file is the API key above, and changes take effect on the very next join.

Discord bot

Run the same commands from your Discord instead of here: who's online, kick, ban, whitelist. Anything that shows a player's IP replies privately, so addresses don't end up pasted in a channel. One Discord server per subscription.

Audit log. Run /serverhelper logchannel #your-channel in Discord and every ban, unban, blocked address and expiry gets written there: who did it, where, and why. Bans made on this page and bans that simply run out land in the same channel, so the log is a record of what happened to the cluster rather than a record of what happened in Discord.

How do I connect my Discord?
  1. Click Invite the bot above and pick your server. You need the Manage Server permission there.
  2. Click Get a link code.
  3. In your Discord, run /link <code>. You need the Manage Server permission, and the code lasts 15 minutes.

Everyone with Manage Server can then use every command. To let your staff kick and ban without handing them Manage Server, run /serverhelper modrole @yourrole in Discord. The commands are hidden from anyone without Manage Server, so to show them to that role open Server Settings → Integrations → Server Helper and add the role under Roles & Members. Run /help any time for the full list.

Your subscription covers one Discord server. To move it somewhere else, unlink the current one first, either here or with /serverhelper unlink.

Adding servers, RCON details and API keys stay on this website on purpose. A chat box is a bad place to type a password, and Discord keeps message history forever.

Update the slash commands owner only

Only needed when the command list itself changes: a new command, or a new option on one. Discord has no page for this, so something has to make the call. The token is used for this one request and never stored. Reset it any time in the developer portal; nothing else uses it, so resetting breaks nothing for anyone already using the bot.

Event mods

early access

Maga Vaults and Maga Dinos announce their drops in Discord. The bot makes a forum channel, a webhook and one post per map, then the mod's section is written into each Nitrado server's config with all of it filled in. Uses the Nitrado token from the card above.

Loading…

Whitelist mode

Allowed accounts

One EOSID per line. Paste as many as you like at once. This list is shared by every server in the cluster.

What is an EOSID, and how do I find someone's?

It is the 32-character Epic account ID that ARK identifies a player by, something like 000278d5475948f7b4c96b11580c3fe1. It stays the same whatever they rename their character to, which is why we key everything on it.

Three ways to get one:

  • Have them join, then copy it from Players online on the Cluster servers tab.
  • Run listplayers over RCON, or cheat listplayers in game: it prints each player's ID.
  • Ask them for their Epic account ID.

Case doesn't matter, and spaces are trimmed.

Always allowed

Your own admin accounts. These are never kicked, not by a ban and not by the whitelist, and they can't be swept up when you ban an alt group.

Per-server override

By default every server follows the cluster switch above. Override one here to lock down a single map, or to keep one open while the rest are closed.

Accounts linked by IP

Across every server in your cluster. Banning any account here bans the whole group on all of your servers.

Banned addresses

Bans the address, not the account. Every account that connects from it is turned away, including one made after the ban. That's the point of it. Anyone already on it is kicked immediately.

Block VPNs and proxies

Every account report tells us which network it came from. Commercial VPN exits and rented servers sit on hosting networks; real players come from home ISPs and mobile carriers. Accounts on a flagged network are kicked unless they are on the list below.

Leave this off until the list below looks right. It is a good signal, not a perfect one. Cloud gaming, some corporate networks and the odd mobile carrier can look like hosting. Everything caught is shown here whether the switch is on or off, so you can see who you would turn away before you turn anyone away.

Allowed to use a VPN

Separate from your join whitelist: this only excuses the VPN. An account here is still subject to bans and to the whitelist like anyone else.

Seen on a VPN or hosting network

Most recent first. Check this before switching enforcement on.

Networks your players come from

We guess whether a network is a VPN from who owns it, and that guess will always be behind: a new provider, or one registered under an unrelated company name, reads as an ordinary home connection. If you can see one is a VPN, say so here. It applies to the joins we already recorded as well as to future ones, so enforcement starts immediately.

Possible account sharing

One account connecting from many unrelated networks, often a shared or sold login. Scored so a player whose home IP simply changes isn't flagged.

Ban a player

Banning also kicks them off every server that has RCON saved, straight away.

Banned accounts

Checked live on every join, so a ban takes effect the next time they try to connect. Nothing to sync. "Push all" additionally writes the list to ARK's own ban list over RCON, which blocks them during the login handshake; useful after adding a server or a wipe.