FAQ & Troubleshooting

Withdraw and Deposit do nothing

The society account does not exist in your banking resource. Create burgershot (or whatever Config.SocietyAccount is set to) in qb-management, qb-banking, Renewed-Banking, bablo-banking, or esx_addonaccount. See Installation, step 4.

The station says "Missing X in your pocket"

This is working as intended. Cook stations consume ingredients from the cook's own inventory, not from the stash. Open the kitchen stash first and take what the recipe needs. Keeping the two separate is what makes the kitchen a real supply chain rather than an infinite dispenser.

The items are in the stash but the customer is told they are missing

The cook made the items but never served them. Making an item at a station puts it in the cook's pocket and flips the line to cooking. The cook then has to walk to the serve point and click Serve, which moves the items into the stash and flips the lines to done. Only when every line is done does the order go READY.

My order is stuck and will not clear

Managers can clear it: /bvoid <orderId> for one, or /bvoid all to wipe every open order at once, which is the fastest way to reset after testing. Customers can cancel their own open order with /bcancel, which works even after a rejoin because the server reads the order from the database.

Orders also clear themselves. An unpaid counter order auto-voids after Config.AutoVoidAfterMs (10 minutes by default), and a claimed order with no station progress returns to the New queue after Config.AutoReleaseAfterMs (5 minutes).

The cook burnt the food and lost the ingredients

That is the mini-game. Stopping the timing bar in the first 30% gives Raw and in the last 5% gives Burnt, and both destroy the item and waste the ingredients. Everything in between produces the item, with the tip multiplier scaled by how close to Perfect they got. Widen the Cooked zone in Config.Quality.Zones if it is too harsh for your server, or set Config.Quality.Enabled = false to remove the mini-game.

Who gets the tip?

The assigned cook, in full. The cook who accepts a ticket owns it, and whoever flips it to READY is recorded as the assigned cook. When the customer pays, the society receives the subtotal and the cook receives 100% of the tip. It pays out even if the cook has logged off since, and the amount is scaled by the cooking quality multiplier.

Employees get clocked out on their own

Config.AutoClockOutMs forces an idle employee off duty after 15 minutes of no meaningful action, with a warning a minute beforehand. This is deliberate, clocking in and going AFK for the hourly wage is the most common way restaurant jobs get farmed. Set it to 0 to disable.

A cook has taken every order in the queue

Config.MaxClaimsPerCook caps how many tickets one cook can hold at once, defaulting to 5. Lower it on a busy server.

Nothing appears at the counter or the stations

Three things to check, in order:

1. You are on the burgershot job. Set it with /setjob <id> burgershot 3.
2. You are clocked in at the duty point. The server validates duty on every action even when the prompt shows.
3. Your coords match your MLO. The shipped coords are for the Vespucci BurgerShot MLO. Set Config.Debug = true to draw the target boxes and see where they actually landed.

Errors mention a nil Bridge field

The bridge files loaded in the wrong order. Compare your fxmanifest.lua against the shipped one, the bridge/ files have to load before server/ and client/.

Does it run under WaveShield?

Yes, with no extra setup. The script contains no os.* calls at all, every timestamp is computed in SQL with UNIX_TIMESTAMP(). Set Config.WaveShield = true to record that in your config.

Which frameworks are actually tested?

QBCore with ox_inventory, ox_target, and qb-management is the fully tested stack. The qbx_core and ESX adapters ship complete and work, and are community tested. Report anything you hit and it gets fixed.

Can I add my own menu items?

Yes. Add the item to ox_inventory, drop an icon into ox_inventory/web/images/, then add a row to Config.Menu, a recipe to Config.Recipes, and a station in Config.Stations pointing at that recipe. See Configuration.

Can other scripts hook into orders?

Yes. The server exports (CreateOrder, OpenPaymentDialog, ServeItemsForChannel, VoidOrder, GetOrder) are stable across v1.x, and the AC_Burgershot:OrderStateChanged event fires on every transition. The Drive-Thru Addon is built entirely on that surface, so it doubles as a worked example.

Still stuck? Reach us at scripts.aczone.xyz.