FAQ & Troubleshooting

The speaker prompt does not appear

Three reasons, in order of likelihood:

1. You are not driving. The prompt only shows to the driver. Passengers and players on foot get nothing, deliberately.
2. You already have an open drive-thru order. One at a time. Collect it or cancel it first.
3. Your coords are wrong for your MLO. The shipped coords are for the Vespucci BurgerShot lane. The speaker triggers within 3.5m, so drive right up to the point you set.

The window says "Wait, order not ready"

The order has not reached READY. That happens only when the cook has served every line at the addon's serve point. Making the items at the stations is not enough on its own, they sit in the cook's pocket until they are served.

The cook cannot see a Serve to Window prompt

The serve point is a normal ox_target zone gated on being on the BurgerShot job and clocked in. Check the duty state first, then the coords with Config.Debug = true.

If you renamed the job in the base script's Config.JobName, the addon still checks for burgershot. See the note at the end of Configuration.

Orders disappear on their own

That is auto-void. It fires when the customer disconnects, or when they stay more than autoVoid.radius (200m by default) from the lane for longer than autoVoid.graceMs (30 seconds). Coming back inside the radius resets the timer. Raise the radius if your approach road is long.

The base script's own Config.AutoVoidAfterMs also still applies as a backstop, so a ticket nobody ever collects clears eventually either way.

Nothing happens at all, no prompts anywhere

Check your load order in server.cfg. ensure AC_Burgershot has to come before ensure ac_burgershot_drivethru, otherwise the addon's export calls hit a resource that has not started.

Do drive-thru orders get their own queue?

No, and that is intentional. They land in the same tablet queue as walk-ins, marked with a car badge, and cooks work them first come, first served. One queue means one workflow to learn, and the kitchen never has to decide which screen to watch.

Does the drive-thru cost more?

By default yes, +10%, which is Config.DriveThruSurcharge. Set it to 0 to match walk-in prices. The markup applies to the subtotal only, tips are outside the subtotal and still go entirely to the assigned cook.

Does the cook get the tip on a drive-thru order?

Yes, identically to a counter order. The cook who accepts the ticket and flips it to READY is the assigned cook and receives 100% of the tip, online or offline.

Can the customer cancel their own drive-thru order?

Yes, /bcancel from the base script works on any channel.

Does it add tables, items, or dependencies?

None. It uses the base script's tables, items, banking, and notifications. Its only direct dependencies are the base script, ox_target, and ox_lib.

Can I use it as a template for my own addon?

That is a fair use of it. Everything it does goes through the base script's documented exports and the AC_Burgershot:OrderStateChanged event, with no reach into the base's internals, so it is a complete worked example of the integration surface. See the export list on the overview.

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