Rust Role Play — User Guide

Help for players joining a server running Rust Role Play. Last reviewed: 27 October 2026.

Introduction

Rust Role Play adds characters, careers, skills, businesses and social systems to Rust. Gathering, building and survival remain part of the game. Each server chooses its installed plugins, published content, prices and rules.

Use this guide for the shared workflows and in-game Help for your current character's options. Ask staff about local rules and what survives a wipe.

Overview

Create a character, choose a profession, discover work or quests, and build connections. Progress can unlock skills, recipes and opportunities. Core, Persistence and UI supply shared services; Economy supplies currency services; feature plugins add activities.

A listed feature needs its owning plugin and any configured providers. A missing section can mean the module is absent, still loading or has no published content. Visibility does not grant ownership or permission.

Contents

• Getting started
• Everyday controls
• RPCore
• RPPersistence
• RPUI
• RPOnboarding
• RPProfessions
• RPSkills
• RPEconomy
• RPCrafting
• RPBuilding
• RPBots
• RPQuests
• RPFactions
• RPPlaces
• RPBusinesses
• RPTraders
• RPStocks
• RPRelationships
• RPFarming
• RPJustice
• Player actions and services
• Troubleshooting

Getting started

1. Join the server and read its rules. Follow the arrival tracker if one appears.
2. Complete introductory activities. Use /onboarding action to open the current stage's action on servers using the role-play journey.
3. Choose an available profession through the prompt or /professions. Read its eligibility, perks and any fee.
4. Create a character through the arrival prompt or /character. Save a name, background and reason for arriving before attempting paid activities that require a character.
5. Open /help. Review your profile, module sections, command list and journal.
6. Try one available activity: gather for your profession, speak to a quest bot, visit a trader or open the recipe book. Check the result and any receipt.

If no free eligible profession or reachable objective exists, give staff the displayed reason and stage title.

Everyday controls

Type chat commands with the leading slash. The server can restrict commands. Use Help → Commands for its current full list and syntax.

Close overlays to return to normal gameplay controls.

RPCore

Purpose: Character identity and shared gameplay rules.

Open /character to view or create your character. The command form is:

/character create Name | Background | Reason for arriving | Optional note

Character identity can differ from Steam identity. Contacts, employment and other records can belong to the character that created them. Another character does not automatically inherit that access.

Story leads suggest role-play opportunities; a rumor does not automatically accept a quest or award a reward. Government identity tags, where configured, are separate from display names.

RPPersistence

Purpose: Durable storage for framework progress and records.

Normally use the owning plugin's interface. Wait for a success message or terminal receipt before treating a purchase or reward as complete. A loading message, timeout or reconnect is not proof of refund or delivery.

Keep order and transaction IDs for support. World-bound progress follows the server's world identity and wipe policy. Repeatedly clicking a pending action does not make storage finish sooner.

RPUI

Purpose: Shared interface, Help, HUD, profile and private journal.

Open /help and select a module. The profile summarizes progress; journal sections hold personal notes and supported records such as contacts. Module pages reflect published content and current eligibility.

Use /hud and /hud edit for supported panels. Colors and available layouts follow the server's theme. Read a locked option's requirements: seeing it in Help does not mean you own it.

RPOnboarding

Purpose: The new-player journey.

Follow the tracker and its objective counters. Stages can request gathering, crafting, bot interaction, profession selection, character creation or opening a guide. Some objectives match exact skins or custom items.

Use /onboarding hide, /onboarding show and /onboarding action as needed. Servers can use Rust's Tutorial Island instead. Publishing a replacement scenario restarts unfinished journeys on the new version while preserving separate character/profession records. Report unreachable targets with their stage title.

RPProfessions

Purpose: Careers, eligibility, XP, tiers and configured work rewards.

Open /professions or Help → Professions. Compare starting perks, tier progression, skill bindings, limits and fees. For a quoted paid picker selection, select the role again within 30 seconds to confirm the fee. A saved character and ready payment services are required.

Only enabled earning rules award XP or payouts; performing an activity does not guarantee money. Profession crafting rules can require a minimum numeric level or explicit learning. Named tiers and numeric crafting levels serve different purposes. Read the recipe book's effective requirements.

RPSkills

Purpose: Published skill trees, owned ranks and supported abilities.

Use Help → Skills to inspect prerequisites, rank requirements, profession gates and costs. Select an offered action and review it before confirming. Acquiring one rank does not grant every later rank.

Free upgrades, paid upgrades and player respec are optional. Follow the displayed instructions, which can use /skillprogress confirm <operation ID> or /skillprogress paidconfirm <request ID>. Paid rank confirmation expires after 30 seconds; /skillprogress paidstatus recovers the original paid-upgrade receipt. Respec refunds nothing.

An ability description or preview is not proof of an executable effect. Only supported, enabled abilities meeting their current conditions run.

Read Player actions and services for activation controls, skill effects, consent-based services and identity documents.

RPEconomy

Purpose: Currencies, wallets, transfers, pricing and supported exchange.

Check currency, amount, fees and balance restrictions before confirming. Cash, scrap and other configured currencies can have separate balances. Physical inventory currency and digital funds are interchangeable only through a supported conversion.

For an interrupted transfer, use /paystatus and retain the original request ID. Wait for its terminal result before sending again. A shop quote or held payment is not proof that goods arrived.

RPCrafting

Purpose: Recipe discovery, learning, custom items and production.

Open /craft or Help → Crafting. Unknown recipes can stay locked until learned. Check unlock requirements separately from ingredients, workbench capability, per-craft gates and charges. Profession-assigned vanilla recipes can have different access rules from ordinary native blueprints.

Where physical orders are enabled, /craft quote <recipe> [quantity] inspects a quote. A proposal alone does not start production; use Start crafting for the configured automatic workflow.

Inspect progress with /craft orders and /craft order [id]. /craft ordercancel <id> requests state-dependent cancellation. /craft orderack <id> records receipt handling; it does not grant another output.

Make inventory space for blocked delivery. Retain the order ID after interruption so staff can inspect materials, payment and output before replacing goods.

RPBuilding

Purpose: Construction recipes, upgrades and foundation allowances.

Use Rust's building plan and grade-upgrade controls. A custom piece/grade recipe replaces that piece's native cost. Check the required ingredients first; the actual custom item may be needed, rather than its vanilla parent.

Eligible profession perks can reduce configured building material use. These recipes do not change cupboard upkeep or repair costs.

Open Foundations in in-game Help to inspect allowance and usage. Profession perks, skills, quests or earning rules can contribute. Lowering the allowance does not itself remove existing foundations, but can block further placement.

RPBots

Purpose: Server-authored NPC characters and services.

Approach a reachable bot and use its offered interaction. Bots can provide quests, training, trading or other authored dialogue. Read service requirements: the owning plugin still validates a trainer enrollment or trader purchase.

Other bots gather, patrol, hunt or fight. Faction relationships and safety rules can affect hostility and service access. Report stuck or missing bots with their name and map location.

RPQuests

Purpose: Authored objectives, progress and rewards.

Open Quests in Help or interact with the assigned quest bot. Read prerequisites, objectives, time requirements and rewards before accepting an available quest.

Follow exact targets. Custom items, bot interactions and timed objectives may require more than similar nearby activity. Completion and reward claims can be separate actions; use the offered claim workflow and check its receipt. Keep quest and claim IDs if a reward stays pending.

RPFactions

Purpose: Organized groups, membership, reputation and territory.

Use the Factions workspace to inspect discoverable groups and recruitment. A group can allow direct joins, applications or invitations. Review fees and gates; an invitation is not membership until accepted through its workflow.

Ranks and reputation can control content access. Wars and authoritative territory can affect supported gameplay. Achievement scores use tracked activities and server-defined weights; they do not automatically grant land or money.

RPPlaces

Purpose: Named locations, map markers and supported grid ownership.

Discover nearby published places and inspect descriptions or ownership through the available map/help interface.

A marker does not grant building privilege, business ownership or entry rights. Grid ownership and faction territory are separate systems. Report missing services with the place name, map grid and world; visibility, publication and service radius affect discovery.

RPBusinesses

Purpose: Place-bound businesses, ownership, staffing and commerce.

Browse business information and jobs in the player workspace. Review invitations and accept the intended role. Ownership and accepted staff access determine available work; access can change when employment ends.

Inspect stock, reserved quantity, payment and delivery separately. A reservation is not delivery. Follow recorded courier custody and handoff steps and keep order IDs.

Wages, deposits, payments and IPO actions need the configured providers. A job title alone does not promise an automatic wage. Private staff information is limited to authorized characters.

RPTraders

Purpose: Bot-accessed offers, stock, purchases and deliveries.

Open the configured trader bot's offers. Review item identity, quantity, stock, currency, requirements and total price. Some offers require a particular custom item or variant.

Make inventory space and inspect the purchase/delivery journal if an order is pending. Keep its original ID after interruption; a second purchase does not repair the first.

RPStocks

Purpose: The server's fictional stock market.

Open Help → Stock Market and its available broker panel. Review published instruments, watchlists, history, holdings and enabled buy/sell actions.

Check quantity, price and fees before submitting an order. Trading depends on instrument availability, payment services and configuration. A simulated trend is not a promised future price. Business IPOs have separate requirements. Preserve the order receipt if a portfolio appears inconsistent.

RPRelationships

Purpose: Consented character contacts.

Use the journal's contacts section to send or answer supported invitations. Review the intended character before accepting. Mutual contact requires consent.

Contacts belong to character identities. Expiry and revocation can change shared access. A private note does not create a relationship, job or faction membership. Confirm your current character and pending invitations before sending duplicates.

RPFarming

Purpose: Authorized farm work, livestock records and crop provenance.

Load your character and obtain current access to a farm business. Use /farming work <farm business> with its slug. Work requires ready records and current business authority.

Look at a nearby supported cow or sheep and use /farming register. /farming inspect inspects your target; /farming herd lists herd records; /farming release ends your work session.

Supported native actions can create husbandry, lineage and crop records during authorized work. These records do not replace native animal behavior. XP requires configured profession integration. For access problems, check character, business slug and current owner/staff access.

RPJustice

Purpose: Incidents, evidence review and custody records.

Use /justice or the Justice help section when enabled. Follow the server's reporting and review procedure.

An allegation is not automatically a proven offense. Authorized staff control warrants, custody and corrective release through the configured workflow. Keep incident and custody references when requesting a correction. A journal note or accusation alone does not authorize enforcement.

Troubleshooting

Give staff the action, time, exact message and relevant record ID. Keep account credentials private.

For server setup, read the Admin guide.