Skip to main content
FA Shop Robbery separates shared gameplay settings, reward tables, and server-only secrets.
Keep webhook URLs and API keys in config/server_config.lua. Never move secrets into config/config.lua or client files.

Bridge settings

config/config.lua
Use none for the ox_lib TextUI target fallback or to disable dispatch. Use custom only after implementing the relevant adapter.

Clerk and robbery rules

Config.Clerk.Enabled controls all clerks. IntimidationMode accepts target, aim_weapon, or both. You can also configure code disclosure, idle scenarios, silent alarms, and clerk combat.Disable one clerk with store.clerk = false or store.clerk.enabled = false.
Config.MinimumPolice sets the required online officer count. Config.PoliceJobs defines which jobs count.Use Config.Flow.RequireClerkBeforeLoot and Config.Flow.RequireRegisterBeforeSafe to enforce a stricter sequence.
Config.Cooldown.StoreSeconds and PlayerSeconds control repeat attempts. Global can be false, true, or a duration in seconds.Cooldowns and robbery state are runtime-only. Restarting the resource clears them.
Config.Security.AllowedWeapons = true accepts every weapon. Replace it with a hash table to allow only selected weapons.Distance, reward, duplicate-claim, cooldown, required-item, and keypad checks remain server-authoritative.

Safe access

A store can offer one or more safe methods.
config/config.lua
The keypad code is generated and validated on the server. Wrong keypad entries lock only the keypad after the configured attempt limit. Another configured method can remain available.
Set Config.Minigames.Safe = 'fa_minigames' to route keypad and drill methods to the bundled resource.

Reusable profiles

Put reusable progress, police, safe, and clerk settings in Config.Profiles, then select a profile with store.profile.
config/config.lua
Values resolve in this order: direct store overrideselected profileglobal configuration Reward tiers and cooldowns stay independent from profiles.

Reward tiers

tier or rewardTier on a store selects the matching table index in config/rewards.lua.
config/rewards.lua
Reward entries support money or item, a chance from 0 to 100, and minimum and maximum amounts. Item names must exist in your inventory. Rewards.PoliceMultiplier can increase reward values for each online officer up to a configured cap.

Server-only logging

config/server_config.lua
Standalone mode gives cash and dirty-money rewards as inventory items. Configure their names through ServerConfig.StandaloneMoneyItems. Next: add a store or tune rewards.