Configuration

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

How Configuration Is Stored

oxide-pills 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).

How it works:

1. The first time the resource starts, the values from the config files are copied into oxide_settings. If you edited those files before that first start, your edits are what gets copied.
2. From then on, the database is what the resource reads. Settings you save in the menu are stored there and win over the files. Editing a config file on a server that has already started once will not change a setting that's stored in the database.

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. The easier path is to start 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).
• 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 /pills settings in game. It opens an editor for the settings. Changes apply live and are saved to the database right away, with no restart.

• Settings are grouped into a sidebar of four categories: Core, Lab, Players, and Advanced, holding 12 sections between them.
• A Basic / Advanced switch at the top of the menu picks which settings you see, and the search box searches the settings on that side. Three sections (Usage Whitelist, Quality, Dispatch) only have Advanced settings, so they only appear in the sidebar once you switch to Advanced.
• A setting you've edited but not saved yet is marked changed. Save Changes saves everything you've edited.
• Reset to default puts a setting back to its factory value from the config files and saves it straight away. It resets the whole setting: resetting Pharma delivery run, for example, also puts back the contact and the drop points.
• The in-world placement zones are drawn directly in the world: the menu hides, you place the corners of the area, then the menu comes back. Each zone also has a Teleport button.
• Item fields have a picker that lists the items your inventory knows about.

Almost every change takes effect the moment you save. The exceptions:

• Changing the workbench's model or slot count only affects workbenches placed afterwards.
• Changing a model replacement rebuilds the placed stations for everyone.

Developers can also read and write settings from another resource. See API Reference.

Settings That Aren't In The Menu

The menu covers everything most servers want to change. A few settings, mostly lists and layouts that a form can't show well, live only in the config files. They come in two kinds, and the difference matters:

1. Config file only: always read from the file. These are never stored in the database, so the config file always wins:

• Config.Skill (how much each level reveals) in shared/config/profile.lua
• Config.Buyers (the street buyer types) in shared/config/world.lua
• Config.SettingsCommand (the command named in missing-model warnings, '/pills settings') in shared/config/models.lua

To change one: edit the file, save it, and restart the server.

2. Not in the menu, but part of a section that is. Some settings sit inside a section the menu does show, but aren't shown themselves. For example, the product line recipes are part of "Product line unlocks", and the bottle label templates are part of "Packaging". They're marked (not in menu) in the tables below. Only the values the menu shows are taken from the database; these are read from the config file on every start.

To change one: edit the file, save it, and restart the server.

The Config Files

Core

General

Placement Zones

Zones apply to workbenches and floor machines. Benchtop machines sit on a workbench, so they go wherever the workbench is.

Usage Whitelist

(Advanced tab.)

Each rule:

A player passes if they match on the job side or the gang side. The rules cover items used from the inventory: station items, the mortar, the sieve, the dust mask, the reagent kit, the Pressing Manual, and every pill, loose or packed.

Lab

Workbench

Config.Workbench (menu: Lab workbench).

Changing the model or slot count only affects workbenches placed afterwards. Workbenches already standing keep the model and slots they were placed with.

Machines

Config.Equipment (menu: Placeable machines). One entry per machine:

• item: the inventory item that places the machine. If you rename it, register the new name in your inventory too.
• requiredLevel: the pill level needed to place the machine and to work it, including a machine someone else placed. It is the only level a machine has. Mixing a product line also needs that line's own level (Formulas).
• facingOffset (not set by default): turns a floor machine by this many degrees when placed. Benchtop machines always face the way their workbench does.
• machine and mount (not in menu) tie the entry to its model and decide bench or floor. Don't change them.

Production

All of these are under Lab → Production in the menu. A stage worked on a machine needs that machine's level, set under Machines. Only the stages with no machine of their own have a level here: bagging at the workbench and the sieve in the menu, and the mortar in the config file only.

Milling

Config.Mill (menu: Milling).

inputs lists party_powder, pharma_bottle, mystery_powder and pill_rejects (marked regrind = true), each with the container model the grinder shows (the stock ones use oxide_pill_powder_pouch). You can add another raw active here (for example an oxy item from another script), but it's only useful if a formula in Config.Formulas accepts it.

Mortar (tools.mortar):

Blade grinder (tools.grinder):

Blending

Config.Blend (menu: Blending).

The locale file already has names for dye_orange and dye_teal if you want to add those colours.

Pressing

Config.Press (menu: Pressing).

In the menu, pendingDays is labelled Keep an abandoned tray for.

stations (not in menu):

Sorting

Config.Sort (menu: Sorting).

Inspecting

Config.Inspect (menu: Inspecting).

Engraving

Config.Engrave (menu: Engraving).

Packaging

Config.Packaging (menu: Packaging).

bottle.labels (not in menu): players pick from these when filling bottles, so a bottle can only claim what you wrote here. Each has a key, a name and directions.

A line in bottle.lines with no templates can't be bottled.

Granulating (sieve)

Config.Granulate (menu: Granulating (sieve)).

What granulating is worth is set under Quality (Granulation).

Drum tumbler

Config.Tumble (menu: Drum tumbler).

Ball mill

Config.BallMill (menu: Ball mill).

Hardness tester

Config.Hardness (menu: Hardness tester).

Pan coater

Config.Coat (menu: Pan coater).

Capsule board

Config.Capsule (menu: Capsule board). The level to use the board is the Capsule Filling Board's under Machines, and capsules also need the capsule line's level (Formulas).

Rotary press (crew)

Config.Rotary (menu: Rotary press (crew)). Starting a run as the feeder needs the Rotary Press's level under Machines. Crew who join a run don't need it.

Stage animations and cameras

(Advanced tab.)

• Config.SceneAnims (menu: Stage animations): what other players see your character doing while you're inside a stage. The stage camera is only on your screen, so without these your character would stand frozen at the bench. Each stage (mill, blend, press, engrave, printer, sealer, bagging, granulate, hardness, ballmill, tumble, coat, rotary, reagent) has a dict, clip and flag.
• Config.SceneCameras (menu: Stage cameras): where the camera sits for each stage and what it frames. Each has an offset (from the station: -Y is in front, +Z is up), a lookAt point and a fov. The press, electric press, capsule board and mixer also have extra shots (over the tray, on the die, while mixing) and an ease time. Change these live, walk into the stage, and adjust until the whole working area is in shot.

Keep unchecked batches for

(Advanced tab.)

Formulas

Config.Formulas in shared/config/production.lua defines the five product lines. Only each line's requiredLevel is in the menu, under Players → Progression → Product line unlocks. Everything else here is (not in menu) and read from the file on every start.

• requiredLevel is the level to make that line (mix it, and cut a die for it).
• accepts is which raw actives' milled powder the line takes.
• stamps is what the engraver may put on the line's dies: plain (a blank face), ref (the line's reference imprint) or brand (a player brand).
• pourable lists what can go in the bowl (milled powder, filler, binder, lubricant, and dye for party pills).
• packed names the item each packing turns the line's pills into, for NOVA Bars packed = { baggie = 'bar_pill_bag', bottle = 'bar_pill_bottle', blister = 'bar_pill_blister' }. Party pills and capsules have no bottle, since they can't be bottled. If you let a line into a packing it has no item for, its packed pills stay the loose item.

Quality

Config.Profile (menu: Lab → Quality → Tablet Profile, Advanced tab). This is what makes a good tablet. Every "window" is a target range, not a maximum: going over costs as much as falling short.

Lines (not in menu) overrides the base values for one product line:

Skill (file only)

Config.Skill.Reveal in shared/config/profile.lua maps each level to how much the gauges and readings show: 'zones' (words, no numbers), 'values' (exact numbers) or 'preview' (numbers, plus each tablet's defect called out and the fuller light-box reading). Defaults: levels 1–2 zones, 3–5 values, 6–10 preview. It's always read from the file: edit it and restart.

Players

World

All under Players → World.

Pills breaking

Config.Decay (menu: Pills breaking).

How much packing protects is set under Packaging (protection).

Dust

Config.Dust (menu: Dust).

Taking pills

Config.Consume (menu: Taking pills).

lines (not in menu): party and capsule are euphoria for 240 s; bar is sedated for 300 s; blues is opioid for 300 s; perc is opioid for 240 s. Lengths are for a batch in the middle of its potency window.

effects (not in menu):

Stress changes need a framework with a stress system (QBCore and QBX; ESX has none).

Reagent testing

Config.Reagent (menu: Reagent testing).

mystery (not in menu): each lot is rolled once from these, by weight.

Police evidence

Config.Evidence (menu: Police evidence).

Selling

All under Players → Selling.

Brand reputation

Config.Reputation (menu: Brand reputation).

Pharma delivery run

Config.Delivery (menu: Pharma delivery run).

The 7 default doorsteps are vec3(772.54, -152.31, 74.42), vec3(839.75, -181.45, 74.18), vec3(920.87, -238.29, 70.17), vec3(1060.83, -378.49, 68.22), vec3(1099.41, -438.71, 67.78), vec3(1207.42, -620.35, 66.43) and vec3(525.93, 207.16, 104.73).

The contact has no map blip, and is stood on the ground wherever you put them, so the height only needs to be close. A moved contact appears at the new spot within a couple of seconds for anyone nearby.

Police alerts for handoffs are set under Dispatch (the Delivery handoff stage).

Laundering

Players → Selling → Pharma delivery run → Laundering → Dirty money is decides where the dirty money comes from:

Each drop takes up to perDrop dollars of it and pays back clean cash. With bills, the biggest bills go first and any change comes back as one new bill. If the player has none, the laundering step does nothing and the drop still pays its normal cash. To switch laundering off entirely, turn off Laundering → Enabled.

Buyers (file only)

Config.Buyers in shared/config/world.lua defines the four street buyer types used for oxide-drugselling sales. It's always read from the file: edit it and restart. Each archetype has:

The default values for each type are in Features. The delivery run pays by the pharma type.

Progression

Config.Progression (menu: Players → Progression).

Levels (in the menu)

Levels must go up in order. If you add levels beyond 10, also look at Config.Skill (above) so the new levels reveal what you want.

XP rewards (in the menu)

Config.Progression.xpRewards (menu: XP per stage):

Inspecting, hardness tests and reagent tests pay nothing on purpose: they already cost tablets. Rotary press and delivery XP are set in their own sections (Config.Rotary.xp, Config.Delivery.xpPerDrop). XP for street sales is set in oxide-drugselling.

Product line unlocks (in the menu)

The level needed to mix each product line (Config.Formulas.<line>.requiredLevel, see Formulas):

A line also needs its machines: capsules need the Capsule Filling Board, for example, whose level is set under Machines.

Perks (not in menu)

Config.Progression.perks:

Advanced

Dispatch

Config.Dispatch (menu: Advanced → Dispatch → Police alerts, Advanced tab). Production is risk-free out of the box.

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

The stages you can tune separately are mill, blend, press, package (baggies), bottle, blister, granulate, tumble, ballmill, coat, rotary and delivery (a delivery run handoff, labelled Delivery handoff in the menu). A common setup is to leave the master chance low and raise just the press.

What "chance" means in practice: it's rolled when a stage is started, not per batch finished. After a station alerts, it doesn't alert again until the Site cooldown has passed. So with the defaults, each station sends at most one alert every 5 minutes, however many times players start stages on it. A roll that doesn't alert leaves the station free to roll again on the next stage.

Delivery handoffs alert where the player hands over the card (within a few metres of the doorstep), with their own wording (stageAlerts, above). Their cooldown is per player rather than per station. Like every other stage they follow the master Alert chance unless you set Delivery handoff yourself, so with the defaults they're off.

What you need installed

Alerts go through whatever dispatch resource you run, as long as o-link supports it: ps-dispatch, cd_dispatch, qs_dispatch, lb-tablet, oxide-dispatch, tk_dispatch, fd_dispatch, emergencydispatch, linden_outlawalert, origen_police, bub-mdt, kartik-mdt, redutzu-mdt, wasabi_mdt and piotreq_gpt.

Without one, the fallback is basic. Players with the alert job get a short notification ([10-15] plus the message; the title isn't shown) and a map blip on the station that disappears after 30 seconds.

If nobody with the alert job is online, the alert is dropped. That's on purpose: there's no queue of old calls waiting for the first officer to log in. (oxide-dispatch is the exception: it records the call whether or not anyone is online.)

Compatibility

Config.ModelSwaps (menu: Advanced → Compatibility → Model replacements).

For example, to replace the workbench table with a different base-game table (add the row in the menu on a server that has already started once):

Config.ModelSwaps = {
    { from = 'bkr_prop_weed_table_01b', to = 'prop_table_03' },
}

Every pill station and tablet model ships in this resource's stream/ folder, so a warning about one of those means the install is incomplete (the folder is missing or damaged), not an old game build. Re-copy the resource. The warning tells you which case it is.

Next Steps

• Installation
• Features
• Admin
• Troubleshooting