Releases: IgnisAlienus/SquadJS-Cheater-Detection
v1.4.2
v1.4.1
v1.4.1
Update the Config.json, the Plugin, and the analyzer.js.
Removed Kills Detection due to amount of false positives
Added Suspected DDoS Logging
Removed the need for the LogDir Config line
Fix Bugs in the analyzer
v1.3.1
Adds Embed Output as an Option among other bug fixes from the Beta Branch.
Update these files:
./config.json
./squad-server/utils/analyzer.js
./squad-server/plugins/discord-cheaters.js
v1.2.1
THIS CAP IS A TEMPORARY FIX UNTIL A BETTER METHOD CAN BE MADE
Add a Cap to the Accepted Connection.
Current Cap is set to 50,000.
This avoids long processing Times when the Server Gets DDoS'd and the Log File gets flooded with "Accepted Connection" Lines.
Update your analyzer.js and discord-cheaters.js
v1.2.0
Removed the Kills Detection Method
Added Knife Wounds Detection Method
This tracks Knife Wounds per Player for their entire Session (can span multiple games).
Threshold is currently set at 15, but may need to be tweaked to prevent too many false positives.
v1.1.2
Updated the default value for "clientNetSpeedThreshold" to 18000 in the config.json
Increased Version in discord-cheaters.js
v1.1.1
Fixed a Bug in analyzer.js and increased version number in discord-cheaters.js
v1.1.0
In this Update I have updated:
• The Recommended Threshold for Kills to 0 to disable the Kills Detection. Too many false positives.
• The Recommended Threshold for FOBHits to 75 to decrease false positives. Keep in mind, this is only Explosive damage to Radios, not Shovel Damage.
• Got the Seed and Live Threshold Values working again.
• Added clarification wording anytime there is an output to help explain what each line item means on an output.
Please report any issues here in GitHub or in https://discord.gg/onlybans
v1.0.2
Bug Fix
v1.0.1
Update Release Version