Configuration

The config file controls how the plugin behaves: the command that opens the menu, permissions, the HUD, logging, and more. It is the only file Contracts uses that you edit by hand. The web editor manages your contracts, categories, and presets, but doesn’t support editing the config file (yet!).

Where it lives

Oxide

oxide/config/Contracts.json

Carbon

carbon/config/Contracts.json

After editing it, reload the plugin for changes to take effect:

Oxide

o.reload Contracts

Carbon

c.reload Contracts

Tip

If a value is invalid, the plugin does not crash: it logs a warning, falls back to the default, and keeps running. Watch the server console after a reload to catch typos.

The shape

The file has one block per section. The full shape looks like this, with each block detailed on its own page below:

{
  "Command": [ ... ],
  "Permissions": { ... },
  "Rewards": { ... },
  "Conditions": { ... },
  "HUD": { ... },
  "Logging": { ... },
  "Version": { ... }
}

Sections

Command The chat and console command(s) that open the Contracts menu.

Permissions The permissions that gate access to Contracts, and the per-permission contract limits.

Rewards Settings that affect how contract rewards are presented to players.

Conditions How the plugin orders condition checks when evaluating objective progress.

HUD Position and collapse behavior of the on-screen contract tracker.

Logging Turn on event logging, choose a format, and customize each event's log line.

Version

The Version block is written by the plugin to track which config format it last wrote. Leave it alone: it is managed automatically and is not a setting you tune. If you upgrade Contracts and the format changes, the plugin migrates the file and updates this stamp for you.