The heist cannot start#
With the default config it needs the casino_diamond contract from glitch-criminaltablet. Set Config.Job.requireContract = 'no' on servers without it. Also check that enough police are online for Config.Job.minPolice, and that the casino is not still resting after a run.
Wrong doors open, or doors do not open#
Config.Doors still holds the shipped ids, which belong to another database. Create the doors in ox_doorlock and put your own ids in. If you use door names, check that install/doors.json has an entry for each name. The console prints how many doors have neither a door nor an entry.
The console lists a missing item#
Add the item to ox_inventory from install/items.lua. The check runs five seconds after the resource starts.
The console says a resource is not started#
glitch-heistEditor, glitch-minigames and ox_doorlock must be running. Start them before glitch-casinoHeist in server.cfg.
Diamond Casino is missing in /heisteditor#
The engine did not load the definition. Check that the folder is named exactly glitch-casinoHeist, that glitch-heistEditor starts first, and read the console for errors from either resource. If doors were created at start-up, the resource triggers glitch-heistEditor:ready to register the heist again.
Cameras do nothing#
glitch-securityCameras is not running. The camera steps pass without it. If it is running, check that the ids in Config.CameraIds are the ones it registered. The resource registers its five cameras when glitch-securityCameras starts, and again if that resource restarts.
Blackout comes back on#
A weather sync resource may be resetting the lights. Run vSync, or stop the weather resource from touching artificial lights.
The lasers do not hurt#
That is intended. The lasers are visual only and do not trigger an alarm.
Getting help#
Include the resource version (in fxmanifest.lua), your framework, which optional resources you run, the steps to reproduce, and the relevant server and F8 console errors in a support ticket.