Rewards are keyed by job id. When a job ends, a server script fires glitch_criminaltablet:reportJobComplete. glitch-criminaltablet fires it for its own jobs, and any server script can fire it too. Each participant is then rolled against these tables in order:
BlueprintDrops[jobId]: the first blueprint whose chance hits, at most one per run.ComponentDrops[jobId]: restricted materials, each line rolled on its own.CacheDrops[jobId]: a loot crate, with bad-luck protection throughpity.CaseDrops[jobId]: blueprint cases, each line rolled on its own.BlueprintPity: signature blueprints guaranteed on the Nth clear of the listed jobs, if the character does not know the recipe and is not carrying the blueprint.
A job in RolledByScript rolls its components or cache itself while the job runs, through the exports.
ServerConfig.ComponentDrops = {
bank = { { 'hardened_alloy_plate', 0.35, 1, 1 } }, -- { item, chance, min, max }
}
ServerConfig.CacheDrops = {
bank = { crate = 'cache_deposit', chance = 0.15 },
pacific_standard = { crate = 'cache_vault', chance = 0.40, pity = 3 },
}
ServerConfig.BlueprintPity = {
military_thermite = { jobs = { 'paleto_bank' }, guaranteeAt = 2 },
}
The shipped tables use example job ids. Replace them with the ids your heist scripts report. A job id that nobody reports does nothing, so unused entries are harmless.
What is kept where#
| Store | Contents |
|---|---|
| Database | crafting_queue, crafting_blueprints, crafting_log, crafting_benches, crafting_admin_recipes, crafting_admin_benches, crafting_settings, crafting_prop_photos, crafting_weekly |
| Resource KVP | Per character id: pity counters, the Head start meter and the Padlock and Production line perk flags. WipeCharacter removes them. |
| Memory | The booster active when a craft was queued. It is lost on restart, and the craft then pays the normal XP rate. |
Stuck on a step?Ask in the Discord →