Global Config Client Ops Learning
Operator runbook Review-first workflow Practical troubleshooting

Client Operations Guide

Day-to-day workflow for server owners and moderators using ImpactGuard in production: install verification, panel sync checks, triage tools, XGuardian pipeline handling, and recovery steps.

Install checks Daily checks AutoWatch and Spectate XGuardian pipeline Admin and unban sync Troubleshooting Deploy verify commands

Install and first-run checks

Plugin load

Confirm CounterStrikeSharp loads ImpactGuard without dependency errors and the config folder is present.

Panel binding

Verify PanelApiUrl and LicenseKey, then confirm the server appears online in the panel after heartbeat.

Module state

Run module/status commands and confirm expected action modes before opening the server to players.

igac_status
igac_modules
igac_reload

Daily operational checks

Detection review

  • Review detections by module, action intent, threat score, and reason.
  • Expect more logs than bans when strict false-positive protection is enabled.
  • Check whether repeated detections come from one noisy module or multiple corroborating modules.

Sync review

  • Confirm the server heartbeat is current in the panel.
  • Wait one config sync interval after panel changes.
  • Use local reload if a single server needs immediate validation.
Use "Free plan" wording in customer messaging. Avoid legacy trial/time-limited phrasing unless describing a separate historical offer.

AutoWatch and Spectate behavior

AutoWatch and Spectate are review tools that help staff focus attention. They do not replace evidence review or override confidence-gated enforcement.

AutoWatch

Queues suspicious players based on detection and trust context. It is useful for prioritizing moderators during busy sessions and may be plan-entitlement dependent.

Spectate

Supports human review once a player is suspicious. Spectate state should be treated as operational context, not a punishment by itself.

If AutoWatch flags a player while enforcement remains log-only, that is often correct under confidence gating.

XGuardian demo pipeline

XGuardian scoring is asynchronous. Demo capture, upload, analysis, and future model improvement can happen after live heuristic detections.

igac_demo_start
igac_demo_stop
igac_xguardian <demo.dem>
igac_status
igac_metrics
igac_reload

When outcomes look delayed

  • Confirm demos are being written to the configured folder.
  • Check upload route, API endpoint, queue health, and timeout settings.
  • Confirm cooldowns are not suppressing repeated analysis.
  • Review panel pipeline status before assuming model failure.
Keep XGuardian auto-kick and auto-ban flags conservative until your moderators have reviewed enough local evidence quality.

Admin integrations and unban sync

IKS / SimpleAdmin / Pisex

Use the admin system configured in General.json. Test routing with log or short-duration actions before enabling permanent bans through an admin plugin.

Panel unban behavior

Panel unbans clear ImpactGuard-side state and should propagate to local/plugin-admin storage. If a player remains blocked, check the admin plugin ban database and reload state.

Whitelist handling

Whitelist bypass should be tightly controlled. It can reduce noise for trusted staff but should not be used as a broad exception mechanism.

Audit trail

Retain module, reason, action intent, confidence state, operator, and sync timing when investigating unexpected outcomes.

Troubleshooting matrix

License or panel offline

Verify key, panel URL, outbound HTTPS, server clock, DNS, and heartbeat interval. Then reload plugin state and refresh the panel.

Panel edits not visible

Wait one sync interval, run reload commands, and compare local config file timestamps against panel updates.

Unexpected punitive action

Check DetectionAction, strict protection, minimum unique modules, threat score, admin-system routing, and local admin plugin rules.

No XGuardian verdict

Validate demo path, file size, upload retries, API endpoint, queue health, timeout, cooldown, and service readiness.

Deployment and reload verification

After panel or docs changes, verify both the web service and the plugin/runtime path relevant to your rollout.

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

For deeper tuning, review configuration reference. For product-wide behavior, start with global operations.