BCC Shops is a powerful and dynamic shop management system for RedM. It allows servers to create immersive NPC-run stores and fully functional player-owned shops, all configurable via an in-game menu. No need to touch config files!
-
🧍 NPC Shops
Create NPC-operated shops with customizable blips, coordinates, and ped models. -
🧑🌾 Player-Owned Shops
Players can own and manage their own shops, complete with inventory caps, ledgers, and sale tracking. -
🔧 Everything Configurable In-Game
No complex config files — all shop settings can be created and edited directly through the management UI. -
🧾 Item & Weapon Categories
Manage shop inventory with category support, separate stock for buy/sell quantities, and level restrictions. -
💰 Ledger System
Track shop funds with deposit and withdrawal options, including automated transaction logging. -
🤖 NPC Customer Simulation
NPCs dynamically spawn, walk to your shop, simulate purchases, and buy random items or weapons. -
📢 Discord Webhook Logging
Important events like purchases, deposits, and edits are sent to a designated Discord channel for transparency. -
🧭 Custom Blip System
Assign map markers to shops with visual identifiers (supports image and hash-based blips). -
🧠 Feather Menu Interface
All menus are powered byfeather-menu, offering a clean, responsive experience. Most of the notifications areFeatherMenu:Notify, no more vorp notification. -
🌍 Multilingual Support
Fully localized in English and Romanian, with support for adding more languages using_U("key").
This system depends on the following RedM/FXServer resources:
vorp_corevorp_inventoryfeather-menubcc-utilsoxmysql
-
Download the bcc-shops last version into your server’s
resources/folder: -
Add to your
server.cfgafter all dependencies:ensure vorp_core ensure vorp_inventory ensure feather-menu ensure bcc-utils ensure oxmysql ensure bcc-shops
-
Start the server once to auto-generate the required database tables.
Located in config.lua, the few basic options include:
defaultlang– Language file to use (en_langorro_lang)keys.access– Interaction key for shop prompt (default: G)ManageShopsCommand– Command for opening admin management menuWebhook– Global Discord webhook URLadminGroups,AllowedJobs– Controls admin access to management UIBlipStyles– Configure available blip iconsNPC– Control NPC buyer behavior and spawn points
📝 All critical shop settings like positions, peds, inventory, and labels are handled directly through the in-game UI — no need to edit config files.
- Players press the configured key to access nearby shops.
- Shop owners can manage inventory, prices, and funds via the in-game interface.
- Admins use the configured command to create, edit, or delete shops.
- NPCs will dynamically simulate buyers and engage in item or weapon purchases.
-
When players sell an item to a shop, that shop’s
buy_quantityfor the item increases.
If you enforce an intake cap, the shop’ssell_quantityis reduced accordingly. -
If the shop didn’t have that item listed yet, it’s added to the shop with
buy_price = 0.
This lets shops collect items from players without instantly listing them for sale. -
An item becomes buyable by customers only when both are true:
buy_quantity > 0buy_price > 0
Ifbuy_priceremains 0, the item stays hidden/unavailable in the Buy menu even if the shop has stock.
-
Player-owned shops: the amount paid to the seller is taken from the shop ledger — ensure sufficient funds to accept sales.
NPC shops: sellers are paid by the system; no ledger required. -
Withdraw collected stock: shop owners can open Manage Items → Remove Items and take any amount from the shop’s stock back into their inventory.