Admin Commands

Complete guide to administrative commands for oxide-blackmarket.

---

Command Overview

Command	Description	Permission
/relocatedealer	Force dealer to relocate	admin
/dealerstatus	Check dealer status	admin
/godealer	Teleport to dealer	admin
/setblackmarketrep	Set player reputation	admin
/checkblackmarketrep	Check player reputation	admin

---

Dealer Management

/relocatedealer

Force the dealer to immediately relocate to a new random location.

Usage:

/relocatedealer

Parameters: None

Output:

• Notification: "Dealer is relocating..."

Notes:

• Useful for testing or if dealer is stuck
• Does not affect relocation timer (resets from new spawn time)
• With Config.Debug = true, detailed location info is printed to console

---

/dealerstatus

Check if the dealer is currently active and get location information.

Usage:

/dealerstatus

Parameters: None

Output (Dealer Active):

• Notification: "Dealer active at location [index]"
• Console prints:
  • Network ID
  • Location index
  • Exact coordinates (x, y, z)

Output (No Dealer):

• Notification: "No dealer currently active"

Notes:

• Useful for debugging spawn issues
• Shows location index matching Config.Locations array

---

/godealer

Teleport to the dealer's current location.

Usage:

/godealer

Parameters: None

Behavior:

• Teleports 3 units in front of the dealer
• Adds 0.5 to Z coordinate to prevent ground clipping

Output (Success):

• Notification: "Teleported to dealer"

Output (No Dealer):

• Notification: "No dealer currently active"

Notes:

• Useful for quickly finding the dealer
• Works regardless of distance

---

Reputation Management

/setblackmarketrep

Set a player's black market reputation to a specific value.

Usage:

/setblackmarketrep [playerID] [amount]

Parameters:

Parameter	Type	Required	Description
playerID	number	Yes	Target player's server ID
amount	number	Yes	Reputation value to set

Examples:

/setblackmarketrep 1 500     -- Set player 1 to 500 rep (Tier 2)
/setblackmarketrep 5 1000    -- Set player 5 to 1000 rep (Tier 4)
/setblackmarketrep 2 0       -- Reset player 2 to 0 rep (Tier 0)

Output (Success):

• Admin notification: "Set player [ID] reputation to [amount]"
• Target player notification: "Your black market reputation is now: [amount] ([tierName])"

Output (Invalid Player):

• Notification: "Player [ID] is not online"

Notes:

• Can set any value (no upper limit)
• Tier is automatically calculated from new value
• Use /checkblackmarketrep to verify change

Quick Reference - Tier Thresholds:

Rep Value	Tier	Name
0-99	0	Unknown
100-299	1	Street
300-599	2	Connected
600-999	3	Trusted
1000+	4	Inner Circle

---

/checkblackmarketrep

Check a player's current black market reputation.

Usage:

/checkblackmarketrep [playerID]

Parameters:

Parameter	Type	Required	Description
playerID	number	No	Target player's server ID (defaults to self)

Examples:

/checkblackmarketrep       -- Check your own rep
/checkblackmarketrep 1     -- Check player 1's rep
/checkblackmarketrep 5     -- Check player 5's rep

Output:

• Notification: "Player [ID] rep: [rep] (Tier [tier]: [tierName])"

Example Output:

Player 1 rep: 350 (Tier 2: Connected)

Notes:

• If no player ID provided, checks command user's reputation
• If the player is not online, shows "Player [ID] is not online"
• Shows both numeric tier and tier name

---

Permissions

All commands require the admin permission level. Permissions are handled through your framework's built-in permission system via Community Bridge.

How It Works

Commands are registered with the admin permission requirement:

Bridge.Framework.Commands.Add('commandname', 'Description', {}, false, function(source, args)
    -- Command logic
end, 'admin')

Granting Admin Access

The method for granting admin permissions depends on your framework:

• QBCore: Use /addpermission [playerID] admin or manage permissions through txAdmin
• ESX: Use your admin system (e.g., set_group admin)
• QBox: Uses ACE permissions — grant via add_ace in your server config
• Other frameworks: Refer to your framework's permission documentation

---

Best Practices

Testing New Configurations

1. Use /relocatedealer after config changes to spawn fresh dealer
2. Use /dealerstatus to verify dealer is active
3. Use /godealer to quickly reach dealer for testing

Managing Player Reputation

1. Use /checkblackmarketrep [id] to verify current state
2. Use /setblackmarketrep [id] [amount] to adjust
3. Consider tier thresholds when setting values

Debugging Issues

1. Enable Config.Debug = true in config
2. Check console for [oxide-blackmarket] messages
3. Use /dealerstatus to check entity state