Skinbox

Features

• Easy-to-use skin selection system for Rust items and deployable objects.
• Opens a private virtual SkinBox container for every authorized player.
• Insert an item and browse all available skins through paginated previews.
• Applies the selected skin while preserving the original item.
• Safely handles weapons, magazines, ammunition, and attached modifications.
• Includes protection against container and attachment-related item exploits.
• Configurable commands, container capacity, panel type, colors, buttons, and UI positioning.
• Supports global skins as well as permission-restricted skin collections.
• Individual skins can be enabled or disabled without deleting them from the catalog.
• Automatic workshop catalog synchronization through ImageLibrary.
• Visual administration interface with item previews, skin IDs, and activation status.
• Add or remove skins through commands or manage them from the graphical interface.
• Special SkinBox Spray Can for reskinning already deployed objects.
• Spray Can targeting requires building privilege and validates the selected deployable.
• Supports standard skins, workshop skins, and dynamically supplied skins through API hooks.
• Provides enabled skin data to compatible plugins such as BKits.
• English and German administrative interface.
• Full Plugin Control Center embedding and settings integration.

Chat Commands

Command / Description

/skinbox → Opens the SkinBox container.

/sb → Short alias for /skinbox.

/skinbox show → Opens the SkinBox container explicitly.

/skinbox get → Displays the shortname and current skin ID of the equipped item.

/skinbox purgecache → Clears the player’s cached skin results.

/skinbox admin → Opens the visual skin-management interface.

/skinbox manage → Alias for /skinbox admin.

/skinbox refresh → Synchronizes the available skin catalog with ImageLibrary.

/skinbox sync → Alias for /skinbox refresh.

/skinbox add <shortname> <skin ID> [permission] → Adds a skin to the specified item. An optional permission can restrict access to that skin.

/skinbox remove <shortname> <skin ID> [permission] → Removes a skin from the specified item or permission collection.

/skincan → Gives the authorized player a special SkinBox Spray Can for reskinning deployed objects.

Permissions

skinbox.use – Grants access to the standard SkinBox container and its player commands.

skinbox.admin – Grants access to catalog synchronization, skin administration, and the visual management interface.

skinbox.skincan – Grants access to the special SkinBox Spray Can.

Additional custom permissions can be assigned to individual skin collections in the configuration. Players only see restricted skins when they possess the corresponding permission.

Rust administrators automatically receive administrative access. When the permission system is disabled, all players may use the regular SkinBox and Spray Can, while administrative tools remain restricted to Rust administrators and the server console.

Usage

Enter /skinbox or /sb to open your private SkinBox container.

Move the item you want to reskin into the SkinBox. The plugin generates the available skin variants and displays them across the container’s pages. Use the Previous and Next controls to browse additional skins.

Select the desired appearance by taking the corresponding item preview. SkinBox applies the selected skin and returns the item while preserving its relevant contents, magazine, ammunition, and attachments.

Use /skinbox get while holding an item to retrieve its shortname and current skin ID.

Administrators can enter /skinbox admin to browse supported items and enable or disable individual skins. New workshop skins can be synchronized through /skinbox refresh when ImageLibrary is installed.

To reskin a deployed object, enter /skincan, equip the special Spray Can, aim at a supported object within range, and press the primary fire button. Select the desired skin from the displayed catalog. The player must have building privilege at the target location.

Required Files and Setup

Skinbox.cs

Upload the plugin to oxide/plugins/.

Skinbox.json — Included in the Package

The package includes the prepared configuration with skin collections and the current plugin settings. Upload it to oxide/config/.

When updating an existing installation, preserve your server-specific settings, permissions, and any previously configured Steam Web API key.

PlayerDLCAPI

PlayerDLCAPI is required for skin ownership checks for regular players. Upload PlayerDLCAPI.cs to oxide/plugins/. A copy is included in the prepared SkinBox installation package.

Without an initialized PlayerDLCAPI, regular players can only use the default skin.

ImageLibrary

ImageLibrary is used to load and cache skin preview images. It is available from the uMod plugin directory. Upload ImageLibrary.cs to oxide/plugins/ if it is not already installed.

Steam Web API Key

Automatic public Workshop synchronization requires a Steam Web API key supplied by the server operator. Obtain it through Steam Community’s Web API key registration page.

Provide the key using either of these methods:

• Set the Rust server process environment variable SKINBOX_STEAM_WEB_API_KEY, then restart the server.
• Enter the key under Workshop Catalog → Steam Web API Key in Skinbox.json.

Keep your key private and do not include it in publicly distributed files.

Automatically Generated Data

SkinBox creates oxide/data/Skinbox/workshop_catalog.json after the first successful Workshop synchronization. You do not need to upload this file manually.

No separate skin image pack or Buzzta logo file is required. Preview images are retrieved when needed, and the logo is embedded in the plugin.