RE:CORD
REC_HeistManager

Configuration

Installation, configuration, and usage for REC_HeistManager.
Added
Updated
FileSettingPurpose
config/sh_config.luaguard / relationshipGuard behavior and relationships
config/sh_config.luadropoffShared delivery settings
config/sv_config.luawebHeist panel permissions
config/sv_config.luaguardRoutePatrol-route recording command and permissions

Guard behavior and shared cooldowns

Shared config.guard controls patrol, vision, time-of-day modifiers, suspicion and alert transitions, detection, sound reactions, fire avoidance, update intervals, routes and feedback. A heist can override its own guard settings when registering.

config.cooldown.global.seconds blocks all heist orders after any heist completes. config.cooldown.player.seconds starts for every crew member when an order is accepted and applies across heist keys. Both default to 0 (disabled). Player cooldown persistence can be memory (cleared on restart) or database (retained). These are separate from each location’s timing.heistCooldown.

Difficulty configuration supplied to register and registerClient selects an active preset from presets. Its values are applied on top of the heist's declared configuration; numeric fields use multipliers unless their annotations specify otherwise.

Guard bodies

guard.corpse.replaceLocal = true replaces a networked body with a local body after delay (8000 ms by default), once no player is within clearRadius (40 m). It checks every checkInterval (2000 ms). Set it to false to keep the networked body until the phase ends.

©2026 RE:CORD Development Group. All rights reserved.