Objectives

An objective is a single goal inside a contract: kill an animal, craft an item, hack a crate. A contract needs at least one. The type field selects which objective it is and which fields it carries. Each per-type page in this section lists its complete field set, shared and type-specific alike.

Every objective shares title, description and a conditions map (a keyed map, not an array) of optional conditions that restrict when progress counts. Progress ticks only when the objective’s main requirement and every attached condition are met.

Objectives also share an optional hideDetails flag (default false). The menu normally renders an objective’s fields and conditions for players (the objective display). Setting hideDetails: true suppresses that for the objective, leaving your title and description as the only explanation players get.

Technical note

At the moment, all objective types are amount-based, meaning they require a certain quantity of something to be completed and have a amountRequired field. That being said, that field is not anchored into the base shape of an objective, it just so happens that all objective types currently derive from an abstract AmountObjective type. It’s also why the docs don’t assume that amountRequired is a base field, like title and description are. The objective shape is designed to accommodate other types of non-amount-based objectives in the future, should one surface.

Item and entity lists

Fields that take items (items, item, fish, bait) or entities (entities) use Rust shortnames / prefab names, lowercase: rifle.ak, scrap, animal_bear, not display names. One exception: the entities list on Kill and Damage also matches the display names of custom NPCs from plugins like BetterNpc or NpcSpawn.

Any item/entity list also accepts preset references written as @presetName. At runtime the plugin expands the reference into that preset’s list, so you can define a list (e.g. all rifles) once and reuse it. Invalid shortnames are dropped when the config loads.

Objective conditions

Contracts’ strength comes from the versatility and possibilities of how objectives can be augmented with conditions. The same objective with no condition can be given a whole new flavor and level of difficulty when you add conditions to it.

ConditionsOptional rules that restrict when progress counts, for example 'only at night', or 'only with a specific weapon'.

Pacing

Amount-based objectives can optionally shape how progress adds up over time:

CooldownLimit how fast progress adds up: at most X units in any sliding window.

BurstRequire actions to arrive clustered: X units within one window form a burst, and the objective counts bursts.

Objective types

Card SwipeSwipe puzzle keycards in monument card readers.

CloningTake clones (cuttings) from specified plants.

CookSmelt, refine or cook specified items in ovens.

CraftCreate specified items.

Crate HackHack hackable locked crates.

DamageInflict damage on specified entities.

FishingCatch specified fish using specific bait.

GambleWager scrap at Rust's gambling games, counting bets won, lost, played, or the scrap they moved.

GatherCollect items from dispensers, like trees and ore nodes.

HarvestHarvest plants from planters or the world.

HealRestore an amount of health.

KillEliminate specified entities.

LootObtain items from the world or world containers.

MixMix specified items at a mixing table or cooking workbench.

PlantPlant specified seeds.

PlaytimeSpend time connected, alive and awake, measured in minutes of play.

RecycleRecycle specified items, counting either what goes into the recycler or what comes out.

RepairRepair items at a bench, or restore HP to structures, deployables and vehicles with the hammer.

TravelCover distance across the world by any means, measured in meters of 3D displacement.

Turn InSubmit items to the plugin.

VisitArrive at monuments. Each arrival from fully outside counts once.