Premium docs Confidence gated actions Plugin + panel operations

Global Operations Handbook

Operator overview for ImpactGuard covering both CS2 and CS 1.6: plugin installation, license and config sync, confidence-gated enforcement, detection modules, and deployment verification.

CS2 install flow CS 1.6 install flow License and config sync Confidence gate Module suite XGuardian Operations Deploy checks

CS2 plugin installation flow

Install the current runtime package once, then manage entitlement, config, and policy from the panel.

1. Prepare server

Install CounterStrikeSharp, confirm the server boots cleanly, and stop the game server before copying plugin files.

2. Copy package

Place ImpactGuard under the CounterStrikeSharp plugins directory and keep the shipped config files together.

3. Bind panel

Create or select the server in the panel, paste the license key into Panel.json, then start the game server.

The Free plan is a normal entitlement path. Upgrades change limits and features through the panel; they do not require a different binary.

CS 1.6 plugin installation flow

Install the ImpactGuard AMXX plugin on your Counter-Strike 1.6 server. The same panel, ban database, and dashboards are shared with CS2.

1. Prerequisites

Install AMX Mod X 1.9+ (1.10 recommended) on your HLDS server. Confirm the server boots cleanly with amxx plugins listing the default plugins.

2. Download & copy

Download the latest .amxx from the panel landing page or /api/download/cs16/latest. Place it in cstrike/addons/amxmodx/plugins/ and add it to plugins.ini.

3. Configure

Edit IGAC_CS16.cfg in cstrike/addons/amxmodx/configs/. Set the panel URL (igac_panel_url) and license key (igac_license_key). Restart the server.

4. Verify

Type igac_status in server console. You should see Panel: Connected and the license status. The server will appear in your panel dashboard within 2 minutes.

CS 1.6 servers share the same license system. A Free-tier license works for both CS2 and CS 1.6 servers within slot limits.

CS 1.6 detection modules

The CS 1.6 plugin (IGAC v1.1.0+) includes 19 detection modules across three tiers. Tier 2 and Anti-ESP modules require ReHLDS ≥ 3.14.0.857, ReGameDLL ≥ 5.28.0.756, and ReAPI ≥ 5.26.0.338.

Tier 1 — Standard (10)

AMX Mod X only · works on any CS 1.6 server

Rapid FireSpeed HackCamera ShakeNo RecoilHS RatioFake LagCheat UserinfoDupe IPCaptchaSentinel Copilot

Tier 2 — ReAPI / ReGameDLL (6)

Physics-level detection via PM_Move & ReGameDLL hooks

Strafe HackFast RunJump BugAir StuckAnti-Aim PMDuck Macro

Anti-ESP — ReHLDS (3)

Server-side hiding of enemy data from clients

Model HidingSound BlockingPhysent Blocking

CS 1.6 console commands

igac_status
igac_sentinel
amx_plugins

License, panel, and config sync

License heartbeat

The plugin sends periodic heartbeats with the license key, server identity, and health metadata. Invalid keys, wrong panel URL, or blocked outbound HTTPS are the first things to check when a server appears offline.

Config sync cadence

Panel-to-plugin changes are asynchronous. A common sync interval is about 120 seconds, so wait one full window before treating a panel update as failed.

Global action override semantics

Eligible means a config has a compatible action field such as DetectionAction.
Changed means the override wrote a different value. Eligible rows already matching the requested value are valid no-ops.
Insertion only adds missing action fields for compatible schemas; unknown or policy-only configs are skipped.
The override sets module action intent. Confidence gating can still downgrade low-confidence kick/ban intent to log-only.

Confidence-gated enforcement

ImpactGuard intentionally separates module detection intent from final punishment. This keeps weak or isolated signals visible without treating every log as a ban-worthy event.

Signal countMinimum detections before action

Module diversityUnique sources required

Threat scoreConfigured confidence floor

Expected behavior: low-confidence single-module bursts remain logs; stronger correlated evidence can allow kick or ban depending on configured policy.

Full detection module overview

The suite spans aim, movement, weapon/fire behavior, evasion, admin policy, and XGuardian signals. Names below reflect current operator-facing module language; exact availability can vary by build and entitlement.

Aim

AimbotAimConsistencyAimDeltaDistributionAimlockSilentAimSmoothAimSpinbotAntiAimUntrustedAnglesFlickAimDetectorStrafeAim

Movement

BunnyHopAutoStrafeMovementAnomalyStaminaAbuseFakeDuckCrouchSpamSpeedTeleportFakeLagBacktrack

Weapon / Fire

TriggerbotRapidFireRageFireR8AutocookKillAuraRecoilAnalysisRecoilControlHeadshotRatioAntiFlash

Behavior / Evasion

WallhackMLBehaviorEvasionTrackerPerRoundStatsSkinChangerNameSpoofChatSpamGriefDetection

Admin / Policy

General confidence gateSuspicionAutoActionAutoWatchWhitelistAdminAlertsFileLoggerRconForwarding

XGuardian

XGuardianXGuardianStreamAutoDemoRecorderMLBehavior scoreDemo uploadCheat-score verdicts

Operational (internal)

Backend services bundled with the CS2 plugin — not detections.

AI AdversaryBehavioral DNAFederation Sync

CS2 totals: 38 detection modules + 3 operational modules = 41 BaseModule classes.

XGuardian demo pipeline and troubleshooting

XGuardian is an asynchronous demo and signal pipeline. It can enrich future confidence decisions, but a submitted demo should not be treated as an instant punishment request.

Capture

AutoDemoRecorder starts from suspicious threat score and unique-module thresholds, or an operator records manually.

Submit

The demo and metadata are queued for XGuardian analysis when upload and API settings are valid.

Review

Panel views expose status, verdict timing, and feed quality for later retraining and operator review.

If verdicts are missing, check demo folder permissions, API endpoint URL, queue health, upload size, and whether cooldown settings are delaying analysis.

Operational integrations

AutoWatch and Spectate

AutoWatch is moderator triage. Spectate helps review suspicious players. Neither should be described as bypassing the confidence gate; they prioritize human review and context.

IKS, SimpleAdmin, and Pisex

Admin-system integration routes punishments through the configured server admin stack. Confirm the selected admin system in General.json and test with a non-production action first.

Unban sync

Panel unbans remove matching records from the panel state and should be mirrored to local ban/admin storage on the next sync or reload path. If a player remains blocked, check local admin plugin ban lists.

Alerts and forwarding

Discord, RCON forwarding, file logging, and admin alerts are support channels. They should explain module source, confidence, and final action clearly.

Deployment and reload verification commands

Use plugin commands for server-side validation and host commands for panel deployment checks.

igac_status
igac_modules
igac_reload
igac_reload_all

igac_suspect <slot>
igac_metrics
igac_demo_start
igac_demo_stop

pm2 reload impactguard-panel --update-env
curl -sS http://127.0.0.1:3000/ready
pm2 list

Continue with configuration reference for exact config keys and client operations for day-to-day moderation runbooks.