The Problem With Traditional Screenshares
Traditional remote screenshares have a fundamental problem: you're trusting the player's screen. A sophisticated cheater can overlay clean-looking windows on top of actual file contents, show pre-recorded footage of a clean system, or switch focus between windows to hide suspicious content. Even Discord's screenshare quality makes reading file names or command output unreliable.
How the PIN Session Works
Staff generate a session at ac.indianmc.in — the server creates a unique 6-digit PIN. The staff shares the PIN with the player, who enters it when running the Audit AC client (JAR or PowerShell). The client runs all forensic checks locally, then posts findings directly to the Audit AC API using the session token. The data never passes through the player's clipboard, screenshot, or any interface they control. Staff see results update live in the dashboard as they arrive.
Why the PowerShell Scanner Is Obfuscated
The alternative PowerShell scanner is distributed as an AES-256-CBC encrypted, GZip-compressed payload served from the API endpoint. A cheater who inspects the downloaded payload cannot reverse-engineer the detection logic or build a bypass. The decryption key is derived at runtime and is not present in the distributed script.
The Trust Model at a Glance
The player controls whether to run the scanner and when to start — nothing else. They cannot control which checks are run, what data is collected, where the data goes, or what staff sees. Their only real choice is to run or refuse. Refusing is itself a significant red flag for competitive servers.
| What the player controls | What they don't control |
|---|---|
| Whether to run the scanner | Which checks are run |
| When to start | What data is collected |
| — | Where the data goes |
| — | What staff sees |
Practical Staff Workflow
Go to ac.indianmc.in and click Generate Session. Share the 6-digit PIN with the player via voice or in-game message. The player runs the client and enters the PIN. Watch results populate live in your browser — no refreshing needed. Review mod integrity, JVM flags, environment checks, and system telemetry, then make your ruling based on the complete forensic picture. The entire process, once the player runs the scanner, takes under 60 seconds.