Skip to content
← All documentation

/// PIMPMYRUST PLUGIN

Item Creator

This plugin is coming soon. This guide covers the release in preparation; its configurator and downloads are not available yet.

Settings guide for this version of Item Creator. Check the plugin page before using it on your server.

Version
0.1.0
Framework
oxide, carbon
Main file
oxide/config/ItemCreator.json
Plugin page →

Settings for this version

General 11
EnablePlayerCatalog
On / off · required
JSON pathEnablePlayerCatalog
EnableRuntimeEvents
On / off · required
JSON pathEnableRuntimeEvents
Locale
Text · required
JSON pathLocale
MaxApiReceipts
Whole number · required
JSON pathMaxApiReceipts

Minimum : 100 · Maximum : 10000

MaxQueuedPerPlayer
Whole number · required
JSON pathMaxQueuedPerPlayer

Minimum : 1 · Maximum : 10

MaxScheduledEvents
Whole number · required
JSON pathMaxScheduledEvents

Minimum : 100 · Maximum : 10000

PlayerCatalogTemplate
Choice · required
JSON pathPlayerCatalogTemplate

Allowed values: industrial-command, arctic-signal, field-dossier

PlayerCatalogVisualMode
Choice · required
JSON pathPlayerCatalogVisualMode

Allowed values: light, rich

RequireGiveCapability
On / off · required
JSON pathRequireGiveCapability
ShowTechnicalDetails
On / off · required
JSON pathShowTechnicalDetails
TerminalCraftRetentionHours
Whole number · required
JSON pathTerminalCraftRetentionHours

Minimum : 1 · Maximum : 720

Plugin instructions

ItemCreator configuration contract 1.0.0

The plugin configuration is oxide/config/ItemCreator.json. It controls the player catalogue, runtime-event processing, limits and UI profile. Item definitions are a separate data document at oxide/data/ItemCreator/catalog.json; this bundle does not edit that catalogue.

Choose PlayerCatalogTemplate from industrial-command, arctic-signal or field-dossier and PlayerCatalogVisualMode from light or rich. CuiDocument is an optional PimpMyCUI runtime document edited from that exact built-in profile. Omit it or set null for the built-in document. A non-null incompatible document blocks the player catalogue UI without fallback; item processing remains separate.

The editor may change visuals, add decorative elements or close-only buttons, and remove elements. Existing action elements must retain their IDs, kind and bindings; model paths must come from the built-in document. Export the complete ItemCreator.json; installing only a PimpMyCUI project/package does not change this consumer. This first contract has no earlier Hub configuration migration.