AWS Black Market

Configurable NPC markets let players sell configured goods, buy goods, and use the money-laundering flow. Locations, allowed jobs, item prices, and currency are defined in config.lua.

Requirements

• QBCore, Qbox, or ESX through the included bridge
• oxmysql
• Inventory and target resources selected by your server
• The manifest references FiniAC unless that optional integration entry is removed

Install

1. Keep the resource folder named rio-black.
2. Back up your database and import rio_black_stock.sql once.
3. If your server uses the additional management_funds schema, review torbaci_jobs.sql and check for an existing table before importing it.
4. Set Config.Locale, Config.Target, Config.BlackMoneyItem, and Config.Markets.
5. Start the core, oxmysql, inventory, target, then:

ensure rio-black

Configure a market

Each Config.Markets entry needs a unique id, type, NPC model and coordinate, optional jobs, and an items list. Use type = "pawn" for player sell-to-market flows. Each item needs the exact inventory item name, price, currency, and optional image filename. Match Config.InventoryImagePath to the inventory image URL.

Set laundering item, rate, and access options in the laundering section. Configured item names must exist in the inventory.

Discord logs

Webhook URLs are blank in this public copy. Add your own URLs in server/webhooks.lua to enable logs. Never publish live webhook URLs; a blank URL disables that log.

Troubleshooting

• NPC missing: check coordinates, model, target resource, and Config.Target.
• Items missing: confirm item names and image paths.
• Stock not persisting: check rio_black_stock.sql and oxmysql.
• Society payment fails: verify framework account/job names and society setup.

Some distribution builds protect runtime files with FXAP. This guide covers exposed settings and SQL; it does not describe code hidden inside protected files.