Buzzta Plugins – Installation & Configuration Guide

1. Introduction

Buzzta Plugins are built for Rust servers running Oxide.

Plugins are installed using the standard Oxide plugin system, while configuration and day-to-day administration can be handled either through traditional configuration files or, where supported, directly in-game through the Buzzta Plugin Control Center.

The Plugin Control Center brings plugin operations, supported configuration editing, player tools, permissions, groups, item distribution and server variables into one central in-game interface.

This allows many common server administration tasks to be performed without constantly switching between the game, server console, file manager and JSON configuration files.

2. Requirements

Before installing a Buzzta Plugin, make sure your server meets the following requirements:

• A running Rust Dedicated Server

• Oxide installed and working

• Access to your server files through FTP, SFTP or your hosting provider's file manager

• The purchased Buzzta Plugin file

• The optional Plugin Control Center, if you want to use its in-game administration features

The Plugin Control Center is available separately and is not automatically included with every Buzzta Plugin.

3. Installing a Buzzta Plugin

Buzzta Plugins are supplied as .cs files.

Example:

ExamplePlugin.cs

Step 1 – Download the Plugin

Download the plugin file supplied with your purchase.

Do not rename the file unless the plugin documentation specifically instructs you to do so.

Step 2 – Open the Oxide Plugin Directory

Connect to your Rust server using your host's file manager, FTP or SFTP.

Navigate to:

oxide/plugins/

Step 3 – Upload the Plugin

Upload the .cs file into the plugin directory.

Example:

oxide/plugins/ExamplePlugin.cs

If Oxide is already running, the plugin will normally be detected, compiled and loaded automatically.

A complete server restart is usually not required.

4. Installing the Plugin Control Center

The Plugin Control Center is installed like any other Oxide plugin.

The required file is:

PluginControlCenter.cs

Upload it to:

oxide/plugins/PluginControlCenter.cs

After Oxide has successfully loaded it, the Control Center can be opened directly in-game.

Use either:

/cc

or:

/controlcenter

The interface opens on the plugin overview.

5. What the Plugin Control Center Does

The Plugin Control Center is designed as a central administration workspace for common Rust server management tasks.

Depending on your permissions, it provides access to:

• Plugin overview and plugin status

• Plugin loading, unloading and reloading

• Supported plugin configuration

• Embedded interfaces of compatible plugins

• Detected plugin commands

• Player information and administration

• Permissions

• Groups

• Item distribution

• Server ConVars

The Control Center does not download purchased plugins, automatically install shop packages or update plugins from the internet.

The relevant plugin .cs file must already exist on the server.

6. Dashboard

The Dashboard provides a compact overview of the current server administration environment.

It can display:

• Loaded plugins compared with detected plugins

• Available configuration adapters

• Pending configuration changes

• Currently active players

• Known player identities

• Whether access is being granted through the permission system or Rust administrator status

• Shortcuts to Plugins, Players and ConVars

The Dashboard is intended as an administrative overview.

It is not a server performance monitor and does not provide CPU, RAM or FPS monitoring.

7. Plugin Management

Open the Plugins section to view plugins detected by the Control Center.

The list can include both currently loaded plugins and available .cs plugin files.

Depending on the plugin and your permissions, the following actions may be available:

Load

Loads a plugin file that is present on the server but currently not loaded.

Unload

Temporarily unloads a running plugin.

Reload

Reloads a currently loaded plugin.

This is particularly useful after configuration changes.

Settings

Opens the available configuration interface for the selected plugin.

Open

Opens an integrated plugin interface or configured opening command when supported by that plugin.

Commands

Displays detected chat and console commands belonging to the plugin.

A plugin may also display a CC UI indicator when it reports support for an embedded Control Center interface.

Not every plugin with configurable settings has its own dedicated embedded interface.

8. Configuring Plugins through the Control Center

For compatible plugins, configuration can be edited directly inside the Control Center.

This is one of the main advantages of using the CC, as many common settings can be modified without manually opening JSON files.

Depending on the detected or provided configuration schema, settings may include:

• ON/OFF switches

• Text fields

• Integer values

• Decimal values

• Plus and minus controls for numeric values

• Defined minimum and maximum values

• Defined adjustment increments

• Configuration labels

• Configuration paths

Changes are kept in the current editing state until they are saved.

9. Save and Save + Reload

The Settings editor provides two different ways of applying configuration changes.

Save

Save writes the modified values into the plugin's existing JSON configuration.

This does not necessarily mean that the target plugin immediately reloads the changed settings.

Whether a setting becomes active immediately depends on how the individual plugin handles configuration changes.

Save + Reload

Save + Reload first saves the configuration and then triggers a reload of the selected plugin.

This ensures that the plugin reads the newly saved configuration again.

For settings that require a plugin reload, this is normally the appropriate option.

Reloading a plugin may briefly interrupt the functionality provided by that plugin.

10. How Plugin Settings Are Detected

The Control Center supports several methods of making plugin settings available.

Built-in Control Center Adapters

Some plugins have configuration definitions directly integrated into the Control Center.

These adapters allow the CC to present known settings in a structured form.

External Adapters

Additional adapter definitions can be stored under:

oxide/data/PluginControlCenter/Adapters

This allows the configuration support of the Control Center to be extended.

Plugin-Provided Schemas

Compatible plugins can provide their own setting definitions to the Control Center.

This allows the plugin itself to define which configuration options should be presented.

Automatic Configuration Detection

The Control Center can also inspect suitable existing JSON configurations and automatically create configuration fields for supported primitive values.

Typical supported values include:

• Boolean

• Integer

• Float

• String

This means that basic configuration support is not limited exclusively to Buzzta Plugins.

However, automatic detection is intentionally limited and should not be considered a universal JSON editor.

Large complex structures, arbitrary arrays and some special configuration values may not be exposed.

11. Embedded Plugin Interfaces

Some compatible plugins provide their own user interface that can be opened within the Control Center context.

When supported, an Open option becomes available.

This is different from the normal Settings editor.

The Settings section exposes configuration fields managed through the Control Center.

The Open function can launch a plugin's own dedicated interface.

The available functions, design and permissions of that embedded interface remain the responsibility of the respective plugin.

Installing the Plugin Control Center does not automatically add dedicated interfaces to every installed plugin.

12. Manual Configuration

You can still configure plugins manually when required.

Plugin configuration files are generally stored under:

oxide/config/

Example:

oxide/config/ExamplePlugin.json

The Control Center does not replace the underlying configuration files.

When using the CC Settings editor, the changed values are written back into the plugin's normal JSON configuration.

This means your configuration remains available even after a server restart.

Manual editing can still be useful for:

• Advanced configuration

• Settings that are not exposed by an adapter

• Complex configuration structures

• Troubleshooting

• Bulk editing

JSON files must remain syntactically valid.

A missing quotation mark, bracket or comma may prevent the plugin from reading the configuration correctly.

13. Backups

The Control Center does not create automatic configuration backups or maintain a configuration version history.

Before performing major changes, it is recommended to back up relevant files.

Typical locations include:

oxide/plugins/PluginName.cs

oxide/config/PluginName.json

oxide/data/PluginName/

The exact files used depend on the individual plugin.

14. Plugin Commands

The Control Center includes a command reference for detected plugin commands.

The overview separates:

• Chat commands

• Console commands

Detected main commands and subcommands may also be identified.

This is intended as a reference tool.

It is not a universal command editor or automatic command execution interface.

Commands that are generated dynamically at runtime may not always appear in the detected list.

15. Player Management

The Players section provides information and administrative tools for players known to the server.

The interface can display online players and, where available, known offline players.

Depending on available player information, the CC may display:

• Player name

• Steam ID

• Online or offline state

• Rust authorization group

• Last known activity

• World position

• Map grid

• Health

• Calories

• Hydration

• Temperature

• Comfort

• Wetness

• Bleeding

• Radiation

Some information requires an active player entity and is therefore only available for currently connected players.

16. Player Actions

For online players, the Control Center provides several direct administrative actions.

These include:

• Kick

• Ban

• Clear inventory

• Reset metabolism

• Unlock blueprints

• Reset blueprints

• Apply 25%, 50% or 75% damage based on current health

• Heal 25%, 50%, 75% or 100% of maximum health

• Kill player

• Teleport yourself to the player

• Teleport the player to you

• Open the player's permission view

Known offline players can also be accessed for selected functions such as banning and permission management.

The Banlist provides an overview of existing bans and allows administrators to remove bans.

17. Permissions

The Control Center contains its own graphical permission management section.

Registered Oxide permissions can be viewed and changed directly from the interface.

Permissions can be managed for:

• Individual players

• Groups

The interface distinguishes between:

DIRECT

The permission has been assigned directly to the player or group.

INHERIT

The permission is inherited through group membership or group inheritance.

OFF

The permission is currently not granted.

This distinction is important.

Removing a directly assigned permission does not automatically remove the same permission if the player still inherits it through a group.

18. Groups

The Groups section allows Oxide groups and group memberships to be managed directly from the Control Center.

Available functions include:

• View existing groups

• View group members

• Create groups

• Add players to groups

• Remove players from groups

• Include known offline players in player selection

• Delete groups with confirmation

The standard groups:

default

and:

admin

are protected from deletion through this function.

The CC also provides a Pre-Wipe Cleanup function for removing selected group memberships belonging to players whose recorded last connection predates the current wipe.

This removes memberships from the selected group.

It does not delete player accounts or player files.

19. Give – Item Distribution

The Give section provides a graphical interface for giving Rust items to players.

Items are displayed with icons and English display names.

Available functions include:

• Item categories

• All-items overview

• Item search

• Player selection

• Give item to yourself

• Give item to a selected online player

• Give item to all online players

• Quick amounts of 1, 100 and 1,000

• Blueprint distribution for suitable craftable items

The item search can also be opened using:

/ccsearch SEARCHTERM

or:

/ccs SEARCHTERM

Not every internal Rust item is displayed.

Hidden or explicitly excluded items are filtered from the interface.

20. Server ConVars

The Control Center provides access to Rust server variables exposed as ServerAdmin ConVars.

The interface allows administrators to:

• Browse available ConVars

• Search by name

• Search available descriptions

• View current values

• Enter new values

• Apply values directly as server console actions

This provides convenient access to many server settings without requiring a separate RCON interface.

However, the ConVar page is not a general RCON console.

Whether a changed value persists after a restart depends on the individual Rust ConVar and your server configuration.

21. Control Center Access

The Plugin Control Center includes separate permissions for its different administrative areas.

Rust server administrators are automatically allowed through the Control Center access check and do not require an additional CC permission assignment.

For non-admin users, permissions can be assigned according to the responsibilities they should have.

For example, a trusted non-admin who should manage plugin configurations through the normal plugin overview requires:

plugincontrolcenter.use

plugincontrolcenter.plugins

plugincontrolcenter.settings

Please note that plugincontrolcenter.plugins also allows plugin lifecycle operations such as loading, unloading and reloading plugins.

Only grant administrative permissions to trusted users.

Permissions, groups and ConVars in particular can significantly affect server operation.

22. Permission System Mode

The Control Center configuration includes:

Use permission system

By default this is enabled.

When enabled, access can be granted to:

• Rust administrators

• Properly permissioned users

When disabled, Control Center access is restricted to Rust administrators.

Disabling the permission system does not make the Control Center available to everyone.

23. Updating a Buzzta Plugin

When a new plugin version is released:

1. Download the updated .cs file.

2. Replace the existing plugin file inside:

oxide/plugins/

3. Allow Oxide to reload the updated plugin.

If the Plugin Control Center is installed, the plugin's current status can then be checked from the Plugins page.

Unless specifically stated in the update instructions, do not delete existing configuration or data files.

Existing configuration is normally intended to remain available after an update.

Creating a backup before larger updates is still recommended.

24. Removing a Plugin

To remove a plugin, delete its .cs file from:

oxide/plugins/

If you only remove the plugin file, existing configuration and data files normally remain on the server.

This can be useful if you plan to reinstall the plugin later.

For a complete removal, the corresponding files under locations such as:

oxide/config/

and:

oxide/data/

may also need to be removed.

Deleting configuration or data may permanently remove stored settings or plugin information.

Create a backup first if the data may still be required.

25. Typical Buzzta Plugin Workflow

For most Buzzta Plugins, the recommended workflow is:

1. Install Oxide on your Rust server.

2. Upload the purchased Buzzta Plugin to oxide/plugins/.

3. Verify that the plugin loads successfully.

4. Install PluginControlCenter.cs if you want to use central in-game administration.

5. Join your Rust server.

6. Open the Control Center with /cc.

7. Open the Plugins section.

8. Check whether the required plugin is loaded.

9. Use Commands if you want to review detected plugin commands.

10. Open Settings when configuration support is available.

11. Change the required values.

12. Choose either Save or Save + Reload.

13. If supported, use Open to access the plugin's own interface.

14. Use the remaining Control Center sections for player, permission, group, item or ConVar administration when required.

For everyday administration, this keeps many frequently used server management functions in one interface while still preserving the normal Oxide configuration structure underneath.

26. Troubleshooting

The Plugin Does Not Appear

Make sure the plugin .cs file exists inside:

oxide/plugins/

Also check that Oxide successfully compiled and loaded the plugin.

A plugin that failed to compile may still exist as a file but cannot operate normally.

The Plugin Is Listed as Unloaded

Open the Plugins section and use Load if available.

If loading fails, check the server console for the actual compilation or runtime error.

Settings Are Not Available

Not every plugin or every configuration value can automatically be represented in the Settings editor.

Settings may be provided through:

• A built-in adapter

• An external adapter

• A plugin-provided schema

• Automatic JSON configuration detection

Complex settings may still require manual configuration.

A Setting Was Saved but Has Not Taken Effect

If you used Save, the configuration file has been updated, but the target plugin may not automatically re-read it.

Use Save + Reload if the setting requires a reload.

The Plugin Has No Open Button

The Open function is only available when an appropriate integration or opening action exists.

A plugin can provide configurable Settings without having its own dedicated embedded UI.

The Control Center Does Not Open

Try:

/cc

or:

/controlcenter

If you are not a Rust administrator, make sure the necessary permissions have been assigned.

General access requires:

plugincontrolcenter.use

Additional permissions are required for the individual administrative sections.

Configuration Errors

If a manually edited JSON file is invalid, the plugin may fail to read it correctly.

Restore a backup when available.

Deleting a configuration file may cause some plugins to regenerate their default configuration, but this also removes your previous settings.

Only do this when you understand the consequences.

27. Support Information

When contacting Buzzta Plugins Support, please provide as much relevant information as possible.

Useful information includes:

• Plugin name

• Plugin version

• Rust server version

• Oxide version

• Relevant console error

• Description of the problem

• Steps required to reproduce the issue

• Whether the setting was changed manually or through the Plugin Control Center

For errors, please include the complete relevant console message whenever possible.

This makes it considerably easier to identify whether the problem originates from the plugin, its configuration, Oxide or another server component.