Documentation

Safe Tiers

Configure the default tiers and add your own.

Safe Crack places no safes in the world. Each integrating resource prepares an attempt with a tier name from Config.Tiers in shared/config.lua. The tier sets how hard that safe is.

#Default Tiers

TierWheelsGate windowFalse clicks per wheelShakeRelocks afterStethoscope
store3±201.0NeverOptional
office3±110.66 wrong pullsOptional
vault4±120.63 wrong pullsRequired

#Adding a Tier

Add a new key next to the default tiers, with every field the default tiers have.

lua
Config.Tiers = {
    -- store, office and vault stay here

    jewelry = {
        wheels = 5,
        window = 1,
        decoys = 1,
        tremor = 0.3,
        relockAfter = 4,
        requireStethoscope = false,
    },
}

Restart zyke_safecrack, then pass the new name as tier from your integrating resource. An unknown name is refused with a warning in the server console. See Config for every field.

Removing or renaming a tier breaks every resource that still passes the old name.

#How a Tier Plays

  • wheels sets how many numbers the combination has, from 1 to 6.
  • window sets how many numbers either side of a gate still count. The click only sounds on the exact gate, but the dial shakes and the pull succeeds anywhere within the window.
  • decoys adds false clicks per wheel. A player carrying the stethoscope does not hear them.
  • tremor sets how much the dial shakes inside the window. 0.0 leaves sound only.
  • relockAfter sets how many wrong pulls on the same safe, by any player, fire the relocker. false never relocks.
  • requireStethoscope refuses the attempt without the stethoscope.

#Relockers

A relocked safe stays locked for Config.Settings.relockDuration seconds, 30 minutes by default. When it runs out, the safe gets a new combination and a working relocker. With relockDuration = false, the safe stays locked until the resource that owns it calls the ResetSafe export.

#Combinations Per Safe

Each safeId keeps its combination and wrong pulls until it is opened, its relocker runs out, or ResetSafe is called. Preparing a safe with a different tier than before gives it a new combination. All safe state is kept in server memory, so restarting zyke_safecrack gives every safe a new combination and clears every relocker.