[CS] 🛡️┃admin-guide & 🔍┃demo-analysis

1. PLAYER VERIFICATION (MANDATORY PROCEDURE)
Before applying any sanction for cheating or taking any action, you are strictly required to follow these monitoring steps:

• Switching to spectator via amx_spectate: In order not to arouse the suspect's suspicion, use the amx_spectate command. This places you in spectator mode, but in the scoreboard (TAB) players will still see you as if you were active on a team and playing normally.

⚠️ PROTOCOL REGARDING EXTERNAL SCANS (WarGods / FunGun) ⚠️
• IT IS STRICTLY FORBIDDEN to request a WarGods (wargods.ro/wcd) or FunGun (fungun.top/ecd) test as a first method of verification! These can ONLY be requested after you have spectated the player for at least 2-3 rounds.
• Why? Foreign players or those unfamiliar with these platforms will immediately leave the server (drop), thinking you are asking them to download dangerous files. To avoid massive player loss and useless bans for "drop/leaving during verification", use these links ONLY AS A LAST RESORT, if the demo is not 100% conclusive and only if the player cooperates voluntarily.



2. HIERARCHY AND VERIFICATION BETWEEN ADMINS (STRICT RULE)
• Admin scan ban: It is STRICTLY FORBIDDEN to request a WarGods or FunGun test from another staff member, regardless of their rank!
• Procedure in case of suspicion: If you suspect a fellow admin of cheating, the only legal method is to record a demo of them in secret (using amx_spectate).
• Who decides the sanction? Demos recorded on admins are not published and are not used to ban directly. These must be sent directly to the higher ranks: Executive, Detinator, Fondator, or MANAGER. Only they have the authority to analyze the evidence and decide whether the suspected admin will be sanctioned/banned or not.



3. COMMANDS AND SANCTIONS (FOR PLAYERS)
Any sanction applied must be based on concrete evidence (a demo saved in the cstrike folder).

• Obvious cheats (Wallhack, Aimbot, Speed): After making a short demo that proves the cheat, a permanent amx_ban is granted.
• Toxic language and behavior / spam: Use commands gradually: amx_gag (3-10 min) ➔ amx_kick ➔ amx_ban (30-120 min, only in cases of severe recidivism).



4. ADMINISTRATOR BEHAVIOR
• Mutual respect: Treat all players with respect, regardless of nationality. Reply to messages in say_team @ in a calm and polite manner.
• Keeping evidence: All recorded demos must be kept for at least 7 days. In case of an unban request or complaint, you are required to present the proof. Lack of a demo leads to the admin being sanctioned!
• No public arguments: Disagreements between admins are discussed strictly in the private chat (amx_chat), on Discord, or directly with a Founder/Manager. Arguing in public chat is penalized directly with Remove.








1. CONFIGURATION AND CONSOLE COMMANDS
To analyze suspect phases in detail, open the console (~):
• viewdemo filename.dem -> Activates the control bar (Play/Slow-Mo)



2. CHEAT DETECTION (CLEAR SIGNS)

[ WALLHACK / ESP ]
• Robotic Pre-Aim: Places the crosshair precisely on the head through the wall before the enemy peeks, without Audio Info.
• Selective Checking: Ignores empty corners, but peeks with a prefire exactly where an opponent is holding.
• Anti-Flash: Takes a full flash to the face but continues to perfectly track the enemy through the wall.

[ AIMBOT / SILENT AIM ]
• Robotic Flick (Snap): The crosshair instantly "jumps" (in a single frame) directly onto the opponent's head.
• Violent Shaking: During a spray, the crosshair shakes strangely on a fixed point on the body.
• Silent Aim: On the screen, the crosshair is 2 meters away, but the bullet registers as a Headshot in the logs.

[ MOVEMENT SCRIPTS ]
• Bhop/Strafe Script: The player gains huge speed in the air and never misses the timing of the jumps.



3. ⚠️ THE GOLDEN RULE FOR BANNING
• Headphones at maximum: Do not confuse Wallhack with heard footsteps or primed grenades.
• Info on Radar: Check if the enemy had already been spotted by a teammate.
• At least 3 Clear Phases: Do not ban for a single lucky kill. Look for consistency!
• Slow-Motion (25%): Slow down Aimbot phases from the panel to see the actual path of the mouse.