An overview of proven free plugins from umod.org that form the basis of most community servers. For each one, you'll find what it does, which permissions to grant, what to set in the configuration and which commands to use. First, there's a recommended set for each type of server.
What you'll need
Rust at StormHost
We're still preparing Rust servers. This guide also applies to a Rust server on your own VPS (installation guide).
How to choose plugins#
- Less is more. Every plugin adds load to the server and can break after a Rust update. Only install what you'll actually use.
- Check the update date on the plugin's page. The version details in this article are as of October 1, 2026.
- Read the description of permissions and commands on the plugin's page. We verified the permission names in this article directly in the code of the listed versions; they may change in newer versions.
oxide.show perms(c.show perms) prints the current list. - The configuration is always in
oxide/(Carbon:config/ <PLUGIN_ NAME>. json carbon/configs/…). The setting names in the tables are exactly as the plugin writes them to the file. - Most plugins work on both Oxide and Carbon. Carbon also has built-in modules that replace some plugins (see the end of the article).
Plugin sets by server type#
| Server type | Recommended plugins | Note |
|---|---|---|
| Vanilla+ (gameplay as Facepunch made it, just easier to manage) | BetterChat, Vanish, Admin Radar, Remover Tool | No kits, teleports or gather multipliers. The server stays close to vanilla. |
| 2x / 3x | + Gather Manager (2–3×), Stack Size Controller (2–3×), Kits (starter kit), NTeleportation (2–3 homes), Backpacks, Clans | The most common type of community server. |
| 10x and up | The same with higher values: gathering and stacks 10×, more homes, shorter cooldowns, bigger backpacks, more kits | Shorter rounds, often a weekly wipe. |
| PvE | Kits, NTeleportation, Backpacks, Remover Tool, BetterChat + the server.pve true setting | For finer rules (who may hurt whom), there are specialized PvE plugins such as TruePVE. |
The multiplier values (2×, 10×) and the number of homes are just a guide; they define your server's style.
ImageLibrary (dependency)#
What it does: a library for other plugins. It downloads and stores images (item icons, kit images, player avatars) that plugins then show in their menus. On its own, it adds nothing for players.
Link: umod.org/plugins/image-library (opens in a new window) · author k1lly0u · verified version 2.0.67
Install it first if a plugin lists ImageLibrary among its dependencies. Kits and Remover Tool, for example, use it for images in their menus; without it, the images won't show.
Permissions: none.
| Setting | What it does | Recommended value | When to change it |
|---|---|---|---|
Avatars - Store player avatars | Stores players' Steam profile pictures (for plugins that display them). | false | true only if a plugin requires it. |
Steam API key (get one here https:// | A Steam Web API key for downloading avatars. | empty | Only for avatars. The key is secret; don't send it to anyone. |
Progress - Show download progress in console | Prints image download progress to the console. | true | false if the output bothers you. |
Commands (server console):
refreshallimages– deletes all stored images and downloads them again. The plugin asks first; confirm withyeswithin 5 seconds (cancel withno). Only use it when images in menus display incorrectly.cancelstorage– cancels a download in progress.
On its first run, ImageLibrary downloads hundreds of icons. It takes a while, and you'll see the progress in the console. The server needs internet access.
Kits#
What it does: sets of items (kits) that players claim with a command or from a menu. Starter kit, VIP kit, automatic kit on respawn, cooldowns and usage limits.
Link: umod.org/plugins/rust-kits (opens in a new window) · author k1lly0u · verified version 4.4.10
Permissions:
| Permission | What it allows | For whom |
|---|---|---|
kits.admin | Create, edit and delete kits, give kits to players, reset counters. | The admin group. |
a kit's permission (e.g. kits.vip) | Claim a specific kit. You choose the name in the kit editor. | The group the kit belongs to (vip). |
A kit without a permission can be claimed by anyone.
Creating a kit step by step:
- Grant yourself the
kits.adminpermission and connect to the server. - Put exactly the items the kit should contain into your inventory, on your belt and on your character.
- Type
/kit newin chat. The kit editor opens. - Fill in the fields:
- Name – the kit's name; players type it in the command (
starter). - Description – the description in the menu.
- Permission – the permission, e.g.
kits.vip. Empty = a kit for everyone. Always start withkits.. - Auth Level – the minimum game admin level (
0= everyone,1= moderators,2= owners). - Maximum Uses – how many times per round a player may take it;
0= unlimited. - Cooldown (seconds) – after how many seconds they may take it again;
0= no waiting. - Purchase Cost – the price (the default currency is scrap,
Scrap);0= free. - Is Hidden – the kit doesn't appear in the menu and can only be given out (good for automatic kits).
- Name – the kit's name; players type it in the command (
- Click Copy From Inventory. The items from your inventory are copied into the kit.
- Click Save Kit.
- If the kit has a permission, grant it to a group:
oxide.grant group vip kits.vip.
Key settings:
| Setting | What it does | Recommended value | When to change it |
|---|---|---|---|
Kit chat command | The name of the chat command. | kit | When it clashes with another plugin. |
Currency used for purchase costs (Scrap, Economics, ServerRewards) | The currency for paid kits. Economics and ServerRewards are separate plugins. | Scrap | When you have an economy plugin. |
Wipe player data when the server is wiped | Resets players' usage counters and cooldowns after a wipe. | true | Leave it false only if limits should carry over between rounds. |
Use the Kits UI menu | The /kit command opens a graphical menu. | true | false for text-only control. |
Autokits ordered by priority | A list of kits a player gets automatically on respawn (they get the first one they're entitled to). | e.g. ["starter"] | When you want an automatic starter kit. |
Allow players to toggle auto-kits on spawn | Players can turn off the automatic kit with /kit autokit. | false | true if players want it. |
Show kits with permissions assigned to players without the permission | Also shows kits the player has no permission for in the menu (like a “VIP Kit”). | false | true as a teaser for VIP. |
Post wipe cooldowns (kit name | seconds) | How many seconds after a wipe a kit can't be claimed. Key = kit name. | e.g. "pvp": 3600 | Strong kits that would give an advantage at the start of a round. |
Commands: /kit (menu), /kit <NAME> (claim), /kit list, /kit new, /kit edit <NAME>, /kit delete <NAME>, /kit give <PLAYER> <NAME>, /kit reset (resets all uses), /kit resetuses <PLAYER> <NAME>.
Clans#
What it does: clans with a short tag, owner/moderator/member roles, clan chat and alliances between clans. Rust has its own teams and a built-in clan system; the Clans plugin adds tags in chat (with BetterChat), alliances and management via commands. The plugin doesn't handle friendly fire.
Link: umod.org/plugins/clans (opens in a new window) · author k1lly0u · verified version 0.2.10
Permissions: none; anyone can create a clan.
Key settings (the Clan Options section with the Alliance Options, Clan Tag Options and Purge Options subsections):
| Setting | What it does | Recommended value | When to change it |
|---|---|---|---|
Member limit | The maximum number of clan members. | 8 (default) | Match it to the team size (relationshipmanager.) and the server's style (solo/duo/trio). |
Moderator limit | How many moderators a clan can have. | 2 | – |
Enable clan alliances | Allows alliances. | true | false on servers with small teams, so clans don't team up. |
Alliance limit | How many alliances a clan may have. | 2 | – |
Tag character limits | The minimum and maximum tag length. | 2–5 | – |
Enable clan tags (requires BetterChat) | Shows the clan tag before the name in chat. | true | Needs the BetterChat plugin. |
Enable clan purging | Automatically deletes clans whose members haven't been online for a long time. On by default (true). | true | false if clans should never be deleted. |
Purge clans that havent been online for x amount of day | After how many days of inactivity a clan is deleted. | 14 (default) | Longer on servers with a monthly wipe, so the clan doesn't vanish for players who take a short break. |
Player commands:
| Command | What it does |
|---|---|
/clan create <TAG> "description" | Creates a clan. |
/clan invite <PLAYER> | Invites a player (owner and moderators). |
/clan accept <TAG> / /clan reject <TAG> | Accepts or declines an invitation. |
/clan | Information about your own clan. |
/c <MESSAGE> | Clan chat. |
/a <MESSAGE> | Alliance chat. |
/clan leave | Leaves the clan. |
/clan kick <PLAYER>, /clan promote <PLAYER>, /clan demote <PLAYER> | Member management. |
/clan disband forever | Disbands the clan (owner only). |
/ally invite <TAG> | An alliance invitation. |
/clanhelp | Help based on your role. |
BetterChat#
What it does: chat titles and colors based on permission groups (e.g. [Admin] in red, [VIP] in gold), message format and a message length limit.
Link: umod.org/plugins/better-chat (opens in a new window) · author LaserHydra · verified version 5.2.15
Permissions: betterchat.admin – managing chat groups with the chat command. Grant it to the admin group.
How it works: a BetterChat chat group has the same name as a permission group. Anyone in the vip group gets the vip group's title. The chat group add command creates both the chat group and the permission group.
Setting up a VIP title (in the server console, or as an admin in chat with a slash):
chat group add vip
chat group set vip Title [VIP]
chat group set vip TitleColor #ffd479
chat group set vip Priority 1
chat user add 76561198000000000 vipchat group add vip– creates thevipgroup (and a permission group of the same name, if it doesn't exist).chat group set vip Title [VIP]– the title text shown before the name.chat group set vip TitleColor #ffd479– the title color in hex.chat group set vip Priority 1– the priority: a lower number = a higher priority. When a player is in several groups, the one with the lowest number is the main one.chat user add 76561198000000000 vip– adds the player to the group.
| Group field | What it sets |
|---|---|
Title, TitleColor, TitleSize | Title text, color and size. |
TitleHidden, TitleHiddenIfNotPrimary | Hide the title always, or when the group isn't the main one. |
UsernameColor, UsernameSize | Name color and size. |
MessageColor, MessageSize | Message text color and size. |
ChatFormat | The message format, default {Title} {Username}: {Message}. |
Priority | Group order (lower = higher). |
| Setting (configuration) | What it does | Recommended value | When to change it |
|---|---|---|---|
Maximal Titles | How many titles are shown for a player at once. | 3 (default) | 1 if you only want the main title. |
Maximal Characters Per Message | The maximum message length. | 128 (default) | – |
Reverse Title Order | Reverses the order of titles. | false | – |
Commands: chat group <add|remove|set|list>, chat user <add|remove> <PLAYER> <GROUP>.
Gather Manager#
What it does: multiplies the amount of resources from gathering, picking up, quarries and survey charges. The foundation of 2x, 3x and 10x servers.
Link: umod.org/plugins/gather-manager (opens in a new window) · authors Mughisi, Ryan · verified version 2.2.78
An older plugin
The latest Gather Manager release is from 2022. Before deploying it, check on its page that it works with the current version of Rust. On Carbon, you can use the built-in GatherManager module instead (see the end of the article).
Permissions: none. Only a game admin (owner or moderator) or the server console can run the commands.
Commands (server console):
gather.rate dispenser * 2
gather.rate pickup * 2
gather.rate quarry * 2
gather.rate excavator * 2
gather.rate survey * 2gather.rate <TYPE> <RESOURCE> <MULTIPLIER>– the multiplier for a given way of obtaining resources:dispenser– gathering with a tool: trees, ore nodes, dead animals,pickup– picking up from the ground (hemp, stones, wood lying around),quarry– the Mining Quarry,excavator– the Giant Excavator,survey– the Survey Charge.
*– all resources. Instead of the asterisk, you can give the English name of a resource; put multi-word names in quotes, e.g.gather.rate dispenser "Metal Ore" 3.2– the multiplier.gather.rate dispenser Wood removeremoves the setting for a resource.
More commands: dispenser.scale tree 2 (how many resources a tree contains in total; types tree, ore, corpse), quarry.tickrate 5 (seconds between quarry yields, default 5), excavator.tickrate 3 (default 3). Players can view the settings with /gather.
The difference between gather.rate dispenser and dispenser.scale: the first changes how much you get per hit; the second changes how many resources a tree or rock holds in total (that is, how many hits it lasts).
The commands are saved to the configuration (the Options section, e.g. GatherResourceModifiers), so they still apply after a restart.
Stack Size Controller#
What it does: changes how many units of an item fit into one inventory slot (a stack). On servers with higher gather rates it's a must, otherwise inventories fill up quickly.
Link: umod.org/plugins/stack-size-controller (opens in a new window) · author AnExiledDev (modified by chrome) · verified version 4.1.3
An older plugin
The latest release is from 2024. Before deploying it, check on the plugin's page that it works with the current Rust. On Carbon, the alternative is the built-in StackManager module. Never use two stack tools at the same time.
Permissions: each command has a permission of the same name (e.g. stacksizecontroller.). From the server console, they work without permissions.
Key settings:
| Setting | What it does | Recommended value | When to change it |
|---|---|---|---|
GlobalStackMultiplier | The stack multiplier for all items that don't have their own category or item multiplier. | 1 | For a simple server-wide setup (2, 3, 10). |
CategoryStackMultipliers | Multipliers for categories (Resources, Ammunition, Medical, Food, Weapon, Construction …). Only values greater than 1 apply, and they take precedence over the global multiplier (they aren't multiplied with it). | 1 for all | Raise mainly Resources. |
IndividualItemStackMultipliers | The multiplier for a specific item (key = the item's short name, e.g. wood). Takes precedence over both the category and the global multiplier. | empty | Exceptions. |
IndividualItemStackSize | The base stack size of each item. The plugin fills it with the game's defaults on first run. The multipliers above are calculated from this value. | the game's defaults | When you want a different base for an item. Note: the category or global multiplier is still applied to the modified value. |
AllowStackingItemsWithDurability | Allows changing stacks of items with durability (weapons, tools). With false, they always keep the game's default size. | true | false if you don't want weapons to stack. |
RevertStackSizesToVanillaOnUnload | Restores the original stacks when the plugin unloads. | true | – |
How the size is calculated: the plugin takes the base from IndividualItemStackSize and multiplies it by only one multiplier – the first one it finds for the item: the item multiplier, otherwise the category multiplier (if it's greater than 1), otherwise the global multiplier. Example: the base for wood is 1000, the Resources category has 5 and the global multiplier is 2. The result is 5000 (the global multiplier isn't used for wood).
Commands (console):
| Command | What it does |
|---|---|
stacksizecontroller. | Sets an item's base size (writes it to IndividualItemStackSize), e.g. stacksizecontroller.. If the category or the whole server has a multiplier, the result is multiplied by it as well. With an x at the end, you set the item multiplier instead: stacksizecontroller.. |
stacksizecontroller. | The category multiplier (a whole number), e.g. stacksizecontroller.. |
stacksizecontroller. | The same multiplier (a whole number) for all categories. |
stacksizecontroller. | Finds an item's short name. |
stacksizecontroller. | Lists the categories. |
On startup, the plugin downloads a list of default stack sizes from GitHub, so the server needs internet access.
Vanish#
What it does: complete invisibility for admins and moderators. Other players and NPCs can't see an invisible player or hear their footsteps. Used for watching suspicious players.
Link: umod.org/plugins/vanish (opens in a new window) · author Whispers88 · verified version 2.1.5
Permissions:
| Permission | What it allows |
|---|---|
vanish.allow | Turn invisibility on and off with /vanish. |
vanish.unlock | Open locked doors and boxes while invisible. |
vanish.damage | Deal damage while invisible. |
vanish.permanent | Permanent invisibility: the player is always invisible, even right after connecting, and /vanish doesn't turn it off. Only give it to a specific account, never to a group. |
vanish.invviewer | View another player's inventory (/inv, /invspy). |
vanish.teleport | Teleport to a map marker while invisible: hold R and place a marker. Only works with Enable teleport to marker when vanished turned on (default false). |
Key settings:
| Setting | What it does | Recommended value | When to change it |
|---|---|---|---|
NoClip on Vanish (runs noclip command) | Turning invisibility on also turns on flying (noclip). | true | false if you give the permission to people without a game admin level (noclip wouldn't work for them). |
Use OnEntityTakeDamage hook (…) | Turns on the vanish.damage permission check. Without it, the vanish.damage permission does nothing. | false (default) | true only if you actually use vanish.damage (costs a little performance). |
Use CanUseLockedEntity hook (…) | Turns on the vanish.unlock permission check. | true (default) | false saves performance if you don't use vanish.unlock. |
Enable teleport to marker when vanished | Allows teleporting to a map marker (the vanish.teleport permission). | false (default) | true if moderators want it. |
Enable GUI | An on-screen icon showing that you're invisible. | true | – |
Commands: /vanish (toggle), /inv <PLAYER> or /invspy <PLAYER> (a player's inventory).
Carbon has a built-in Vanish module with the same permission names (vanish.allow …). Don't use the plugin and the module at the same time.
Admin Radar#
What it does: a “radar” for admins: shows players, sleepers, boxes, stashes, corpses, vehicles and other objects through walls, with names and distances. Helps catch cheaters and find hidden stashes.
Link: umod.org/plugins/admin-radar (opens in a new window) · author nivex · verified version 5.4.3
Permissions:
| Permission | What it allows |
|---|---|
adminradar.allowed | Use the radar. |
adminradar.auto | The radar turns on automatically after connecting. |
adminradar.list | Use the listings (list). |
Who has access: if the Restrict Access To Steam64 IDs list is filled in, only those people can use the radar. Otherwise, anyone with the adminradar.allowed permission or a game admin level of at least Restrict Access To Auth Level (default 1, i.e. both moderators and owners) can use it.
| Setting | What it does | Recommended value | When to change it |
|---|---|---|---|
Restrict Access To Steam64 IDs | A list of Steam IDs that are the only ones allowed to use the radar. | empty | For maximum safety, fill in only the head admins' IDs. |
Restrict Access To Auth Level | The minimum game admin level for access without the permission. | 1 | 2 if moderators shouldn't get it automatically. |
Default Distance | The radar range in meters. | 500 | A bigger range puts more load on both the client and the server. |
Default Refresh Time | How often the radar refreshes (seconds). | 5 | – |
Max Active Filters (MODERATORID) | How many filters a moderator can have on at once. | 4 | – |
Commands: /radar (toggle), /radar <REFRESH> <RANGE> <FILTERS> – for example /radar 1 1000 box loot stash (refresh 1 s, range 1000 m, boxes, loot, stashes). Also /radar online (with the box filter, only boxes of players who are online), /radar ui (a quick control panel), /radar vision (shows where players are looking), /radar ext (extended player information) and /radar drops (items on the ground nearby).
NTeleportation#
What it does: homes (/home), teleporting to another player on request (/tpr and /tpa), going back (/tpb), teleporting to town, Outpost and Bandit Camp. With cooldowns, countdowns and daily limits, separately for VIPs.
Link: umod.org/plugins/nteleportation (opens in a new window) · author nivex · verified version 1.9.6
Permissions (selection):
| Permission | What it allows | For whom |
|---|---|---|
nteleportation.home | Homes: save, list, teleport. | default |
nteleportation.tpr | Send and accept teleport requests. | default |
nteleportation.tpb | Return to where you were before the last teleport. | default or vip |
nteleportation.tpoutpost, nteleportation.tpbandit, nteleportation.tptown | Teleport to Outpost, Bandit Camp, town. | depending on the server's style |
nteleportation.vip | VIP limits from the configuration (more homes, shorter cooldowns). | vip |
nteleportation.tp | Admin teleport /tp. | admin |
nteleportation.admin | Managing other players' homes and other admin functions. | admin |
Key settings (the Home section; TPR is similar):
| Setting | What it does | Recommended value | When to change it |
|---|---|---|---|
Homes Limit | How many homes a player may have. | 2 (default) | 3–5 on 10x servers. |
VIP Homes Limits | The VIP limit: key = permission, value = count. | {"nteleportation.vip": 5} | You can add your own permission; the plugin registers it. |
Cooldown | Seconds between teleports. | 600 (10 minutes) | Shorter on fast servers. |
Countdown | The countdown in seconds before a teleport (taking damage interrupts it). | 15 | – |
Daily Limit | How many teleports per day. | 5 | – |
Location Radius | The minimum distance between homes (meters). | 25 | – |
Wipe On Upgrade Or Change (the Settings section) | Deletes homes after a wipe. | true | – |
A home can only be saved on a foundation of your own building. An admin saves the town location with /town set.
Player commands: /home add <NAME>, /home <NAME>, /home list, /home remove <NAME>, /tpr <PLAYER>, /tpa (accept), /tpc (cancel), /tpb, /town, /outpost, /bandit.
Remover Tool#
What it does: players can remove their own building parts and items (say, a wall built by mistake) and get part of the materials back. Admins can remove anything.
Link: umod.org/plugins/remover-tool (opens in a new window) · authors Reneb, Fuji, Arainrr, Tryhard · verified version 4.3.48
Permissions:
| Permission | What it allows | For whom |
|---|---|---|
removertool.normal | Remove your own buildings and items. | default |
removertool.admin | Admin mode: remove anything. | admin |
removertool.all | Remove a whole building, including items. | admin |
removertool.structure | Remove a whole building (without items). | admin |
removertool.external | Remove external walls and gates. | as needed |
removertool.target | Turn on removal for another player. | admin |
removertool.override | Override another player's settings. | admin |
Key settings:
| Setting | What it does | Recommended value | When to change it |
|---|---|---|---|
Use Entity Owners | A player can only remove what they built themselves. | true | – |
Use Clans / Use Teams / Use Friends | They can also remove buildings of clanmates, teammates or friends. | Use Clans true, Use Teams false | Use Teams true if players mostly play in teams. |
Use Tool Cupboards (Strongly unrecommended) | Anyone authorized on the tool cupboard (TC) can remove things. The author advises against it (can be abused during a raid). | false | – |
Remove Damaged Entities › Enabled | Allows removing damaged objects. With false, nothing with less than 90% health (Percentage) can be removed, and the player sees Can't remove: Server has disabled damaged objects from being removed. This protects against abuse during a raid. | false (default) | true only if you want to allow removing damaged objects. |
Remove Damaged Entities › Exclude Building Blocks | Building blocks (walls, foundations, ceilings) are excluded from the protection, so a damaged wall can be removed even with Enabled set to false. | false (default true) | Set it to false to protect buildings during raids. |
Use Raid Blocker (the NoEscape Settings section) | Blocks removal during a raid block (needs the NoEscape plugin). | true if you have NoEscape | – |
Refund (per permission) | The player gets part of the materials back. | true | – |
Cooldown (for the removertool.normal permission) | Seconds between uses of the tool. | 60 | – |
Commands: /remove (turns the tool on; then left-click objects; another /remove turns it off), /remove <SECONDS>, /remove admin, /remove all, /remove structure, /remove external.
Backpacks#
What it does: a personal backpack with extra inventory space, opened with a button or a command. Size based on permissions, options for what happens on death and at a wipe.
Link: umod.org/plugins/backpacks (opens in a new window) · author WhiteThunder · verified version 3.17.7
Permissions:
| Permission | What it allows | For whom |
|---|---|---|
backpacks.use | Use the backpack. | default |
backpacks.gui | The on-screen backpack button. | default |
backpacks.size.<COUNT> | Backpack size in slots: 6, 12, 18, 24, 30, 36, 42, 48, 96, 144 (according to the Permission sizes setting). | e.g. backpacks.size.24 for vip |
backpacks.keepondeath | The backpack's contents aren't lost on death. | depending on the server's style |
backpacks.admin | View and edit players' backpacks. | admin |
Key settings:
| Setting | What it does | Recommended value | When to change it |
|---|---|---|---|
Backpack size › Default size | The backpack size without a size permission. | 6 (default) | 12–24 on fast servers. |
Backpack size › Permission sizes | Which sizes have their own permission. | the default list | – |
Drop on Death (true/false) | After death, the backpack drops to the ground (and can be looted). | true | false on PvE servers. |
Erase on Death (true/false) | After death, the contents are erased. | false | – |
Clear on wipe › Enabled | Empties backpacks at a wipe. | true | The default is false – unless you change it, backpack contents survive the wipe. |
GUI Button › Enabled | The on-screen backpack button. | true | – |
Commands: /backpack (open), /backpackgui (hide/show the button), and for admins viewbackpack <PLAYER>.
Built-in alternatives in Carbon#
Carbon has optional modules that replace some plugins. You turn them on with c.setmodule <MODULE> true (off with false), c.modules lists them, and the settings are in the carbon/modules folder or in the /cpanel admin panel.
| Module | Replaces | Note |
|---|---|---|
GatherManager | Gather Manager | Multipliers for Pickup, Gather, Quarry, Excavator; "*" = all resources. Marks the server as modded. |
StackManager | Stack Size Controller | Global multiplier, categories, specific items, an exclusion list. |
Vanish | Vanish | Permissions vanish.allow, vanish.unlock, vanish.permanent, the /vanish command. |
Whitelist | whitelist plugins | Only lets in players with the whitelist.bypass permission or in the whitelisted group (and admins). |
AutoWipe | scheduled wipe plugins | Wipes on a cron schedule, see Wipe. |
Admin panel (/cpanel) | admin plugins with menus | Always on, for owners (auth level 2). |
Never run a module and a plugin with the same function at the same time.
Troubleshooting#
Players can't use a plugin command#
A permission is missing. Grant it to the default group (e.g. oxide.grant group default nteleportation.home) and check with oxide.show group default. See Permissions.
Kits: You do not have the required permission to access this kit#
The kit has a permission the player doesn't have. Grant it to their group, or clear the Permission field in the kit editor. Similarly: You have a cooldown of … remaining (waiting for the cooldown), You have already reached the maximum number of uses allowed for this kit (used up the limit) and You do not have enough space in your inventory to claim this kit (full inventory).
NTeleportation: You can only use a home location on a foundation!#
A home can only be saved while you're standing on a foundation. On someone else's building, it says You can't use home on someone else's house., and once you've reached the limit, Unable to set your home here, you have reached the maximum of … homes!.
The plugin's menu has no images#
ImageLibrary isn't installed, or it's still downloading images. Check oxide.plugins and the download output in the console. The server needs internet access.
Stacks or gathering behave strangely#
Two tools for the same thing are running (Stack Size Controller and the StackManager module, or two gathering plugins). Keep only one. After changing the configuration, reload the plugin.
Titles are duplicated in chat#
Two chat plugins are running, and both modify messages. Keep only BetterChat (or only the other one).
A plugin won't load after a Rust update#
A compilation error after a major update means the plugin needs a new version. Check its page on umod.org, or unload it until a fix is released. Troubleshooting steps are in installing plugins.
Backpacks aren't empty after a wipe#
In the Backpacks configuration, Clear on wipe › Enabled is at its default false. Change it to true and reload the plugin.
Summary
- Start with a small set based on your server type and only add what you'll use.
- Install ImageLibrary first if other plugins need it.
- Grant players' basic permissions to the
defaultgroup, VIP perks to thevipgroup and admin tools to theadmingroup. - Gather Manager and Stack Size Controller are older plugins – check compatibility, and on Carbon consider the built-in modules.
- Watch the default wipe settings: Kits (
false), Backpacks (false), NTeleportation (true).