Rust Console Server Settings vs PC Plugins: What Can You Use?
Compare documented Rust Console server settings, provider-specific WebRCON tools, and PC-only plugins before choosing a feature or platform.
You will need
- Rust Console Edition or PC Rust, identified for every player
- The exact community-server provider and feature you want
If you are looking for a Rust Console plugin, first identify what the feature should do. Console Edition has documented server settings and provider-specific administration routes; PC Rust has separate frameworks such as uMod/Oxide and Carbon. Those are different tools for different server ecosystems. This guide helps you sort a request into a documented Console setting, an external tool your provider explicitly supports, or a PC-only plugin path. It does not promise feature parity or make a Console server compatible with PC Rust.
First confirm which Rust edition your group uses#
Rust for PC and Rust Console Edition are separate products. Double Eleven’s current Console FAQ lists PlayStation 5 and Xbox Series X|S. The official community-server route sends Console owners to that ecosystem’s community-server providers. Game Hosting’s Rust product serves PC Rust only. A PC plugin list, server address, or hosting plan does not make the editions crossplay compatible.
If you are comparing an actual Console rental, use the Console server pre-purchase checklist to verify edition, provider and terms. This guide focuses on whether a requested control or plugin path fits that edition; it is not a provider ranking.
Write down each player’s edition before researching a feature. If your whole group has Console Edition, use the official Console setup documentation and the exact provider’s offer. If the group deliberately chooses PC Rust instead, start with a PC guide such as how to build a maintainable Rust plugin stack and check current provider support. Do not switch only one player and expect the server ecosystem to bridge the gap.
Classify the feature before choosing a tool#
Describe the result you want in plain language: limit who joins, change the map, moderate chat, show a live map, or add a new gameplay mechanic. Then use this table to identify what evidence to look for.
| Feature request | Console route to check | What the evidence means |
|---|---|---|
| Set a server name, password, map, seed, size, or monuments | Provider panel described by the official setup guide | These are documented setup controls; the exact provider panel may expose a subset or use different labels. |
| Restrict access with a whitelist | Official Console server settings and the provider panel | A documented setting is not proof that your plan exposes it or that a join test succeeded. |
| Run commands or inspect a remote console | Ask the provider which Console RCON route it supports | A provider-specific WebRCON guide documents remote administration, not a plugin runtime. |
| Add a gameplay feature implemented by a PC plugin | Check whether the Console publisher and exact provider document that feature | PC framework instructions alone do not establish a Console equivalent. |
Keep the exact setting name, provider, plan, and source together. A similar label in a different edition is not evidence that the control exists in your server panel.
Check documented native Console settings#
The official Console setup guide describes provider-entered basics such as server name, password, map, seed, player count, map size, and monuments. It also documents Console owner, admin, moderator, and VIP role commands. These references tell you which controls belong to the Console community-server system; they do not guarantee that every host exposes every control on every plan.
The official server settings reference documents server.enablewhitelist as an owner-level setting with 0 or 1 input and a default of 0. It says the whitelist rejects players who are not on it. Before relying on that control, confirm that your provider exposes it, ask how allowed players are added, and test an allowed and an unlisted account if the feature is essential. The same reference lists an idle-kick timer and mode; verify their current panel exposure and behavior with your provider.
This is a useful pattern for any desired feature: find it in the current official Console reference, confirm it appears in your actual provider panel, then test its effect. If one of those checks is missing, record the uncertainty instead of assuming the PC command or plugin behaves the same way.
Separate WebRCON from installed plugins#
Remote Console (RCON) sends administrative commands to a server. A browser client, bot, or dashboard connected through RCON can provide an external workflow, but that is not the same as installing code into the game server.
GPORTAL’s Rust Console RCON guide describes connecting a WebRCON client with the IP address, port, and password supplied in its panel. Treat this as GPORTAL’s documented route for its own Console service. It does not prove every Console provider offers RCON, that every third-party client is supported, or that the connection delivers arbitrary new gameplay mechanics. Confirm the current host documentation and protect the RCON password as an administrator secret.
Ask the provider these questions before building a workflow around RCON:
- Is WebRCON available on this exact Console plan and region?
- Which client or connection method does the provider document?
- Which commands and administrative roles are supported?
- Can the tool only observe and send commands, or does it claim to add a game feature?
- What happens to access when the server password or owner changes?
If the feature is supplied by a separate vendor, check that vendor’s current compatibility statement with your host and console platform. Keep its claims separate from Double Eleven’s documentation and from the host’s own support terms.
PC plugins belong to the PC server route#
On PC Rust, frameworks such as uMod/Oxide and Carbon load server-side plugins. Their own uMod installation documentation and Carbon owner guide describe PC server workflows. They are useful sources when your group has chosen a PC dedicated server and wants to assess a plugin stack.
Those pages do not describe a Console Edition installation route. A PC plugin’s feature name may sound like a Console setting, but matching the outcome does not establish that the implementation, command, data format, or compatibility carries over. Do not upload a PC framework or plugin to a Console host unless Double Eleven and that specific provider document the exact procedure. The same distinction applies in reverse: a Console provider’s WebRCON guide is not a PC plugin installation guide.
For other PC-only configuration questions, see how Rust server settings persist across restarts. That reference concerns the PC server configuration route. It cannot confirm that a similarly named setting is available in Console Edition or in a provider’s Console panel.
For PC Rust, a host may document support for a framework without guaranteeing that every third-party plugin works. Check the required framework version, plugin dependencies, update policy, file access, and recovery process with the provider. If you choose PC hosting, Game Hosting offers PC Rust plans; review the Rust product page for current product details. That offer does not apply to Console Edition.
Use a provider evidence checklist#
Before you pay for a Console community server or connect an external tool, save answers for the exact offer:
| Check | Record |
|---|---|
| Edition and platforms | Rust Console Edition and the supported consoles named by the current offer |
| Native setting | Official setting or setup reference, exact value, and whether the provider exposes it |
| External administration | Provider’s RCON instructions, required credentials, supported commands, and vendor compatibility |
| Plugin or gameplay feature | Whether Double Eleven and the provider document it for Console, rather than only for PC |
| Verification | A test that demonstrates the intended result and the failure case, if the feature is essential |
| Open question | The provider’s written answer, the date, and what it does not confirm |
Do not treat a marketing label such as “custom,” “modded,” or “RCON ready” as an answer to all of these checks. Ask what the named feature does, where its code or commands run, which edition it supports, and how to undo it. If the host cannot answer, choose a documented native option or leave the feature out.
Decide whether the missing feature changes your edition#
If the feature is essential and only a PC plugin source documents it, the group has a platform decision to make. Compare whether everyone can and wants to use PC Rust, then evaluate the PC server and plugin route separately. If the group stays on Console, use the current official Console community-server route and select features documented for that ecosystem.
Do not choose a host based on a promised result that has not been verified for your edition and plan. A settings reference, a provider support page, and a successful live test are three different levels of evidence. Keep them distinct, and ask for a specific confirmation when the result matters to your group.
If the provider confirms a feature only in a support reply, save the wording and date with your server notes. Ask whether the answer applies to your exact edition, region and plan, and whether it describes an available control or only a requested change. That record gives your group a clear decision point if the panel, provider terms or game update later changes.
Quick answers
Can I install Oxide or Carbon on a Rust Console server?
Do not treat PC Oxide/uMod or Carbon installation guides as a Console installation method. Their documented server framework instructions are for PC Rust; check Double Eleven and your exact Console provider for supported options.
Does WebRCON give a Console server PC plugins?
No. WebRCON is a remote command interface. GPORTAL documents a WebRCON connection for its own Rust Console servers, but that does not load code into the game server or establish support at every provider.
Are PC Rust and Rust Console Edition crossplay compatible?
Do not assume crossplay between editions. Double Eleven lists PlayStation 5 and Xbox Series X|S for Console Edition; Game Hosting offers PC Rust hosting, not a Console server.