How to Build and Run a Rust Discord Community With YourBot

TH The YourBot Team 2026-09-22 · 27 min read
How to Build and Run a Rust Discord Community With YourBot

Updated September 2026

A strong Rust Discord should do more than provide one #lfg channel. Rust communities revolve around servers, wipes, regions, group rules, clans, base-building, raiding, monuments, events, moderation, and server-specific expectations. A player looking for a monthly vanilla server has a very different goal from someone looking for a weekly 2x modded server, a PvE community, or Rust Console Edition.

That means the Discord should identify the server and play style before it tries to organize the players.

YourBot can build that foundation with Start Your Server, then run recurring community workflows through its ten built-in services.

This guide uses a fictional PC Rust Community server as the main example, while also explaining how Rust Console Edition differs so the two ecosystems are not accidentally mixed.

Editorial disclosure: This guide is published by YourBot.gg. Rust facts are based on current Facepunch, official Rust Wiki, Steam, and Rust Console Edition documentation. YourBot-specific behavior is based on current product behavior and read-only repository review. Rust changes every month, so server rules, progression, wipe behavior, clans, monuments, game modes, and server tooling should be rechecked after major updates.

First: Understand the Different Kinds of Rust Communities

“Rust server” can mean several different things.

Before creating Discord roles or LFG templates, identify what the community actually runs.

Facepunch / official-style Rust

Rust’s Steam version is developed and published by Facepunch Studios.

The official PC ecosystem includes the survival game most players mean when they simply say Rust.

Steam App ID:

252490

The game is built around:

Community-hosted servers

Rust has a mature dedicated-server ecosystem.

A community can operate its own server and control things such as:

The official Rust Wiki documents the dedicated-server configuration process, server.cfg, query ports, RCON, server identity, wipe timers, and server-browser tags.

This is where Discord becomes operational infrastructure rather than only a social chat.

Modded servers

Rust’s server browser supports explicit modded tagging, including current tags for frameworks such as:

A modded server may change:

Do not advertise a modded server as “vanilla” simply because its map and weapons look normal.

PvE, Softcore, roleplay, training, and other server styles

Facepunch’s current server-browser tag system supports categories including:

That matters for Discord onboarding.

A member joining a PvE server should not have to discover in #general that the community’s LFG posts assume unrestricted PvP.

Rust Console Edition

Rust Console Edition is a separate product and server ecosystem.

Double Eleven describes it as a version based on Rust but developed as a separate console experience with its own roadmap.

As of September 2026, the current New Gen Rust Console Edition is available on:

It has its own:

Do not tell a PC Rust player to join a Rust Console Edition server or vice versa.

For a mixed franchise Discord, create a clear:

split before LFG.

Wipes Are the Center of Rust Community Operations

Rust is unusual because the server lifecycle matters almost as much as the game itself.

PC monthly update cadence

Facepunch says Rust has guaranteed content updates on the first Thursday of every month.

The official wipe-timer documentation uses that cadence as the default baseline for monthly servers.

Current supported browser wipe tags include:

The default wipe-timer examples are aligned around Thursday schedules.

A community server may configure its own supported wipe schedule, but the Discord should always state the actual server policy.

Map wipe and Blueprint wipe are not the same thing

Do not write:

“Everything always wipes every month.”

Rust distinguishes map/server-state wipes from Blueprint progression.

Facepunch has historically forced Blueprint wipes when progression changes required them, and in late 2025 explicitly experimented with Blueprint wipes again.

A server’s current wipe message should say:

Map: Wiped
Blueprints: Kept

or:

Map: Wiped
Blueprints: Wiped

based on the actual server.

Do not make members guess.

Console wipes are different

Rust Console Edition’s current FAQ documents:

That is another reason not to combine PC and console wipe announcements.

Current Rust Context in September 2026

Rust changes unusually fast.

The current September PC update is Breach and Clear, released September 3, 2026.

Current 2026 additions have included:

The September update specifically added upkeep group scaling, while the July Common Ground update introduced Rust’s new Clan System.

Those are important current mechanics.

They should not become permanent Discord architecture.

Teams and Clans Are Now Different Concepts

This is especially important in 2026.

Rust has had the Team system for years.

Teams provide features such as:

The July 2026 Clan System adds a more advanced social layer.

Facepunch describes Clans as an advanced version of teams with:

That means a Discord should distinguish:

They are not automatically synchronized.

A Discord @Clan Member role does not add someone to a Rust Clan.

The Community We Will Build

This guide uses a fictional PC Rust community called Scrapline [SCRAP].

Scrapline has around 300 Discord members and operates:

The Discord also allows general Rust discussion, but the main operational workflows are built around the Scrapline server.

Console players may join the Discord socially, but they are clearly separated from PC server LFG.

YourBot Services We Will Use

YourBot service Rust use
Welcome PC/console split, region, play-style, clan/new-player interests
Sentinel Scam links, cheat/RMT ads, harassment, invite spam, raid protection
Tickets Player reports, ban appeals, staff applications, server support
Beacon Events Wipe-night events, monument runs, training, community events
Group Finder Roam groups, monument runs, farming/building groups, new-player teams
Join-to-Create Voice Temporary team, roam, monument, building, and clan rooms
Announcements Wipe schedules, maintenance, server events, rule reminders
Social Feeds Built-in Rust publisher announcements
Analytics Discord participation, retention, voice use, channel health
Giveaways Optional legitimate community prizes

Step 1: Build the Foundation With Start Your Server

Start Your Server can create or reorganize channels, roles, permission overwrites, starter content, and supported YourBot service settings.

For an existing Rust Discord, make the first build add-only.

Do not delete current server-information, LFG, or moderation channels until staff have tested the replacement.

Copy-ready Start Your Server prompt

Create or reorganize this Discord server for a 300-member Rust community
called Scrapline.

Scrapline operates a PC Rust Community server.

The server is:
- North America
- monthly wipe
- vanilla-style
- clan friendly
- community moderated

Create onboarding with:
- welcome
- rules
- how-to-connect
- wipe-information
- verification
- PC / Console Edition role selection
- region roles
- play-style interests
- notification roles

Platform / ecosystem roles:
PC Rust
Rust Console Edition

Play-style interests:
Solo
Duo / Small Group
Clan
Builder
Farmer / Gatherer
Roam / PvP
Monuments
Electricity / Industrial
New Player
Mentor

Notification roles:
Wipe Alerts
Server Status
Event Alerts
Patch Notes

Do not imply Discord roles automatically change in-game Rust Teams,
Clans, Tool Cupboard authorization, server permissions, or whitelists.

Create public areas for:
server information, rules, wipe schedule, how to connect, general chat,
new-player help, clans, building, monuments, electricity/industrial,
PvP/roams, LFG, events, clips, and official Rust updates.

Create private staff areas for:
player reports, ban appeals, staff applications, server incidents,
event planning, and moderation logs.

Configure Welcome, Tickets, Sentinel, Beacon Events, Group Finder,
Join-to-Create Voice, Analytics, Announcements, Giveaways, and Social Feeds.

Use Join-to-Create Voice for temporary roam, monument, farm, build,
and event groups.

Do not create permanent channels for every monument, weapon, vehicle,
blueprint, monthly update, or current meta.

If this Discord already exists, do not delete or rename live channels
during the first build. Stage the replacement beside them for testing.

Suggested channel structure

☢️ START HERE
├── #welcome
├── #rules
├── #how-to-connect
├── #wipe-info
├── #verify
└── #choose-interests

📡 SCRAPLINE SERVER
├── #announcements
├── #server-status
├── #wipe-schedule
├── #official-updates
└── #community-events

💬 COMMUNITY
├── #general
├── #new-player-help
├── #clips-and-raids
├── #base-design
├── #electricity-and-industrial
└── #off-topic

🗺️ ISLAND
├── #monuments
├── #pvp-and-roams
├── #farming-and-resources
├── #clans
└── #trading-and-shops

🔎 PLAY TOGETHER
├── #group-listings
├── #new-player-groups
├── #monument-runs
└── #event-signups

🎙️ VOICE
├── Outpost
├── Event Command
└── ➕ Create a Team Room

🛡️ STAFF
├── #staff-chat
├── #player-reports
├── #ban-appeals
├── #server-incidents
├── #event-planning
├── #mod-log
└── Staff Voice

Suggested Discord roles

Access and staff

Ecosystem

Play style

Notifications

Do not make a Discord @Clan role equal to in-game Rust Clan membership.

Step 2: Make Welcome Server-Aware

Open Plugins → Welcome.

A Rust newcomer needs answers before they need channels.

Ask:

  1. PC Rust or Rust Console Edition?
  2. Which region?
  3. Are they joining Scrapline or only the general community?
  4. Solo, small group, or clan?
  5. What do they want to do?
  6. Which alerts do they want?

Example:

Welcome to Scrapline.

Our primary server is a PC Rust Community server.

Before using LFG:
1. Choose PC Rust or Rust Console Edition.
2. Choose your region.
3. Choose the activities you enjoy.
4. Opt into Wipe Alerts if you want server reset notifications.

Discord roles do not automatically add you to an in-game Team or Clan.

Put the current server facts in one place

Your #how-to-connect post should state:

Server:
Scrapline Monthly

Platform:
PC Rust

Region:
North America

Style:
Community / Vanilla-style

Wipe:
Monthly

Blueprint policy:
[Current policy]

Server rules:
#rules

Player reports:
Use the Player Report ticket

Do not scatter connection details across months of chat.

Step 3: Treat Wipe Information Like an Operations Page

Rust members constantly ask:

When is wipe?

Create one authoritative post.

Example:

**Scrapline Wipe Information**

Schedule:
Monthly

Next Map Wipe:
[Discord timestamp]

Blueprints:
Kept / Wiped

Map:
Procedural

Server update window:
[estimate]

If Facepunch changes the forced wipe or update timing, staff will update this post.

Why Discord timestamps matter

Facepunch’s default wipe tooling uses explicit timezones.

Discord timestamps let members see the event in their local time.

That is better than:

“wipe at 2”

with no timezone.

Do not promise exact update completion time

Monthly Rust patches can require:

Announce the planned window and then post when the server is actually ready.

Step 4: Use Sentinel for Rust-Specific Community Risks

Rust communities are exposed to:

Use Sentinel to help manage the Discord layer.

Rules worth testing

Start aggressive rules in observation or dry-run mode where practical.

Server enforcement and Discord enforcement are separate

A Discord ban does not automatically:

Unless you deliberately build a supported integration, staff must handle those systems separately.

Step 5: Use Tickets for Server Administration

A community-owned Rust server benefits heavily from structured private intake.

Create panels for:

Player report

Ask:

Steam profile / player name
Approximate date and time
What happened?
Relevant players
Evidence / clip link
Server:
Any additional context?

Do not promise a ban.

Ban appeal

Ask:

Steam identity used on the server
Approximate action date
Reason shown
What happened?
Why should staff reconsider?

Keep appeals private.

Exploit report

Rust changes monthly.

If someone finds a server-specific exploit, route it privately instead of letting the Discord become an instruction manual.

Step 6: Use Beacon for Scheduled Rust Activity

Beacon works well for events where attendance matters.

Examples:

Example: Wipe Day Launch

Title: Scrapline Wipe Day
Signup:
- Playing at launch
- Joining later
- New Player
- Mentor

Do not use Beacon attendance as a server-slot reservation unless your community actually enforces that.

Example: Monument Workshop

Title: Monument Fundamentals
Signup:
- Learning
- Mentor
- Experienced Helper

Use the description for the current monument.

Do not build a permanent Beacon preset for every monument.

Example: Building Workshop

Title: Base Building Basics
Signup:
- Learning
- Builder
- Observer

This is a useful low-risk community event for new players.

Step 7: Build Rust Templates in Group Finder

YourBot’s current Group Finder auto-detection table does not include Rust.

Create templates manually.

That is useful because Rust groups are activity-based rather than MMO-role based.

Template 1: Roam / PvP

Example:

Server: Scrapline Monthly
Activity: Roam
Current: 2 players
Need: 1–2
Experience: Any
Voice: Required

Template 2: Monument Run

Server: Scrapline Monthly
Monument: Oil Rig
Current Group:
Need:
Experience: Learning / Experienced
Voice:

Do not hard-code a universal group size.

Server rules, team limits, and community policies may differ.

Template 3: Farming / Resource Run

Activity: Farming
Goal: Stone / Metal / Wood
Current:
Need:
Voice: Optional

Template 4: Building Group

Useful for:

Example:

Activity: Base Build
Need: Builder / Farmer / Electricity
Server:
Start Time:

These are community contribution labels, not game classes.

Template 5: New Player Group

Title: New Players Welcome
Activity: Learning
Server: Scrapline Monthly
Goal: Learn spawn, tools, building, TC, bags, workbenches, monuments
Voice: Optional

Rust’s Tutorial Island already covers many fundamentals on compatible servers.

The Discord mentor program should complement it, not pretend Facepunch offers no tutorial.

Template 6: Console Edition

If Scrapline’s Discord also supports console players, create a completely separate game label:

Game: Rust Console Edition
Server:
Region:
Wipe:
Players Needed:

Do not merge PC Rust and Console Edition groups.

Step 8: Use Join-to-Create Voice for Temporary Teams

Static channels such as:

become clutter quickly.

Use Join-to-Create Voice.

Recommended:

Members can rename rooms:

Rust already has team/clan chat

Discord voice complements:

It does not need to replace them.

Step 9: Use Announcements for Wipes, Maintenance, and Events

Start Your Server can enable Announcements, but schedules are created manually.

Weekly community message

**Scrapline — This Week**

Tuesday: New Player Workshop
Thursday: Monument Night
Saturday: Community Event

Next wipe:
[Discord timestamp]

Use #group-listings for groups forming now.

Wipe-day notice

**Wipe Day**

Map: Wiping
Blueprints: Kept
Expected maintenance start: [timestamp]

We will post again when the server is ready.

Update notice

Facepunch has guaranteed monthly content updates on the first Thursday.

Do not schedule a hard “server online” time before you know the update is complete.

Step 10: Use the Built-In Rust Social Feed

YourBot already includes Rust in its curated Social Feeds catalog.

The current entry uses:

That means Scrapline can use the one-click game catalog rather than entering the Steam ID manually.

Recommended setup

The underlying Steam News source:

Use it for:

Important limitation

Facepunch’s own devblog can contain details before or beyond a Steam announcement.

For critical server-owner decisions, read the actual Facepunch update.

Social Feeds is an awareness tool—not a substitute for admin review.

Step 11: Understand Rust’s Current Server Browser Before Writing Rules

Facepunch’s current server-browser tagging system is more expressive than many old Rust guides suggest.

It supports wipe tags:

It also supports server-style tags such as:

Your Discord’s #how-to-connect post should match the actual server listing.

If the in-game server says:

Weekly / Modded / 2x

do not call it:

Monthly vanilla

on Discord.

Step 12: The 2026 Clan System Changes Clan Discords

Rust’s July 2026 Clan System is relevant to Discord communities because it creates an in-game organization layer beyond traditional Teams.

Facepunch says the system includes:

That means Discord no longer needs to imitate every clan-management function.

Use Discord for:

Use Rust’s Clan System for:

Do not promise automatic synchronization between them.

Step 13: Rust+ Is Useful but Separate From Discord

Rust+ connects to Rust servers through the Companion Server.

Facepunch documents it as a separate server-side companion connection.

For a player community, Rust+ may already handle some game-adjacent alerts and smart-device interactions.

Discord still handles:

Do not make a Discord bot duplicate Rust+ simply because both can send notifications.

Step 14: Analytics Measures Discord Health, Not Rust Performance

YourBot Analytics can help answer:

Exclude:

Analytics does not know

Do not use Discord message count as a Rust skill score.

Step 15: Giveaways and Rust Item Trading Need Clear Boundaries

Rust has Steam inventory items and skins.

Community giveaways can work, but scams are common.

Suitable prizes include:

Never ask a winner for:

YourBot Giveaways can select the Discord winner.

It does not authenticate Steam trades or grant in-game resources.

PC Rust and Rust Console Edition Should Not Share One LFG Pool

This deserves an explicit rule.

Double Eleven says Rust Console Edition is a separate console experience with its own roadmap.

As of September 2026, its current New Gen platforms are:

Its wipe schedule and updates are also separate from PC Rust.

For a mixed Rust franchise community, use:

PC RUST
├── #pc-lfg
├── #pc-wipe-info
└── #pc-updates

RUST CONSOLE EDITION
├── #console-lfg
├── #console-wipe-info
└── #console-updates

If console participation is small, Forums/tags are enough.

The important part is not pretending they are the same server ecosystem.

Vanilla, Modded, Softcore, and PvE Need Different Expectations

A good Rust Discord states the server style before someone joins.

Vanilla-style

Expect normal Rust progression and server behavior.

Modded

Explicitly state:

Softcore

Facepunch’s current Softcore mode includes significant changes.

In 2026 it also gained:

Official documentation says Softcore defaults to a maximum team size of four, though server owners can configure related settings.

Do not copy Softcore expectations into a vanilla server.

PvE

State:

“PvE” can mean different things on different community servers.

Your Discord rules are the source of truth for your specific server.

Server Owners: Do Not Put RCON in Discord

Rust server owners commonly use:

Those credentials are powerful.

Do not paste:

into:

If you later build a real server integration, use secure credential handling and least-privilege access.

Version 1 of the custom plugin below deliberately avoids live RCON.

A Complete First-Week Workflow

Day 1: New member

A player joins.

They:

  1. verify,
  2. choose @PC Rust,
  3. choose @NA,
  4. choose @Small Group,
  5. choose @Monuments,
  6. opt into @Wipe Alerts.

They immediately see the correct server information.

Day 2: Monument group

They create:

Title: Oil Rig
Server: Scrapline Monthly
Current: 2
Need: 1–2
Experience: Learning Friendly
Voice: Preferred

The listing expires after the session.

Day 3: New-player event

A mentor schedules:

Title: Rust Fundamentals
Signup:
- Learning
- Mentor
- Experienced Helper

Beacon handles reminders.

Day 4: Player report

A member reports suspected rule-breaking privately.

Staff review evidence through Tickets.

Day 5: Facepunch update

YourBot posts a Rust publisher announcement in #official-updates.

Staff read the Facepunch devblog before changing server configuration.

Day 6: Clan event

Clan members coordinate through Discord voice while the in-game Clan System handles in-game identity.

Day 7: Staff review

Staff review:

Discord activity is not used as an in-game player rating.

Optional Plugin Builder Project: Wipe & Server Operations Board

The AI Plugin Builder is useful when a community operates its own Rust server and needs a persistent operational record beyond Announcements.

A Wipe & Server Operations Board is a strong fit.

Version 1 should remain manual.

Do not connect it to RCON or a hosting panel until you have a secure, documented integration design.

Copy-ready Plugin Builder prompt

Create a Rust Wipe & Server Operations Board plugin for YourBot.

This is a Discord-side server operations workflow.

Administrators configure:
- Server Admin role
- Moderator role
- public server-information channel
- private operations channel
- Wipe Alerts role
- Server Status role

Each Rust server record stores:
- server display name
- platform:
  PC Rust
  Rust Console Edition
- region
- server style:
  Vanilla
  Softcore
  PvE
  Modded
  Roleplay
  Custom
- browser category / tags
- wipe frequency:
  Weekly
  Biweekly
  Monthly
  Custom
- next planned wipe date/time
- wipe type:
  Map Only
  Map + Blueprints
  Unknown / Pending Facepunch
- map name / seed / size as optional text
- short rules summary
- current staff-maintained status:
  Online
  Wipe Maintenance
  Updating
  Degraded
  Event
  Offline
- current public notice
- private staff note

Add a wipe checklist:
- backup completed
- game update applied
- server configuration reviewed
- map verified
- mods/plugins verified if applicable
- connection tested
- Discord wipe post updated
- LFG reopened
- incident log checked

Allow staff to create a wipe record with:
- wipe date
- wipe type
- previous map
- new map
- public notes
- private staff notes
- completion status

Commands:
- /rust-server
- /rust-wipe
- /rust-next-wipe
- /rust-server-status
- /rust-wipe-checklist

The public server command should show only approved public information.

The private operations view may show staff checklist data.

Do not request or store:
- RCON passwords
- hosting-panel passwords
- SSH credentials
- Steam credentials
- API keys
- private server tokens

Do not connect to RCON, Rust+, the hosting provider, or the Rust server
in version 1.

Do not claim a staff-maintained server status is a live health check.

Store all records per Discord server and keep an audit log for staff changes.

How it complements the built-ins

Use:

The custom plugin fills a Rust server-operations gap instead of rebuilding the existing services.

A Future Rust Server Integration Should Be Separate

Rust does provide server-side tooling.

Facepunch documents:

A future integration could potentially expose carefully chosen information such as:

But that needs a real security design.

Define:

Do not jump directly from “we have RCON” to “let an AI plugin control the server.”

Common Setup Mistakes

Mixing PC and Console Edition LFG

They are separate server ecosystems.

Saying every Rust server wipes the same way

Server schedules vary.

Treating map wipe and Blueprint wipe as identical

They are separate concepts.

Calling a modded server vanilla

Use accurate server tags and rules.

Creating one channel per monument

Use LFG fields and threads.

Treating Discord Clan roles as in-game Clan membership

The systems are separate.

Ignoring Rust’s 2026 Clan System

Discord still matters, but the game now handles more in-game clan identity itself.

Posting RCON credentials in Discord

Never.

Using Discord Analytics as game/server analytics

It is not.

Hard-coding one monthly update’s meta

Rust changes every first Thursday.

Frequently Asked Questions

What is Rust’s current PC platform?

Rust’s main Facepunch edition is available through Steam under App ID 252490.

Is Rust Console Edition the same game/server ecosystem?

No. Double Eleven describes Rust Console Edition as a separate console experience with its own development roadmap and servers.

What platforms currently support the New Gen Rust Console Edition?

PlayStation 5 and Xbox Series X|S.

How often does Rust update?

Facepunch says Rust receives guaranteed monthly content updates on the first Thursday of every month.

Do all servers wipe monthly?

No.

The Rust server browser supports monthly, biweekly, and weekly wipe tags, and community owners can operate different schedules.

Does a map wipe always wipe Blueprints?

No. Map/server-state and Blueprint wipes are separate.

Does Rust have clans?

Yes. Facepunch introduced a more advanced Clan System in July 2026 with roles/permissions, clan chat, MOTD/announcements, Clan Table management, and in-game clan identity.

Does Rust support modded servers?

Yes. The official server-browser tag system includes Modded, Oxide, and Carbon tags, among others.

Does YourBot Group Finder automatically detect Rust?

Not in the currently inspected automatic game-keyword list. Create Rust templates manually.

Does YourBot have a Rust update feed?

Yes. Rust is already in the curated Social Feeds catalog with Steam App ID 252490.

How often does the feed check?

The inspected Steam source defaults to a 900-second polling interval.

Can YourBot control my Rust server?

Not through the built-in Discord services described here.

The proposed Wipe & Server Operations Board is intentionally manual and does not use RCON.

Can YourBot verify kills, clan membership, or blueprint progress?

Not through the built-in services described here.

Final Verdict

Rust is one of the strongest fits for a structured Discord because the community exists around the server lifecycle as much as the game itself.

A modern Rust Discord may need to manage:

Use Start Your Server to build a permanent foundation around:

Then give each YourBot service one clear responsibility:

Use the Plugin Builder when the community needs a persistent operational workflow such as a Wipe & Server Operations Board.

Discord can organize the community. Rust remains the source of truth for the world, clans, blueprints, bases, server state, and survival.

← Back to the blog
2026-09-22 ·25 min How to Build and Run a Diablo IV Discord Community With YourBot Build a Diablo IV Discord with YourBot: Seasonal and Eternal LFG, Hardcore and SSF support, clan applications, boss runs, events, and game updates. Read more → 2026-09-21 ·25 min How to Build and Run a Hell Let Loose: Vietnam Clan Discord Server With YourBot Build a Hell Let Loose: Vietnam Discord with YourBot: clan recruitment, organized operations, squad LFG, temporary voice, official updates, and custom training workflows. Read more → 2026-09-21 ·25 min How to Build and Run a VALORANT Discord Community With YourBot Build a VALORANT Discord with YourBot: PC and console LFG, ranked stacks, Premier teams, coaching, patch notes, events, and custom team workflows. Read more → 2026-09-21 ·24 min How to Build and Run a Counter-Strike 2 Discord Community With YourBot Build a Counter-Strike 2 Discord with YourBot: Premier and Competitive LFG, Wingman, scrims, community servers, patch updates, events, and custom map-veto workflows. Read more →

Find your next plugin

Browse the YourBot marketplace and add exactly the features your server needs.

Browse the marketplace →