Commands

Contracts is driven mostly from its in-game menu, but a few commands let players tweak their view and let admins manage rotations and troubleshoot.

Players type the chat command in chat. Admins run console commands from the server console (RCON) or the F1 client console. The chat command name is configurable; this page uses the default contracts (see Command Configuration). Admin and debug commands require the contracts.admin permission (see Permissions Configuration).

In the tables below, <angle brackets> mark required arguments and [square brackets] optional ones.

Search commands

Player commands

Available to anyone with the contracts.use permission. Type them in chat.

Command	Arguments	Description
/contracts	—	Opens the Contracts menu.
/contracts hud	—	Toggles the on-screen HUD on or off.
/contracts scale	[amount]	Adjusts the plugin’s UI scale for the player. amount should be between 0.5 and 1.0 (default). Players should set this to their Rust UI scale.

Admin commands

Require the contracts.admin permission. Run them from the server console or the F1 console.

Command	Arguments	Description
contracts.rotate_category	<categoryId>	Immediately re-rolls one category’s active contracts and reschedules its next rotation.
contracts.reset_all_progress	—	Wipes every player’s contract progress and all unclaimed rewards. Cannot be undone!

Debug commands

Also require contracts.admin. These are for troubleshooting and support; you won’t need them in normal operation. Output prints to the console you run them from.

Command	Arguments	Description
contracts.debug.hooks	—	Lists every game hook Contracts uses and whether it is currently subscribed or not. Contracts automatically unsubscribes from hooks when no active contract’s objective needs it.
contracts.debug.reset_data	<yes>	Resets all plugin data (contracts, categories, presets, progress, preferences, pending rewards) to defaults, then reloads the plugin. You must pass the literal yes to confirm. Cannot be undone!
contracts.debug.refresh.all	—	Rebuilds every objective cache from the current data.
contracts.debug.tainted_items	—	Prints how many items are flagged as tainted in the loot objective cache. This usually stays under 1000. Clear if it exceeds 100k (never happens in practice).
contracts.debug.clear_tainted_items	—	Clears the tainted-item set from the loot objective cache.
contracts.debug.transfers	—	Prints how many in-flight item transfers are tracked in the loot objective cache. Transfers should typically be completed within a single tick. It should ideally be 0 all the time.
contracts.debug.clear_transfers	—	Clears tracked item transfers from the loot objective cache. You can usually safely run this, because it’s unlikely you’ll clear any active transfers.

Cache inspection

Each objective type keeps a cache for fast objective progress lookups on high-frequency game events. These commands dump the contents of one cache (or all of them) to the console for diagnosis. You will likely never need to run these. They’re only documented here for completeness and for support purposes.

Command	Arguments	Description
contracts.debug.cache.all	—	Dumps every objective cache.
contracts.debug.cache.attackers	—	Dumps the attackers cache.
contracts.debug.cache.kill	—	Dumps the kill objective cache.
contracts.debug.cache.damage	—	Dumps the damage objective cache.
contracts.debug.cache.loot	—	Dumps the loot objective cache.
contracts.debug.cache.gather	—	Dumps the gather objective cache.
contracts.debug.cache.harvest	—	Dumps the harvest objective cache.
contracts.debug.cache.craft	—	Dumps the craft objective cache.
contracts.debug.cache.heal	—	Dumps the heal objective cache.
contracts.debug.cache.fishing	—	Dumps the fishing objective cache.
contracts.debug.cache.plant	—	Dumps the plant objective cache.
contracts.debug.cache.card_swipe	—	Dumps the card-swipe objective cache.
contracts.debug.cache.crate_hack	—	Dumps the crate-hack objective cache.