Admin Guide

Commands and tools for testing and managing oxide-meth.

Every command is now a subcommand of /meth. Typing /meth on its own shows the list of subcommands. (The old separate commands — /methkit, /meth_sellkit, /setmethlvl, /methstats — no longer exist; use the /meth versions below.)

Commands Overview

The Settings Editor (/meth settings)

This is the main way you configure oxide-meth. Every setting the resource has is edited here, in game, and your changes are saved in your database and applied straight away — no need to restart the server. (For the full explanation of how database-saved settings work, see Configuration.)

Opening it

Type /meth settings in the chat box while playing. A panel opens over the screen. Only admins can open it; a non-admin who tries gets a "No permission" message and nothing happens.

Finding your way around

• Categories down the side — settings are grouped into Core, Production, Chemistry, Player, and Immersion. Click one to jump to its sections.
• Basic and Advanced tabs — the panel opens on Basic, which shows the settings most servers change. Switch to Advanced to reveal the deeper, rarely-touched settings (things like debug logging and animation details).
• Search box — start typing the name of a setting (for example "cook time" or "drying") to filter down to just the matching ones.

Changing a setting

1. Click into the field and type or pick the new value. Toggles are on/off switches; numbers have a box; some settings are lists you add rows to.
2. If a value isn't allowed (for example a number outside its range, or two settings that conflict), the panel shows a short red message right under that field and won't save it until you fix it.
3. Click Save. Valid changes are stored in your database and take effect immediately.

Resetting a setting

Every setting has a reset to default control that puts it back to the value the resource shipped with (the value from the config files). Use this if you change something and want to undo it. Reset also saves and applies right away.

What "applies live" means

You don't restart the server after a change. In practice:

• Placed equipment and crystallizer trays re-appear with their new look/geometry as soon as you save — for example if you change a prop model or tray layout.
• Minigame values (cook timing, temperatures, shard counts, bag weights, and so on) take effect on the next cook, break, or bagging session a player starts.

Placement Zones (drawing them in the world)

A zone is an area of the map you outline on the ground, used to control where players may place meth equipment. A zone is a polygon: a flat shape you mark out by dropping a series of points, like marking corners on a map.

There are two lists and a mode that picks which one is in charge. Open /meth settings → Placement Zones (under the Core category) and set Zone mode:

The two lists are stored separately, so you can draw both and switch between them without losing any shapes.

To draw a zone:

1. Go to the Placement Zones section and pick the list you want (Blocked areas or Allowed areas).
2. Start a new zone. The panel hands you an in-world editor: your view lifts into a free-moving camera so you can fly around and look at the ground.
3. Drop points to outline the area. The editor shows its own on-screen hints telling you which keys place a point, adjust the height, undo, save, and cancel — follow those prompts.
4. Save the zone. You're returned to the settings panel with the new zone added. Give it a name to remember it by, expand it to edit, jump to it with the teleport button, redraw its shape later, or remove it.

Saved zones apply live — no restart needed.

Police Alerts

Under Dispatch (in the Core category, on the Advanced tab) you can make cooking carry a risk of being reported to police.

Set Alert chance above 0 and every time a player starts a stage the server rolls for a dispatch call at that equipment's location. Each of the four stages — cook, break, bag, dry — can carry its own chance; leave one at -1 and it follows the master chance.

Two settings stop it becoming noise:

• Site cooldown (default 5 minutes) — the same table can't raise a second alert until it expires. Other equipment is unaffected.
• Per-stage chance — turn the quiet stages down or off and leave the cook itself risky.

Everything is decided on the server from the equipment's stored position, so a player can't suppress the alert or make it point somewhere else.

Changes apply live. See Configuration for the full field list and what you need installed.

Player Command

/meth stats

Any player can run this. It shows their stats card for 10 seconds:

• current level, XP, and progress to the next level
• total product created and sold
• their current purity penalty
• which additives are unlocked and which levels unlock the rest

Admin Test Commands

/meth kit

Gives you everything needed to run the full production line once:

• 5x of each base ingredient
• 1x meth table and 1x crystallizer
• 10x baggy
• 3x of every additive
• 1x gas mask and 1x cooking manual

Use this on a test character to walk the whole pipeline after installing.

/meth sellkit

Gives several random stacks of finished meth baggies, with random variants and purity grades already stamped on them. Use this to test selling, usage effects, or anything that consumes finished product without cooking it first.

/meth setlevel [id] [level]

Sets a player's meth level, and sets their XP to that level's starting threshold.

• id — the player's server ID
• level — 1 to 10 (with the default level table)

The player must be online with a character loaded. Both you and the player get a confirmation message. Useful for testing additive unlocks — for example /meth setlevel 1 7 unlocks everything including Toluene.

This command also works from the live server console (txAdmin or terminal), where no permission is needed.

Permissions

The admin subcommands — /meth settings, /meth kit, /meth sellkit, and /meth setlevel — check whether the player is a server admin before they do anything. A player without admin access who runs one gets a "No permission" message.

Admin access uses FiveM's built-in permission system (called ACE). Give your admin group the admin permission, then add your admins to that group. In server.cfg:

add_ace group.admin admin allow
add_principal identifier.license:YOUR_LICENSE_HERE group.admin

If your server already has an admin group set up this way (most do), the commands work for your admins with no extra setup. Old per-command grants such as command.methkit no longer apply.

/meth stats needs no permission.

Next Steps