Studios
Data Thefthouse-3.jpg

Examples

SoonData TheftQbox
PAGE 04 OF 06  ·  CONFIGURATION → EXAMPLES → TROUBLESHOOTINGdocs.glitchstudios.dev
Browse docs

Run without XP levels#

Config.xpSystem = ''
Config.tierChance = { low = 0.6, mid = 0.3, high = 0.1 }

The menu then offers one random job, and the tier is picked with those odds.

Pay out in clean cash#

Config.Items.payout = 'money'
-- or pay straight into the character's cash account
Config.useBuiltInCash = true

Turn off the police requirement#

Config.checkCops = false

Use a different hacking item#

Add the item to ox_inventory, then point the setting at it:

Config.Items.decryptionItem = 'laptop'

An empty string ('') means no item is needed to decrypt.

Open the job menu from another resource#

Any client script can open the built-in menu, for example from a phone app or a target option:

TriggerEvent('datatheft:client:job_options')

Start a specific tier#

-- 'low', 'mid', 'high' or 'random'
TriggerEvent('datatheft:client:start', { diff = 'mid' })

The normal level, police and cost checks still run on the server.

How a job runs#

  1. The player picks a tier. The server checks level, police count, a free site and the run cost, then locks the site.
  2. When the owner gets within Config.spawnDistance, the server spawns the guards, vehicles and case and starts watching the site.
  3. The case opens with the key (taken from the guard that carries it) or the lockpick minigame. The server records who opened it and gives the drive to that player once.
  4. The drive can be decrypted from the inventory with the hacking laptop. Hand-in works with or without decrypting.
  5. The owner heads to the marked drop-off, where the server spawns the fence ped. At the ped the server finds the drives, removes them and pays out.
  6. One server loop handles timeouts, dead players and empty sites. Jobs end cleanly on hand-in, cancel, timeout, disconnect and resource stop.