Docs

How it works

Usely is hosted, so there is nothing to install on your game server. You give us your server's WebRCON details once, and we hold an outbound connection to it. That connection powers three things:

• The web panel — your browser view of players, kits, bans, and the RCON console.
• The Discord bot — population channels, kill feeds, and staff sign-in.
• Your workspace — the container for your servers, staff, and billing, reachable at your own address on usely.dev.

No plugins, no mods, no uploads. If you change hosts, you only update the connection details.

Create your workspace

Usely is buy-first: you pick a plan before the workspace exists, which keeps signup to a single step.

1. Choose a plan on the pricing page and pay.
2. We email you a setup link. It's valid for seven days.
3. Open the link and pick your panel address — the subdomain your panel lives on, like astral.usely.dev. Lowercase letters, numbers, and hyphens; some names are reserved.
4. Set your owner password. You'll sign in with your email address and this password from now on.

Connect a server

Each server is one WebRCON connection. From the panel, add a server and provide:

Host

The IP address or hostname your host exposes WebRCON on.

Port

The WebRCON port — usually different from the game port players connect to.

Password

Your RCON password. It's encrypted before it's stored, and it's never shown back to you in full.

Your host's control panel is where all three values live, often under a remote console, RCON, or server settings section. If you can't find them, your host's support can tell you which port WebRCON is on.

Once saved, the connection comes up on its own and the panel starts showing live data. If it can't connect, the server shows as offline and Usely keeps retrying — you don't need to reconnect by hand after a restart or wipe.

Players and moderation

The players view lists everyone currently online, pulled live from the server rather than a cached snapshot. From there you can:

• Kick a player, with a reason they'll see.
• Ban a player, which adds them to your ban list.
• Review and unban from the ban list, including bans placed before you started using Usely.
• Broadcast a message to everyone on the server.
• See which players have linked Discord accounts.

RCON console

The console runs any command your server accepts and shows the raw response, for the cases the panel doesn't cover. Access to it is a separate permission, so you can give staff moderation tools without giving them full server control.

Kits

A kit is a named set of items players can claim in-game. To build one, select items from the Rust Console item list and save the kit — there's no JSON to write and no file to upload.

Players claim kits through the quick chat phrases you configure, so the flow works with a controller and needs no typing. Kits are per-workspace, so a kit you build is available on whichever of your servers you assign it to.

Discord bot

The bot is included with every plan. Invite it to your server from the panel, and give it permission to read and post in the channels you want it to manage.

What it handles:

• Population channels — a channel name that updates with your live player count, so members can see how busy the server is without launching the game.
• Kill feeds — in-game kills posted to a channel.
• Staff sign-in — moderators authenticate to the panel with Discord instead of a password you have to share.

If the bot goes offline, the panel keeps working — they're independent connections.

Staff permissions

You don't create accounts for your staff. Instead, you map Discord roles to permissions in your workspace. Anyone with that role can sign in with Discord and gets exactly what the role allows.

The practical effect: promoting someone is giving them a Discord role, and removing their access is taking it away. Nothing to deprovision, and no shared credentials to rotate when someone leaves.

Permissions are checked on every action, not just at sign-in, so a role that can kick and ban but not use RCON genuinely cannot run RCON commands.

Multiple servers

Basic covers one server. Pro covers two, and Network covers more. Each one is its own WebRCON connection with its own players, bans, and status.

Switch which server you're managing from the panel header. Your kits and staff role mappings belong to the workspace, so you configure them once rather than repeating the setup per server.

If you downgrade to a plan with a lower limit, disconnect the extra servers first.

Billing

Plans are monthly, and payment is handled by Stripe — card details never touch Usely's servers. From the panel you can change plans, update your payment method, download invoices, and cancel.

Upgrades take effect immediately so you can add a server right away. Cancelling stops future charges and your workspace stays available until the end of the period you've paid for.

Troubleshooting

The server shows as offline

Almost always the host, port, or password. Confirm the port is the WebRCON port and not the game port, and re-enter the password if it was changed on the host. If your host rotates IPs, the host value may be stale.

No players are listed but the server is online

An online status with an empty list usually means the server genuinely has nobody on it. If players are in-game and still not showing, the connection may be authenticated but restricted — check that your RCON user has full console access on the host.

The Discord bot is offline or silent

Check that it's still in your Discord and can view and post in the channels you assigned. Population channels also need permission to rename the channel, which is separate from posting.

Staff can't sign in

Confirm the Discord role is mapped in your workspace and that the person actually holds that role. Discord role changes can take a moment to appear.

Something else

Check the FAQ, then get in touch — include your panel address so we can find your workspace.