Diamond Bartending Job

Overview

Diamond Bartending Job is a complete player-run nightlife business resource. It combines precision cocktail preparation, shared stock, customer orders, employee invoices, supplier deliveries, NPC customers, table service, reviews, progression, promotions, analytics, premium distributors, and Superstar VIP visits.

Compatibility matrix

Requirements

Required resources

• ox_lib — callbacks, menus, progress interactions, notifications, and utility functions.
• ox_target — all configured interaction zones and entity targets.
• oxmysql — persistent businesses, orders, stock, deliveries, reviews, progression, distributors, Superstar visits, and reports.
• One framework — ESX or QBCore.
• One inventory — ox_inventory, qs-inventory, or qb-inventory.

Recommended environment

• OneSync enabled for networked couriers, NPC customers, waiters, and Superstar guests.
• A compatible bar, nightclub, restaurant, or lounge MLO.
• A server artifact and framework build current enough for Lua 5.4 and modern ox resources.

Installation

1. Download and extract.

   Place the folder in your server resources directory and keep the resource folder named diamond_bartending.

2. Install dependencies.

   Verify oxmysql, ox_lib, ox_target, your framework, and your chosen inventory start correctly.

3. Add inventory items and images.

   Use the included snippets and copy the 13 PNG files to the image directory used by your inventory.

4. Prepare jobs.

   Review shared/jobs.lua and the included QBCore job snippet. Confirm the configured job name and boss grade match your server.

5. Prepare the database.

   Leave Config.Database.autoInstall = true for automatic schema installation, or import install/diamond_bartending.sql manually.

6. Configure the venue.

   Update business coordinates, targets, tables, queue positions, waiter corner, courier points, bouncers, VIP seats, and camera data.

7. Add ACE permissions.

   Grant only the administrative commands that your staff require.

8. Start and test.

   Restart the resource, run dbhealth, and complete the first-run acceptance test below.

Recommended server.cfg order

# Core dependencies
ensure oxmysql
ensure ox_lib

# Framework (choose one)
ensure es_extended
# ensure qb-core

# Inventory (choose one)
ensure ox_inventory
# ensure qs-inventory
# ensure qb-inventory

# Target
ensure ox_target

# Diamond Bartending last
ensure diamond_bartending

First health check

dbhealth

A healthy ESX/ox installation reports a line similar to:

[diamond_bartending:health] v0.16.0 · ready yes · database yes · esx/ox

Default job and grades

shared/jobs.lua registers a job named bar when it does not already exist. Existing job definitions are not overwritten.

Items & Images

The package includes one metadata-driven finished cocktail item and twelve configured bottle/ingredient items.

Included inventory files

• install/ox_inventory/items_snippet.lua
• install/qb_inventory/items_snippet.lua
• install/qs_inventory/INSTALL.md
• install/images/*.png

Typical image destinations

Configuration Reference

Main configuration groups

Editable data files

Business, Targets & Coordinates

Each entry in Config.Businesses represents one independent bar business. Duplicate the supplied bar1 structure when adding another venue, then change every unique ID and coordinate.

Core business fields

Config.Businesses = {
    bar1 = {
        label = 'Diamond Bar',
        job = 'bartender',
        bossGrade = 4,
        -- venue-specific targets, tables, NPCs,
        -- waiter, courier, bouncer, VIP and camera data
    },
}

Protected interaction targets

• Bartender station
• Customer menu
• Pickup counter
• Boss menu
• Stockroom
• Supplier terminal
• Review board
• Player tables

Recommended coordinate workflow

1. Stand at the exact interaction point and record the centre coordinate.
2. Set an appropriate heading and box-zone size.
3. Test from every side of the counter or prop.
4. Configure table customerSeat and servicePoint separately.
5. Place NPC queue positions in walking order from the counter outward.
6. Keep courier and Superstar spawn points outside the interior with a clear navmesh route.
7. Run /dbproximity <playerId> [businessId] if an MLO target reports “too far.”

Gameplay Workflows

Player customer order

1. Customer opens the menu and adds cocktails to the basket.
2. The server validates business status, pricing, payment method, table state, and stock.
3. Stock is reserved for the order.
4. An eligible employee claims the ticket and prepares each cocktail.
5. The bartender pours, mixes, and collects the drink.
6. The order moves to pickup or assigned table delivery.
7. The customer receives the cocktail and the transaction/statistics are completed once.

Supplier flow

1. Boss or eligible employee opens the supplier terminal.
2. The server validates the selected distributor, business balance, limits, and purchase.
3. A persistent delivery record is created.
4. The courier travels to the configured destination when physical courier mode is enabled.
5. Stock waits in the stockroom until an eligible employee claims it.
6. Bottles become persistent FIFO stock batches.

NPC and table service

1. An opted-in business receives walk-in guests based on the configured conditions.
2. Guests queue, take a table or order, and generate a stock-valid ticket.
3. Staff prepare the drinks through the normal precision flow.
4. An NPC waiter or assigned employee delivers the order.
5. Guests consume, react, publish a review, and leave.

FIFO distributor behaviour

Distributor tabs are views only. The server always consumes the oldest remaining delivery batch first. An older Reserve batch is therefore used before a newer Standard batch. The active batch’s multiplier affects pour speed but never guarantees a perfect measurement.

Database & Data Safety

The supplied SQL and automatic installer define the same 31 Diamond Bartending tables. No SQL change is required when updating from v0.15.4 to v0.16.0.

Persistent data includes

• Business records, balances, employees, transactions, and catalogue prices
• Orders, preparation state, pickup, invoices, reservations, and delivery assignments
• Supplier purchases, courier state, stockroom claims, stock totals, reservations, and FIFO batches
• Bartender XP, levels, perfect pours, tips, and performance statistics
• NPC service preferences, reviews, business ratings, promotions, events, analytics, and reports
• Distributor unlocks, Superstar qualification, visits, rewards, and cooldowns
• Database-backed cocktails created through the Drinks Creator

Included tables

Automatic or manual installation

Config.Database = {
    autoInstall = true,
    cleanStockOnMigration = true,
    cleanStockMigrationKey = 'v0_5_0_clean_stock',
}

Commands & ACE Permissions

Recommended ACE entries

add_ace group.admin diamond_bartending.health.admin allow
add_ace group.admin diamond_bartending.proximity.admin allow
add_ace group.admin diamond_bartending.stock allow
add_ace group.admin diamond_bartending.distributors.admin allow
add_ace group.admin diamond_bartending.superstars.admin allow
add_ace group.admin diamond_bartending.reviews.admin allow
add_ace group.admin diamond_bartending.drinkscreator allow

Developer API

Client exports

Server exports

Examples

-- Server: add five 750ml vodka bottles
local ok, errorCode, stock = exports.diamond_bartending:AddBottleStock(
    'bar1', 'vodka', 5, 750
)

-- Server: check whether the business may accept orders
local isOpen, reason = exports.diamond_bartending:IsBusinessOpen('bar1')

-- Server: fetch seven-day analytics
local analytics = exports.diamond_bartending:GetBusinessSales('bar1', '7d')

-- Client: read the local player's alcohol level
local alcohol = exports.diamond_bartending:getAlcoholLevel()

Security & Health Diagnostics

All 60 server callbacks and 23 client-triggered server events pass through the shared request guard in v0.16.0.

Included safeguards

• Per-player, per-endpoint token-bucket rate limits
• Duplicate-click protection on financial, stock, order, delivery, reservation, review, and management mutations
• Payload depth, node, and string-length limits
• Startup-readiness rejection before framework/database initialisation finishes
• Source validation and rejected-request diagnostics
• Server-side distance and MLO-safe proximity checks
• Rate bucket cleanup when players disconnect

Reading dbhealth

ready yes      resource startup completed
database yes   schema/database layer is available
esx/ox         detected framework and inventory
requests       accepted + blocked guarded requests
blocked        total rejected requests
rate           token-bucket rate-limit rejections
startup        requests rejected before ready
payload        malformed/oversized payload rejections
source         invalid source rejections

Troubleshooting

Debug mode

Config.Debug = true
Config.Security.logRejectedRequests = true

Disable verbose logging after diagnosis.

Updates & File Reference

Recommended escrow-ignore files

escrow_ignore {
    'shared/config.lua',
    'shared/jobs.lua',
    'shared/ingredients.lua',
    'shared/suppliers.lua',
    'shared/bottles.lua',
    'shared/recipes.lua',
    'install/**/*.lua',
}

Keep shared/catalogs.lua, shared/version.lua, all client modules, all server modules, and framework/runtime bridges protected.

Safe update procedure

1. Back up the resource and database.
2. Back up the six editable shared files and custom installation snippets.
3. Read the release notes and affected-file list.
4. Stop diamond_bartending.
5. Delete the existing web/dist directory.
6. Copy the new full release or the documented drop-in patch.
7. Merge new configuration keys instead of blindly replacing customised files.
8. Restart dependencies, then the resource.
9. Run dbhealth and repeat the acceptance test.

First-run acceptance test

• dbhealth reports ready yes and database yes.
• All eight protected interaction targets open inside the MLO.
• Customer checkout, cancellation, preparation, pickup, and consumption work.
• Employee invoice creation, response, payment, expiry, and cancellation work.
• Supplier purchase, courier arrival, stockroom claim, and FIFO deduction work.
• Player table reservation, checkout, waiter assignment, delivery, and release work.
• NPC customers complete order, service, review, departure, and cleanup.
• A forced Superstar visit completes from spawn through cooldown.
• Restart and disconnect recovery preserve applicable orders, deliveries, tables, NPCs, and VIP visits.
• Repeated submissions cannot duplicate payments, stock, rewards, collection, or delivery.