Documentation

Overview

Usely is a hosted admin panel and Discord bot for Rust Console Edition. You never install plugins or upload files to your game server. Instead you give Usely your host’s WebRCON details once, and we hold an outbound connection that powers:

• The web panel — live players, kits, bans, broadcasts, wipe tools, and a raw RCON console at your own address (for example myserver.usely.dev).
• The Discord bot — killfeeds, join/leave, game events, population and wipe countdown channel names, VIP claims, and staff slash commands.
• Your workspace — billing, staff keys, and one or more WebRCON servers under one plan.

Usely is in public beta. Features ship often. If something breaks, report a bug and include your panel address.

What you need

• A Rust Console Edition server whose host exposes WebRCON (IP or hostname, port, and password). Nitrado and similar hosts show this under remote console / RCON settings.
• A Discord server where you have Manage Server (to invite the bot).
• A card for Stripe checkout (monthly billing).

Get started

Pick a plan, pay, then finish setup from the emailed link.

1. Choose a plan and pay

1. Open Pricing (or Signup) and choose Basic, Pro, or Network.
2. Enter the owner email and continue to Stripe checkout.
3. After payment, we email a Finish setup link. It expires in seven days. You can resend it from the signup page if needed.

2. Finish setup (wizard)

Open the link from the email. You’ll walk through three steps:

Your workspace

• Community / workspace name — shown in the panel.
• Panel address — the subdomain staff will bookmark, like astral.usely.dev. Choose carefully; changing it later means everyone updates bookmarks.
• Owner password — at least 8 characters. This login controls billing and server credentials.

Invite the Discord bot

• Click invite and authorize the bot on your Discord (you need Manage Server).
• Paste your Discord guild ID (Developer Mode → right-click the server → Copy Server ID) and link it.

Connect WebRCON

• Display name — label for this server in the panel header.
• RCON host — IP or hostname only (no http://).
• RCON port — WebRCON port from the host.
• RCON password — stored encrypted; never shown back in full.

Setup tests the connection when you add the server. If it fails, you can still open the panel and fix host/port/password under Workspace → Setup. On Pro/Network you can add more servers there later.

3. First things after setup

1. Confirm the server shows online on Home → Overview.
2. Open Discord → Channels and assign at least Killfeed, Pop status, and Leaderboard if you use those features.
3. Create staff keys under Workspace → Staff keys for moderators.
4. Optionally set a wipe countdown under Server → Wipe.

Signing in

Always use your panel URL (yourslug.usely.dev), not the marketing site.

Owner

Email + password under Owner on the login screen. Use Forgot password? for a one-hour reset link. Owners manage billing, WebRCON servers, Discord guild link, staff keys, and audit logs.

Staff

Paste the full access key (ask_…) under Staff on the login screen. Keys are permission-scoped and never include billing or key management.

The panel

The left nav groups everything by job. Switch the active game server from the header when you have more than one.

Advanced tools: RCON (raw console), Warps, and Logs (owner audit). Access to each area is controlled by staff key permissions.

WebRCON

Each connected server is one WebRCON endpoint. Usely keeps the socket alive, reconnects after restarts, and uses it for player lists, kicks/bans, kits, broadcasts, stats, and the console.

• Add or remove servers under Workspace → Setup (within your plan limit).
• Mark a default server for the header switcher.
• Private / local hosts are rejected — Usely must reach a public WebRCON endpoint.
• Credentials are encrypted at rest. Staff keys never expose the password.

If the connection drops, the panel shows the server offline and Usely retries. You don’t need to reconnect by hand after a wipe or host restart once the details are correct.

Discord bot

Every plan includes the bot. Invite or re-invite it from setup or Workspace → Setup. The panel keeps working if Discord is down — feeds simply pause.

Typical staff and community slash commands (enable/disable under Discord → Slash cmds):

• Info: /server, /players, /stats, /leaderboard
• Linking: /link start, /link status, /link unlink (staff can force-link from the panel or Discord)
• Teleports: /home, /warp, /tpr / /tpa / /tpd (need a linked IGN)
• Staff: /rcon, /kit, /player, /bans, moderation, tickets, giveaways, polls, announces

After inviting, map channels under Discord → Channels or the bot has nowhere useful to post.

Channels & feeds

Open Discord in the panel. Only set the channels you actually use.

Channels

Pick a channel from the dropdown or paste a channel ID. Save when you’re done.

Status displays

Under Discord → Status, control how pop and wipe channel names look (online/max format, queue label, offline label, wipe prefixes like countdown / TBA / Wiped).

Feeds

Under Discord → Feeds, turn individual feeds on or off and tune killfeed options (compact PvP, NPC, animal, traps, natural deaths, suicides, streak callouts).

VIP

Under Discord → VIP: Discord role, kit id (often vipkit), claim phrase (default quick chat like i need water; use | for aliases), post-wipe lockout hours, and once-per-wipe limits. Players need the role and a linked IGN to claim.

Kits

Open Kits. There are two kinds:

In-game kits (server)

Pulled live from the game host via RCON (kit list). Resync when you change kits on the server. Give them from the kits page or Actions.

Panel kit bundles

Built in Usely from the Rust Console Edition item catalog:

1. Click Create kit.
2. Set Kit ID, display name, and cooldown (minutes).
3. Optional Claim phrase — what players must say in quick chat (aliases with |).
4. Optional Discord role — only members with that role (and a linked IGN) can claim.
5. Add items from the catalog (or a custom shortname) and Save kit.

Kits are available on every server in the workspace. Staff can still Give a kit even when claims are locked.

Kit locks

Use locks on wipe day to pause quick-chat claims for boom kits (or any claimable panel kits):

1. Select which kits to pause.
2. Choose duration: 2 / 6 / 12 / 24 hours, custom hours, or until you end it.
3. Start lock / End lock now.

Staff can also manage locks from Discord with /kit lock, /kit unlock, and /kit locks.

Account linking

Linking ties a Discord user to an in-game name so homes, warps, TPR, VIP claims, and role-gated kits work.

• Player: join the server, then run /link start <IGN> in Discord while that IGN is online.
• Check or remove: /link status, /link unlink.
• Staff: Players → Links in the panel, or force-link from Discord staff commands.

Staff keys

Open Workspace → Staff keys (owner only).

1. Pick a preset (Helper, Moderator, or Admin) or toggle permission chips.
2. Give the key a label (for example Mod — Alex).
3. Generate access key — copy the ask_… secret immediately; it’s shown once.
4. Staff open your panel URL → paste the key under Staff on the login screen.

Disable or revoke anytime. Permissions are checked on every action, not only at login. Keys never unlock billing, staff-key management, or owner audit logs.

Toggle permission chips when you create or edit a key — the panel lists every available permission.

Wipe day

Open Server → Wipe.

Countdown

Set the wipe datetime and save. Usely renames your wipe-status Discord channel and can post reminders to the Wipes channel (falls back to Announcements) at 24 hours, 1 hour, and wipe time.

Run wipe

This resets Usely-tracked wipe data. It does not wipe the Nitrado / host map — you still do that in the host panel.

Checklist steps (all on by default): stats & leaderboard, homes, TP cooldowns, kit cooldowns, VIP kit claims, kill streaks, group alerts, republish boards, clear countdown, announce.

• Run wipe now — needs the Wipe reset permission.
• Auto-run at countdown — runs the checklist when the wipe time hits zero.

Also consider starting a kit lock before wipe so boom kits aren’t claimed early.

Plans & billing

Every plan includes the panel and Discord bot. Kits and staff keys are shared across servers in the workspace. Switch the active server from the panel header.

Manage plan, payment method, invoices, and cancel from Workspace → Billing (Stripe Customer Portal). Upgrades apply immediately. Cancel stops future charges; access continues until the end of the period you paid for. If you downgrade below your current server count, disconnect the extras first.

Troubleshooting

Server shows offline

Almost always host, port, or password. Confirm the port is WebRCON (not the game port). Re-enter the password if the host rotated it. If the host changed IPs, update the host field under Workspace → Setup.

Online but nobody in the player list

Usually the server is empty. If players are in-game, the RCON user may lack full console access — check permissions on the host.

Discord bot silent

Confirm the bot is still in the guild and can view, post, and (for pop/wipe) rename the channels you assigned. Re-invite from Workspace → Setup if it was kicked.

Staff can’t sign in

They must open yourslug.usely.dev, not www.usely.dev. Confirm the key is enabled and they paste the full ask_… string.

Setup email expired

Use Resend setup email on the signup page with the same owner email.

Role-gated or VIP kit won’t claim

Player must be online, linked (/link start), have the required Discord role, and not be blocked by kit lock / wipe lockout / cooldown.

Something else

Check the FAQ, then contact us with your panel address and what you were doing. Support: support@inbound.usely.dev.