Configuration

oxide-cocaine is configured in-game, from a settings menu — you don't edit script files on a running server. This guide explains how that works, then lists every setting so you know what each one does.

How Configuration Is Stored

oxide-cocaine keeps its live configuration in your database, in a shared table called oxide_settings. The shared/config.lua file and the files in shared/config/ are the factory defaults — the starting values the resource ships with. The table is created automatically on first start (you don't run any SQL by hand).

The flow:

1. The first time the resource starts, every value from the config files is copied into oxide_settings. If you're upgrading and had customized those files, your customizations are copied in as-is — nothing is lost.
2. From then on, the database is what the resource reads. The config files were only the defaults it filled the table from that first time. Editing them on a server that has already started once will not change anything.

What this means for you:

• Setting up for the very first time? You can edit the config files before the first start, and your values will be imported. But the easier path is to start the resource with the defaults and adjust everything in-game.
• Changing a setting on a server that has already run the resource? Use the in-game settings menu (below). Editing the file does nothing at that point.
• A resource update adds new settings? Those aren't in your database yet, so they come from the updated config file automatically on the next start — no action needed.

The in-game settings menu

As an admin, run /cocaine settings in-game. This opens an editor for every setting. Changes apply live and are saved to the database immediately — no restart.

• Settings are grouped into a sidebar of four categories — Core, Production, World, and Players — holding 12 sections in total (listed below).
• Each section has a Basic tab (the common settings) and an Advanced tab (fine-tuning), plus a search box.
• Every field shows whether it's been changed, and has a Reset to default button that restores that setting's factory value (the value from the config files).
• The in-world zones (placement zones and wild-plant spawn zones) are drawn directly in the world: the menu hides, you place the polygon points, then the menu returns. Each zone also has a Teleport button.
• Model fields accept either a prop model name (like prop_pot_03) or a hash number. Names are converted to a number when you save, so a model you typed by name will show as a number afterward — that's normal.
• Item fields have a browse button that opens a searchable catalog of your framework's items, with icons, so you don't have to type item names by hand.

Most changes take effect the moment you save. A few need a brief rebuild that the resource does for you: changing station props or their positions respawns the placed stations for everyone within a few seconds, and changing wild-plant settings respawns the bushes.

Developers can also read and write settings from another resource — see Exports.

The Config Files (factory defaults)

These files hold the defaults imported into the database on first start. They're worth reading as a reference for what each setting means, but the settings menu is how you change a running server.

Core

General

Police Alerts

Production is risk-free out of the box. To make it occasionally draw police, open the Dispatch section (under Core, on the Advanced tab).

When a player starts a stage the server rolls once. On a hit, a dispatch call goes out at the station's location — not the player's, so a suspect can't fake or move it.

The four stages you can tune separately are Stomp, Cook, Press and Package. A common setup is to leave the master chance low and raise just the cook, since that's the loudest part of the operation.

What "chance" means in practice. It's rolled per stage started, not per batch finished. A player who starts, cancels, and restarts rolls twice — but the site cooldown means only the first can actually alert.

What you need installed

Alerts go through whatever dispatch resource you run. Most are supported, including ps-dispatch, qs_dispatch, cd_dispatch, lb-tablet and the common MDTs. You don't strictly need one — with no dispatch resource installed, players with the alert job get a notification and a map blip instead.

If nobody with the alert job is online, the alert is discarded. That's intentional: there is no queue of stale calls waiting for the first officer to log in.

Equipment & Stations

The four placeable stations (Config.Equipment). Each entry sets the inventory item that places the station, the props that appear when placed, its offsets, and any level requirement.

requiredLevel is the cocaine level needed to place that station. Only the brick press has one by default (level 5); the other three have none. The pool uses a sphere zone for its walk-up menu (because you stand inside it), tuned by its targetRadius (1.6). Each station's objects list holds its props — you can add, remove, or nudge props (model, offset, rotation) right in the menu.

Production

Recipes

The item names and amounts each stage consumes and produces (Config.Items). If you rename an item here, remember to register the new name in your inventory too.

Bagging also consumes one empty bag per sealed bag. Which item that is comes from Config.Items.package.bagItem (default baggy). Whatever you set must be registered in your inventory.

Each stage also has a "server floor" (minTime) — an anti-cheat guard. The server rejects a stage that completes faster than its floor:

(The stomp has its own floor, Config.Stomp.minTime, listed under Stomping.)

You can change any input/output amount here. For example, raising Config.Items.press.inputCost makes bricks cost more cocaine.

Stomping

The pool stomp minigame (Config.Stomp).

The two additives poured before stomping (Alkali, then Water) are the additives list — each has a label and a pourTime (both 3000 ms by default). The models, pourProp, and per-additive particle blocks control how the props and streams look.

Extraction

The soak extractor (Config.Container)

World status labels (Config.Labels) (Advanced)

The styled panels that show over nearby extractors when the player holds the label key.

The remaining label settings (scaleNearDist, scaleFarDist, scaleMin, scaleMax, updateInterval) only affect how the labels scale and refresh, and rarely need changing.

Cooking

The stove cook minigame (Config.Cook). The interesting numbers for game balance:

The temperature ceiling that ruins the batch (100°C) is fixed in code. The rest of Config.Cook (camera framing, pour steps, pot prop, fire/smoke effects) controls how the cooking scene looks and rarely needs changing — though every part of it is editable in the menu, including the base "cocaine base" prop (baseProp), which is optional and simply skipped if its model isn't streamed on your server.

Adulterants

The cutting agents ("cuts") a player adds when cooking crack, and how they change the result. A crack cook must include at least one cut (and takes up to Config.Cut.maxAdulterants), so a player with no cutting agents can't make crack.

The cuts (Config.Adulterants)

Each entry is one cutting agent, keyed by its item name. The numbers that matter:

The eight cuts that ship, with their defaults:

Add, remove, or retune cuts freely in the menu. Each cut is also a real inventory item the player must hold and that gets used up when the batch finishes — these aren't sold anywhere by default, so decide how players source them. The remaining per-cut settings (offset, rotation, fx*, heatRateModifier, optimalRangeModifier) control how the pour looks and plays.

Cut rules (Config.Cut)

Packaging

The bagging minigame (Config.Packaging). The loop tuning:

The remaining settings (camera, prop models, spoon movement, drag feel) control how the scene looks.

Brick Press

The brick press (Config.Press). (This whole section is under the Advanced tab.)

The rest (mold props, animation clips, where the operator stands) controls how the press looks.

World

Wild Plants

Wild coca bushes that spawn in polygon zones around the map (Config.WildPlants).

Each zone has a name, its polygon shape (drawn in-world), a minZ/maxZ height band, and an optional plants count for how many bushes it holds (defaults to 5 if left off). Add zones with the zone tool in the menu.

Players

Progression

XP rewards (Config.Progression.xpRewards)

Wild bush harvest XP is set separately, under Wild Plants (harvestXP, default 10).

Levels (Config.Progression.levels)

Ten levels with these total-XP thresholds:

0, 100, 300, 650, 1200, 2000, 3200, 5000, 7500, 11000

Purity penalties (Config.Progression.purityPenalties)

How many points each level loses off every cook's purity score (skilled cooks lose less):

-30, -25, -20, -15, -10, -8, -5, -3, -1, 0

If you add a level, add a matching purity-penalty entry for it.

Usage & Effects

What happens when a player uses a bagged cocaine or crack item. Each product is defined under Config.Usage.products.

Cocaine (Config.Usage.products.cocaine)

Crack (Config.Usage.products.crack)

Effect toggles (Config.Usage.needsEffects)

Turn whole effect types on or off server-wide:

Purity multipliers (Config.Usage.purityMultipliers)

The grade on the bag scales the high's duration, intensity, and stress relief:

The screen-effect block (Config.Usage.screenEffects) sets the timecycle filter, camera shake, FOV boost, and intensity-pulse timing. The defaults are tuned for a stimulant feel and rarely need changing. The styles block sets the sniff/smoke animations and the held props (glass pipe, etc.).

Next Steps