Global Config Client Ops Learning API
Production defaults Sync-aware rollout Safe enforcement tuning

// CONFIGURATION

Configuration Reference

Use these notes to tune ImpactGuard without breaking panel sync or accidentally turning weak detections into aggressive enforcement.

Panel sync Confidence policy Module configs Override behavior XGuardian Ops integrations Reload workflow

Panel.json baseline

Panel connectivity, license validation, heartbeat timing, and config sync behavior are controlled here.

{
  "Enabled": true,
  "PanelApiUrl": "https://impactguard.ac",
  "LicenseKey": "IG-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXX",
  "ServerName": "CS2 Server",
  "ServerIp": "YOUR.PUBLIC.IP",
  "ServerPort": 27015,
  "HeartbeatIntervalSeconds": 60,
  "ConfigSyncIntervalSeconds": 120,
  "AutoSyncPanelToLocal": true,
  "AutoSyncLocalToPanel": true
}
  • PanelApiUrl must match the production panel URL reachable from the game server.
  • LicenseKey binds the local server to the account entitlement and plan limits.
  • ConfigSyncIntervalSeconds defines the normal propagation window. Around 120 seconds is expected for many installs.
  • Use local reload commands when you need immediate validation after editing files by hand.

General.json confidence policy

These controls decide whether module action intent is allowed to become a kick or ban.

{
  "StrictFalsePositiveProtection": true,
  "MinDetectionsForPunitiveAction": 3,
  "MinUniqueModulesForPunitiveAction": 2,
  "MinThreatScoreForPunitiveAction": 25,
  "ConfidenceGateEnabled": true,
  "MinConfidenceForKick": 0.72,
  "MinConfidenceForBan": 0.86,
  "AdminSystem": "none",
  "BanDurationMinutes": 0
}

AdminSystem is none, iks, simpleadmin, or pisex. Shipped default is none. Extra keys in the file cover correlation windows, shadow mode, and session gates for bans — leave them unless you know you need them.

Recommended posture: keep strict protection enabled, start in log-heavy mode, then tune after reviewing real server evidence.

Module config families

Most detection modules share DetectionEnabled, DetectionAction, AlertDiscord, MaxDetectionsBeforeAction, and decay controls. Specialized modules add thresholds for their signal type.

Aim

Angle deltas, aim variance, tracking, silent aim, spin/anti-aim, flicks, interpolation, reaction timing, and smoothing curves.

AimbotAimConsistencyAimDeltaDistributionAimlockSilentAimSmoothAimSpinbotAntiAimUntrustedAnglesFlickAimDetectorFlickPathJitterFlickOvershootStrafeAimAimInterpolationReactionTimingSmoothingCurve

Movement

Bhop perfection, auto-hop, strafe ratios, stamina, fake duck/crouch spam, velocity, teleport, lag, adaptive lag, and backtrack windows.

BunnyHopAutoHopDetectorAutoStrafeMovementAnomalyStaminaAbuseFakeDuckCrouchSpamSpeedTeleportFakeLagAdaptiveFakeLagBacktrack

Weapon / Fire

Trigger timing, fire-rate abuse, revolver cook behavior, recoil compensation, headshot ratios, and anti-flash kill context. Recoil config file is RecoilControl.json.

TriggerbotRapidFireRageFireR8AutocookKillAuraRecoilControlHeadshotRatioAntiFlash

Behavior

XGuardian-backed behavior score, per-round stats, name/chat abuse, skin changer, griefing, toxicity, audio-visual desync, and convar tamper.

MLBehaviorPerRoundStatsSkinChangerNameSpoofChatSpamGriefDetectionToxicityDetectionAudioVisualDesyncConVarManipulationPhantomDecoy

Native sensors

Tick and client integrity. These stay idle until impactguard_native is loaded (bundled in the CS2 zip).

CommandTimingSubtickBurstInvalidButtonsAirKeyNullsJumpScrollClientConVarsClientSignalScan

Global override mechanics

The global override is a bulk edit tool for compatible action fields, not a blanket rewrite of every config file.

  • Log is the safest override for learning, rollout, and false-positive review windows.
  • Kick and Ban set module intent, then confidence policy still decides final enforcement.
  • Eligible counts configs with a known action schema. Changed counts configs where the stored value actually changed.
  • Policy-only, panel, logger, whitelist, and admin integration configs may be skipped because they do not represent detection action intent.
Do not interpret low changed count as failure if eligible count is high; most configs may already match the selected action.

XGuardian and demo configuration

XGuardian can analyze demos on round or match boundaries and feed model-backed scores into review workflows. Keep automatic punishment disabled until local review quality is proven.

{
  "EnableXGuardian": true,
  "AnalyzeOnRoundEnd": false,
  "AnalyzeOnMatchEnd": true,
  "AutoKickEnabled": true,
  "AutoBanEnabled": false,
  "MinCheatScoreForAction": 0.85,
  "AnalysisTimeoutSeconds": 300
}
{
  "Enabled": true,
  "MinThreatScoreToRecord": 15,
  "MinUniqueModulesToRecord": 1,
  "StopRecordingAfterIdleSeconds": 300,
  "MinRecordingSeconds": 20,
  "AutoSubmitToXGuardian": true
}
Shipped XGuardian.json has AutoKickEnabled true and AutoBanEnabled false. Confidence gating still applies. Turn auto-kick off if you want demo scoring to stay review-only. Keep AutoBanEnabled false until local evidence quality is proven.

Operations integrations

AutoWatch and Spectate

AutoWatch prioritizes suspects for moderator review. Spectate supports manual verification. Both are review tools and can be plan-entitlement dependent.

Admin systems

AdminSystem should match the installed stack: iks, simpleadmin, pisex, or a disabled/manual mode depending on deployment.

Unban sync

Panel unban operations should clear panel-side state and sync to local/plugin-admin state. If a player remains banned, check local admin plugin files and reload state.

Notifications

Discord, RCON, admin alerts, and file logging should carry module name, action intent, threat score, and reason so staff can audit decisions.

Reload and verification workflow

Use this sequence after changing configs or deploying panel/docs updates.

igac_reload
igac_reload_all
igac_modules
igac_status
igac_suspect <slot>
igac_metrics
igac_demo_start
igac_demo_stop

Next: client operations guide for moderator runbooks and troubleshooting steps.