Troubleshooting

Fixes for the most common problems. For most of these, the first step is the same: turn on the Config.Debug setting and restart the resource — the [oxide-blackmarket] lines in the server console will usually tell you what's going wrong. (If the resource has already started once, Config.Debug lives in the database now, not shared/config.lua — see the first section below.)

Configuration Issues

Dealer Issues

Shop Issues

Pager Issues

Police Issues

Death and Loot Issues

Performance Issues

Debug Logging

All debug output is prefixed with:

[oxide-blackmarket]

With Config.Debug = true, the console covers:

• resource startup and dealer initialization (N/M spawned)
• config item-name validation warnings
• dealer spawn, relocation, and despawn
• pager use and results
• shop requests and transactions
• stock changes (per dealer)
• reputation changes
• loot generation and collection
• dealer death handling
• arrest delivery and reward payout

For a permanent audit trail (money, transactions, arrests, security rejections), install the optional oxide-logger resource — this resource logs structured events through it automatically when it's present.

Next Steps

Support

Need more help?

• Discord: https://discord.gg/dZ6q8FyGhm
• Website: https://www.oxidestudios.dev/
• o-link (required abstraction layer): https://github.com/WHEREISDAN/o-link