Automatically solves Overwatch cases. Its not good but its trying.
You can forcefully parse a demo by running node force.js
, it will ask you for a demo file path and a suspect SteamID. Alternatively just use node force.js <Demo> <SteamID>
This script does not even initialize VAC, you cannot be VAC banned for a cheat detection using this. You can however get manually banned or even suspended from Steam entirely for using this. Valve does not want you to automate Overwatch cases. Use this at your own risk. I am not responsible for any bans, damages, lost items or anything else. You have been warned.
NodeJS 12+ version
- Install NodeJS
- Download and extract this repository
- Open a command prompt inside the directory
- Run
npm ci
- Make a duplicate of the
config.json.example
and remove the.example
- Adjust your now called
config.json
- See Config - Run
node index.js
- After every update repeat from step 3
account
username
: Your Steam account namepassword
: Your Steam passwordsharedSecret
: Optional shared secret to generate Mobile Steam Guard codes. Leave empty to enter manually.saveSteamGuard
: Set totrue
to save login key between sessions - This key bypasses Password and Steam Guard (Stored indata/loginKey
)invisible
: Set totrue
to show as offline on SteamnotifyXPReward
: Set totrue
to receive a notification if you've been granted the Overwatch XP Reward for submitting correct verdicts
parsing
forceConvictOnPreviousBan
: When parsing is done the Suspect's Steam profile is checked for previous bans, if the previous ban is younger than this number of days it will forcefully convict the suspect for wallhack. Use-1
to disable.minimumTime
: Minimum amount of time in seconds for parsing to take before sending verdict to CSGO. If too low CSGO will ignore our verdict.aimbot
maxTicks
: Amount of ticks to check when the suspect gets a killthreshold
: Maximum threshold between angles before adding an infraction for aimbotting
afking
radius
: If the suspect is within this radius for an entire round count as infraction for griefing
detectors
Aimbot
: Enable/Disable aimbot detectorWallhack
: Enable/Disable wallhack detectorGriefing
: Enable/Disable griefing detectorAFKing
: Enable/Disable afking detectorAntiAim
: Enable/Disable anti-aim detector (By @BlackYuzia)
verdict
-
writeLog
: Should we write our logs to a folder calledcases/<CaseID>
? -
backupDemo
: Should we backup the Overwatch demo in a folder calledcases/<CaseID>
? -
printScoreboard
: Should we print a scoreboard with player statistics to console? -
logWithEmojis
: Should we print with emojis? Set tofalse
to use "YES"/"NO" instead of "✔️"/"❌" -
maxVerdicts
: Maximum amount of Overwatch cases to do before stopping.0
for unlimited. -
minAimbot
: Minimum amount of aimbot infractions required to convict for aimbotting -
minWallKills
: Minimum amount of kills through a wall required to convict for wallhacking -
minAFKing
: Minimum amount of rounds the suspect must be AFK for to count as griefing -
minAntiAim
: Minimum amount of anti-aim infractions the suspect must have before convicting for other -
minTeamKills
: Minimum amount of team kills required to convict for griefing -
minTeamDamage
: Minimum amount of team damage required to convict for griefing
-