Bakery Claiming — Gang/Vendor Claiming System for QBX & QBCore

Bring organised gang competition to your FiveM server with Bakery Claiming. Create timed Gang/Vendor Claiming events where gangs battle to control a vendor, take ownership from rivals and accumulate hold time. The gang with the highest total hold time at the end wins.

Manage gang settings, rosters and matches through an in-game admin interface, with a live match HUD and final scoreboard for participants.

Gameplay Features

• Vendor claiming: Interact with the vendor to take control for your gang.
• Hold-time scoring: Scores accumulate every second while your gang owns the vendor.
• Multi-gang matches: Select two or more configured gangs for each event.
• Configurable events: Set the vendor location, zone radius, match duration and respawn delay.
• Instanced matches: Each match uses its own routing bucket to separate participants from the main server population.
• Gang garages: Configure vehicle models, primary and secondary colours, and garage spawn locations per gang.
• Automatic respawns: Return eliminated players to their gang’s configured respawn location after the match’s respawn delay.
• Live HUD and results: Display remaining time, current vendor ownership, gang scores and final standings.
• Reconnect handling: Disconnected participants can return to their active match after reconnecting.

Administration & Rosters

• In-game admin panel for gang configuration, saved event profiles and match management.
• Start, spectate and manually end Gang/Vendor Claiming matches.
• Custom gang display names and colours.
• Gang boss roster management with configurable member limits.
• Roster lockout deadlines to prevent last-minute lineup changes.
• Online rostered members are entered when a match starts.
• Position capture from the interface for easier location setup.
• Configurable admin access through framework permissions, ACE permissions and license identifiers.

Integrations & Technical Specifications

Component

Details

Frameworks

QBX / Qbox (qbx_core) and QBCore (qb-core)

Framework selection

Automatic detection or manual configuration

Required dependencies

ox_lib, oxmysql, and a supported framework

Medical integrations

wasabi_ambulance and qb-ambulancejob

Inventory bridge

ox_inventory, qb-inventory, or disabled

Database

Persistent gang settings, roster settings, roster members and event profiles

Interface

Bundled web-based NUI, match HUD and scoreboard

Default commands

/claimadmin and /claimroster — configurable

Discord logging

Optional server-side webhook for completed match results

Customisation access

config.lua, server/logs.lua and all Lua files inside bridge/ are excluded from Asset Escrow

Additional Technical Features

• Server-side checks for admin access, roster permissions, match participation and vendor interaction distance.
• Server-created claim vehicles with checks for available spawn space.
• One tracked claim vehicle per participant, with configurable cleanup when left without a driver.
• Match vehicle cleanup when an event ends.
• Automatic database table creation for fresh installations.
• Discord results include the winner, winning hold time, match duration, end reason and standings for up to ten gangs.

Before Purchasing

This resource uses your framework’s gang system. A supported framework, ox_lib and oxmysql must be running before the resource starts. Medical integration should match your server’s death and revive system.

The included game mode awards victory through accumulated vendor hold time. Automatic money or item rewards are not included.

Build your roster. Claim the vendor. Hold it for the win.