Skip to content
RustPluginGenerator

Permission command builder

Build the exact oxide.grant, oxide.group and c.grant commands for players and groups. Copy them into your console.

Framework
Give to

Built-in groups: default (everyone) and admin.

One per line or comma separated. Use pluginname.* for every permission of a plugin.

Console commands

> oxide.grant group default killrewards.use> oxide.grant group default kits.vip

Paste into the server console, your RCON tool, or the F1 console in game as an admin. Check that it worked:

oxide.show group default

How Oxide permissions work

Plugins register permissions such as killrewards.use or kits.vip. Nobody has them until you grant them, either to a single player or to a group. Every player is in the default group, and admins are in admin.

  • Grant to a group when a rule applies to many players: oxide.grant group vip kits.vip.
  • Grant to a player for one-off cases: oxide.grant user 76561198000000000 kits.vip.
  • Use wildcards to give every permission of a plugin: oxide.grant group admin kits.*.
  • Parent groups inherit permissions, so a vip group with parent default gets everything default has.

Oxide vs Carbon commands

Carbon uses the same model with a c. prefix: c.grant, c.revoke, c.group and c.usergroup. Switch the framework at the top and the commands update.

Checking the result

Run oxide.show user <name> or oxide.show group <name> to list what a player or group has. oxide.show perms lists every permission registered by loaded plugins, which is the fastest way to find the exact name to grant.

FAQ

Do I use the SteamID or the player name?

Both work while the player is known to the server, but the SteamID64 (17 digits starting with 7656119) is safer: names change and can contain spaces or symbols.

Why does my permission not work after granting it?

Check the exact name with oxide.show perms: a typo creates nothing. The plugin must be loaded for its permissions to exist. Some plugins also read permissions only when a player connects, so have the player reconnect.

Where are permissions stored?

Oxide saves them in oxide/data/oxide.users.data and oxide.groups.data. They survive restarts and map wipes. A blueprint wipe does not reset them either.

How do I give a permission to everyone?

Grant it to the default group: oxide.grant group default pluginname.use. Every player is in that group.