Admin Tools

Everything an admin does in oxide-shops happens through two in-game menus, opened by one command. There are no separate commands to memorize for each action.

Commands Overview

All three are the same command /shop with a different first word after it. Anyone who is not an admin gets "You don't have permission to do that".

Command Details

/shop

Typing /shop on its own (or with an unknown word) prints the usage line: Usage: /shop <admin|settings>.

Usage:

/shop

If you run it from the server console, it also prints the list of available subcommands. The admin and settings subcommands open on-screen menus, so they can only be used by a player in-game — not from the console.

/shop admin

Opens the admin panel, where you create and manage every shop on the server. See The Admin Panel.

Usage:

/shop admin

• Success: the admin panel opens on your screen.
• From console: prints "This subcommand cannot be used from console".
• No permission: "You don't have permission to do that"

/shop settings

Opens the settings editor, where you change prices, tax, blips, rate limits, and every other option live. See The Settings Editor.

Usage:

/shop settings

• Success: the settings editor opens on your screen.
• From console: prints "This subcommand cannot be used from console".
• No permission: "You don't have permission to do that"

The Admin Panel

Open with /shop admin. From here you manage individual shops. What you can do:

• Create a shop — from scratch or from a ready-made template (all the default GTA stores are templates). You choose the shop's ID, name, style, shopkeeper model, and location, and you can place the location in the world.
• Edit a shop — change its name, model, location, style, and interior.
• Delete a shop — permanently removes the shop and its stock.
• Reclaim a shop — takes a player-owned shop back to server-run (static) status, wiping its balance and restoring unlimited stock.
• Make a shop purchasable — set a purchase price so players can buy it (set it to nothing to take it off the market). Pawn shops cannot be made purchasable.
• Transfer ownership — hand a player-owned shop to a different character by their character ID.
• Adjust the shop balance — add, remove, or set the money in a player-owned shop's till.
• Manage items — add or remove items on a shop, and set item prices (works for both sellable items and service prices).
• Access restrictions — lock the shop to a job, a minimum rank, and/or on-duty players only.
• Map Blip editor — hide the shop's blip, or give it a custom icon, color, size, and label. Blanks fall back to the style's default.
• Chairs (barber/tattoo shops) — place or remove the seats customers sit in during styling.
• Tattoo camera editor (tattoo shops) — set the preview camera angle for a tattoo. A tattoo with no camera is hidden from customers until you set one.
• Auction preview spots (auction house) — add or remove spots where listed vehicles appear for viewing, and save each spot's camera angle.

Changes made in the admin panel apply immediately for everyone on the server.

The Settings Editor

Open with /shop settings. This edits the global options — prices, tax, markup, blips, rate limits, wholesale catalog, and templates — not individual shops. See Configuration for what each setting does.

• Settings are grouped (General, Economy, Blips, each shop type, and so on) and split into Basic and Advanced tiers.
• Change a value and press Save Changes. It takes effect right away and is saved to your database.
• Each setting has a Reset to default option that restores the value the resource shipped with.
• Some settings (placing a location in the world) need an up-to-date o-link. If you see "In-world placement needs an updated o-link", update o-link.

Permissions

oxide-shops treats admin access as a simple yes/no through o-link. A player counts as an admin if any of the following is true — so on a standard framework setup, your existing admins already qualify:

• They are in a group that has the admin ACE permission (the recommended setup, below).
• They have the stock QBCore/QBX command ACE (which those frameworks grant to group.admin out of the box).
• On ESX, they are flagged as an admin by their ESX group.

The server console always counts as admin, but the /shop admin and /shop settings menus are on-screen, so they can only be opened by a player in-game.

Granting admin access (ACE method)

If your admins can't open the panel, add these two lines to your server.cfg (the text file that configures your server), replacing <license> with the player's license identifier, then restart:

add_principal identifier.license:<license> group.admin
add_ace group.admin admin allow

• The first line puts the player in the admin group.
• The second line grants the admin group the admin permission that oxide-shops checks.

Higher groups (like group.superadmin) that inherit from group.admin are admins too. You do not need to grant any per-command permission.

Next Steps

• Configuration — every setting the editor exposes
• Features — how the systems you manage behave
• Troubleshooting — if the panel won't open