Raised This Month: $23 Target: $400
 5% 

[ANY] Little Anti-Cheat


Post New Thread Reply   
 
Thread Tools Display Modes
Author
J_Tanzanite
Member
Join Date: Aug 2018
Location: Norway
Plugin ID:
6943
Plugin Version:
1.6.1
Plugin Category:
Server Management
Plugin Game:
Any
Plugin Dependencies:
    Servers with this Plugin:
     
    Plugin Description:
    A simplistic Anti-Cheat for source games
    Old 02-12-2020 , 19:05   [ANY] Little Anti-Cheat
    Reply With Quote #1

    Little Anti-Cheat 1.6.1

    Description:
    This is a simplistic Anti-Cheat for sourcegames, which will catch some cheaters/hackers (not all).
    Little Anti-Cheat also patches some exploits.

    Lilac is compatible with Sourcemod Anti-Cheat and will not conflict with it.
    That said, there are some notes about SMAC later on that you should read if you have SMAC installed.

    Lilac comes with Sourcebans++ support out of the box.
    It is not required for Lilac to run, you can use Little Anti-Cheat without it.

    Supported Games:
    - Team Fortress 2
    - Counter-Strike:Global Offensive
    - Day of Defeat: Source
    - Left 4 Dead 2
    - Left 4 Dead 1 (Still a little unsure about this game)

    Untested games, but should work in:
    - Counter-Strike:Source (waiting for confirmation)
    - Half-Life 2 : DeathMatch



    Features:
    - Angle Cheat detector (Detects basic angle exploits used by cheats, like Pitch AA, Legit Anti-Backstab and Duckspeed).
    - Chat Clear Detector (Detects when cheaters clear the chat).
    - Basic ConVar checker (Checks clients for invalid ConVars, like sv_cheats).
    - NoLerp Detector (Detects invalid interpolation, done by some cheats to get higher aimbot accuracy).
    - Bhop Detector (Detects perfect bunny hops, shouldn't detect legit scripts or AHK).
    - Basic Aimbot detector (Doesn't detect all aimbots, but some. Also detects projectile aimbots).
    - AimLock Detector (Detects constant aimsnaping onto targets).
    - Anti-Duck-Delay/FastDuck (CS:GO only, detects duck delay bypass).

    Extra Features:
    - Angle Cheat Patch (Patches angle-cheats. Also prevents console getting spammed).
    - Backtrack Patch (Disabled by default).
    - FakeLatency/High ping kicker (Disabled by default).
    - Interp Exploit Kicker (Kicks players trying to abuse interp to get easy facestabs (cl_interp 0.5)).



    Important Notice!
    From version 1.6.0, Bhop bans will now by default only last a month!
    If you wish to use the ConVar "lilac_ban_length" value, add this line to the config file at the bottom:
    Code:
    lilac_set_ban_length bhop -1


    ConVars and Commands:
    Code:
    lilac_enable               [1/0 (Default 1)]         Enables or disables Little Anti-Cheat.
    lilac_welcome              [1/0 (Default 0)]         Welcome players saying the server is protected.
    lilac_sourcebans           [1/0 (Default 1)]         Ban via sourcebans++ if it is installed.
    lilac_materialadmin        [1/0 (Default 1)]         Ban via Material-Admin if it is installed.
    
    lilac_log                  [1/0 (Default 1)]         Logs bans and cheat suspicions.
    lilac_log_extra            [2->0 (Default 1)]        0 = Disabled. 1 = Log extra info on ban. 2 = Log extra info on all detections.
    lilac_log_misc             [1/0 (Default 0)]         log when players are kicked for misc features (convar response failure, high ping, interp exploit).
    
    lilac_ban                  [1/0 (Default 1)]         Ban cheaters, disable this if you wanna test Lilac before fully trusting it with bans.
    lilac_ban_length           [999+/0 (Default 0)]      Ban length in minutes, 0 = forever.
    lilac_angles               [1/0 (Default 1)]         Detect angle cheats (Pitch AA, Duckspeed and Legit Anti-Backstab).
    lilac_angles_patch         [1/0 (Default 1)]         Patch angle cheats.
    
    lilac_chatclear            [1/0 (Default 1)]         Detect chat-clear (cheats clearing chat with newlines).
    lilac_convar               [1/0 (Default 1)]         Detect basic ConVar violations.
    lilac_nolerp               [1/0 (Default 1)]         Detect NoLerp.
    
    lilac_bhop                 [2->0 (Default 2)]        Detect bhop cheats (0 = Disabled, 1 = ban on 10 bhops, 2 = ban on 5 if jump isn't spammed).
    lilac_aimbot               [5+/1/0 (Default 5)]      Detect Basic Aimbots (0 = Disabled, 1 = Log only, 5+ = Ban on n'th detection, minimum possible is 5!).
    lilac_aimbot_autoshoot     [1/0 (Default 1)]         Detect autoshoot.
    lilac_aimlock              [5+/1/0 (Default 10)]     Detect Aimlock (0 = Disabled, 1 = Log only, 5+ = Ban on n'th detection, minimum possible is 5!).
    lilac_aimlock_light        [1/0 (Default 1)]         Only process at most 5 players who are suspicious.
    
    lilac_anti_duck_delay      [1/0 (Default 1)]         CS:GO only, detect Anti-Duck-Delay/FastDuck.
    lilac_noisemaker           [1/0 (Default 0)]         TF2 only, (BETA, MAY NOT WORK) detect Noisemaker spam, only logs! Doesn't ban!
    
    lilac_backtrack_patch      [2->0 (Default 0)]        Patch backtracking cheats. 0 = Disabled. 1 = Randomized (Not recommended). 2 = Lock (Recommended patch method).
    lilac_backtrack_tolerance  [3->0 (Default 0)]        How tolerant the backtrack patch will be of tickcount changes.
    lilac_max_ping             [100+/0 (Default 0)]      Temporarily ban players for 3 minutes (Doesn't use Sourcebans!) Minimum possible is 100.
    lilac_max_ping_spec        [90->30 (Default 0)]      Move players with a high ping to spectators and warn them after X many seconds.
    
    lilac_max_lerp             [105+/0 (Default 105)]    Kick players who attempt to exploit interpolation (cl_interp 0.5). Anything lower than 105 = Disabled.
    lilac_loss_fix             [1/0 (Default 1)]         Ignore some detections on laggy players (packet loss).
    lilac_auto_update          [1/0 (Default 0)]         Automatically update Little Anti-Cheat, requires updater plugin.
    
    lilac_log_date             [{year}/{month}/{day} {hour}:{minute}:{second}]  Lets you pick date format in logs (see command lilac_date_list for more info).
    Commands:
    - lilac_date_list - Lists all date formatting options.
    - lilac_ban_status - Print banning status, tells you where bans will go (Sourcebans++, Material-Admin or basebans).
    - lilac_set_ban_length - Sets ban length exception for specific cheat features.

    Date formats:
    In case you don't like year/month/day, you can setup your own date preferences with the "lilac_log_date" convar.
    Examples:
    - lilac_log_date "{year}/{month}/{day} {hour}:{minute}:{second}"
    - lilac_log_date "{month}/{day}/{year} {12hour}:{minute}:{second} {pm}"
    - lilac_log_date "" (No date / time)

    If you want something more complicated/detailed, you can use the "{raw}" option to skip all formatting.
    You can then insert your own stuff like so:
    - lilac_log_date "{raw} %Y/%m/%d %H:%M:%S"

    Set Ban Length:
    The ConVar "lilac_ban_length" controls how long a ban should last in minutes (0 = forever).
    However, if you wish to change the ban length for one or more specific cheat features, you can do it like this:
    - lilac_set_ban_length bhop 15
    This will set the ban length for bhop for 15 minutes, instead of using the value of "lilac_ban_length".
    Here's a list of possible options:
    - lilac_set_ban_length angles <minutes>
    - lilac_set_ban_length chatclear <minutes>
    - lilac_set_ban_length convar <minutes>
    - lilac_set_ban_length nolerp <minutes>
    - lilac_set_ban_length bhop <minutes>
    - lilac_set_ban_length aimbot <minutes>
    - lilac_set_ban_length aimlock <minutes>
    - lilac_set_ban_length antiduckdelay <minutes>

    If you wish to revert to using the ConVar "lilac_ban_length" again, use set the time in minutes to "-1", like so:
    - lilac_set_ban_length bhop -1



    Installation and Setup:
    1: Download the ZIP file and unpack all the files to their respective folders.
    2: Type "sm plugins load lilac.smx" in console.

    Configuration and Detection Logs:
    All cheat detections are logged to addons/sourcemod/logs/lilac.log
    The configuration file will automatically be generated in your cfg/sourcemod/lilac_config.cfg
    The default values are fine as is, and should work optimally.
    Optional features are disabled by default.

    SMAC (Sourcemod Anti-Cheat) notes:
    If you already have SMAC installed, and have the convar/cvar module installed, it is recommended that you disable Little Anti-Cheat's convar checker.
    You can do this by changing "lilac_convar" to "0" in the cfg/sourcemod/lilac_config.cfg file.

    It is NOT advised that you run Lilac's backtrack patch (lilac_backtrack_patch) if you are running SMAC's Eye-Test module.
    Patching Backtracking while running SMAC's Eye-Test module may cause false detections for SMAC.
    Either disable the Eye-Test module, disable Eye-Test bans or disable the backtrack patch in Lilac.
    The backtrack patch (lilac_backtrack_patch) is disabled by default for this reason.



    Updates and Future plans:
    Updates:
    Quote:
    1.6.1
    - Fixed bug where angle-cheats would ban all players in L4D and L4D2.

    1.6.0
    - Removed redundant code.
    - Added new cheat detection feature for CS:GO (Only), Anti-Duck-Delay/FastDuck.
    - Added new BETA (May not work) TF2 cheat detection for Infinite Noisemaker Spam. Since it is in BETA, it WON'T ban, only log! If no false positives are reported, it will perma ban in the future.
    - Added BETA auto updater support.
    - Added new ConVar "lilac_anti_duck_delay" (Default 1), detect Anti-Duck-Delay/FastDuck in CS:GO.
    - Added new ConVar "lilac_noisemaker" (Default 0), detect infinite noisemaker in TF2.
    - Added new ConVar "lilac_auto_update" (Default 0), enable this to auto update (Requires updater plugin).
    - Added new ConVar "lilac_max_ping_spec" (Default 0), moves players with high ping into team spectator and warns them about potential kick after x many seconds.
    - Added Russian warning if MA wasn't included when compiled (command: lilac_ban_status).
    - Added new backtrack patch method, Lock. This patch method shouldn't affect laggy legit players much.
    - Added a delay for forwards so they won't get spammed to other plugins.
    - Fixed overly long ConVar description for "lilac_max_lerp".
    - Fixed typo in max ping ConVar description, Thanks 4LEJ4NDRO/ALEJANDRO!
    - Fixed a typo in code and translations files.
    - Updated Bhop to have a lower chance of false positives, thanks M4rkey and Thundy!
    - Updated Ping kicker to wait 100 seconds before kicking instead of 45 seconds.
    - Updated Ping kicker to skip testing players who have not been in game for more than 120 seconds.
    - Updated default ban length for Bhop to be 1 month instead of permanently, do "lilac_set_ban_length bhop -1" to use the ConVar value "lilac_ban_length" instead.
    - Updated Aimlock to check newly connected players for AimLock.
    - Updated command "lilac_ban_status" to tell you if bans will go through Sourcebans++, Material-Admin or Basebans.
    - Updated command "lilac_ban_status" to show if native ban functions are available.
    - Updated so ban status will be printed after all plugins are loaded along with startup message.
    - Updated how banning works through Sourcebans++/MaterialAdmin, it will now check if the native exists and not if the plugin by name is loaded.
    - Updated ConVar checker to be more basic and less CPU intensive.

    1.5.1 (Never officially released on AM)
    - Added new command "lilac_ban_status", which prints to server console the status of Sourcebans++ and Material-Admin.
    - Removed mat_fullbright comparison, despite it having been removed from queries.

    1.5.0
    - Added new ConVar "lilac_aimbot_autoshoot" (Default 1), enables autoshoot detection.
    - Added new command "lilac_set_ban_length", can be used to overwrite ban length for specific cheat detections.
    - Added German, Spanish, Portuguese, Turkish and Ukrainian translations.
    - Fixed false Angle-Cheat detections in L4D (Thanks finishlast).
    - Fixed false ConVar detection "mat_fullbright" on some community made maps. Lilac will no longer check for this ConVar.
    - Fixed some errors in Aimlock detections.

    1.4.0 (Never officially released on AM)
    - Added support for MateralAdmin (Thanks panikajo and CrazyHackGUT).
    - Added new ConVar "lilac_ban_length" (Default 0), sets ban length in minutes (0 = Forever).

    1.3.0
    - Fixed false Angle-Cheat detections in Left4Dead2 (Thanks larrybrains).
    - Updated ConVar "lilac_max_lerp" to be disabled if less than 105.
    - Updated where detection logs are stored, from "{gamefolder}/lilac.log" to "{gamefolder}/addons/sourcemod/logs/lilac.log".

    1.2.0 (Never officially released on AM)
    - Added new ConVar "lilac_ban" (Default 1), set to 0 to disable all banning (useful for those who want to test Lilac before fully trusting it).
    - Updated code syntax so older versions of sourcemod can compile and run Lilac.
    - Updated ConVar updates to be cleaner, thanks MAGNAT2645!
    - Updated ConVar checker to not kick unresponsive clients so quickly.
    - Updated the default config location to "cfg/sourcemod", if the old config file is still in the "cfg/" folder, the old file will still be used.

    1.1.0 (Never officially released on AM)
    - Added new forward for blocking cheat detections (Should be used by bhop/VIP plugins).
    - Fixed some false positives for Aimlock detections (Hopefully, still not sure what caused issues for others).
    - Fixed aimlock lightweight mode testing 6 players, not 5 (Typos are fun ).
    - Updated backtrack patch to last 1 second instead of 5 (Laggy players should not get punished so harshly now).

    1.0.0
    - Rewrote large portions of the Anti-Cheat (A complete rewrite?).
    - Removed OnGameFrame check in TF2 for taunting players.
    - Added translation support, Lilac now supports French, Russian, Norwegian and English.
    - Added startup message when Little Anti-Cheat is loaded.
    - Added TF2 forward for checking when players are taunting.
    - Added new ConVar "lilac_aimlock_light" (Default 1), if enabled, won't check for aimlocks on all players constantly to prevent lag on some servers.
    - Added new ConVar "lilac_welcome" (Default 0) saying the server is protected.
    - Added new ConVar "lilac_loss_fix" (Default 1), if enabled, ignores some detections on laggy players (packet loss).
    - Added new ConVar "lilac_log_misc" (Default 0), if enabled, lilac will log when players are kicked for misc features (high ping, interp exploit and query failure).
    - Added new forward when players are banned.
    - Fixed plugin not loading in CS:GO (Thanks Bottiger).
    - Fixed extreme rare case where aimbot detector would look at the wrong victim.
    - Fixed cases where Lilac would look a little too far back at tick history.
    - Fixed so connecting players can't inherit angle history from previous players.
    - Fixed missing punctuation in NoLerp detection log message.
    - Fixed a bug where aimlock detections would not expire after 10 minutes, but aimbot detections would (Typos are fun).
    - Fixed sourcebans++ compatibility not working (Thanks foon).
    - Fixed so repeat tests (aimbot) aren't done between close players.
    - Updated interp exploit kicker to display the correct interp convar value.
    - Updated several comments and ConVar descriptions to be more clear.
    - Updated Aimlock detector to ignore players who are too close to each other.
    - Updated Aimlock detector to consider packet loss (if lilac_loss_fix is enabled).
    - Updated Aimbot detector to consider packet loss (if lilac_loss_fix is enabled, total_delta detection works regardless).
    - Updated Aimbot detector to check for things it previously wouldn't under certain circumstances.
    - Updated ConVar detector to query for ConVars every 5 seconds instead of every 2 seconds.
    - Updated Backtrack patch to last 5 seconds instead of 10.
    - Updated Backtrack patch to use correct random tick ranging from -200ms to max 200ms based on ping.
    - Updated "lilac_log_extra" to have an option to also log extra information on every detection, suspicions and kick.
    - Updated coding style somewhat, to make it easier to follow and understand.

    0.7.1
    - Fixed potential for false NoLerp ban if sv_maxupdaterate is updated mid-game and then plugin is loaded.
    - Changed high ping players getting kicked after 100 seconds to 45 seconds.
    - Changed Aimlock detection to increment after two snaps instead of three.
    - Changed so cheaters banned for Chat-Clear can't continue spamming chat.
    - Removed "Full" backtrack patch method, it was never used anyway (Old stuff from development/testing).
    - Changed backtrack patch to modify tickcount to a random value ranging from 400ms instead of 200ms.
    Future plans:
    I wish to add more cheat detection methods, specifically for CS:GO.

    I also plan on supporting more games. Currently, Counter-Strike:Source is technically supported.
    I just haven't gotten any clear confirmation that it does work from server owners yet. Once I get that, it will be officially listed as supported.

    I've gotten some complaints regarding ban reasons listed on Sourcebans++, a future update will add an option to set all ban reasons in the server's language instead of the player's language.



    Special thanks to:
    Bottiger - For fixing the plugin not loading in CS:GO & General criticisms.
    foon - For fixing sourcebans++ support not working.
    MAGNAT2645 - For informing me of a better method of handling convar changes.
    Larry/Larrybrains - For informing about false Angle-Cheat detections in L4D2.
    Finishlast - For informing me about false Angle-Cheat detections in L4D (1).
    panikajo and CrazyHackGUT - For helping me add support for MaterialAdmin.
    M4rkey and Thundy - For Bhop report.
    4LEJ4NDRO/ALEJANDRO - For fixing a typo.


    Translation authors:
    Simplified Chinese by RoyZ (https://github.com/RoyZ-CSGO).
    Brazilian Portuguese by:
    - SheepyChris (https://github.com/SheepyChris).
    - Perkzitos (https://github.com/Perkzitos).
    French By Rasi.
    Spanish By ALEJANDRO.
    Ukrainian By panikajo.
    Turkish By ShiroNje.
    English & Norwegian By J_Tanzanite.
    ... The rest wanted to stay anonymous... For some reason.

    Videos:
    Aimbot & Backtrack showcase (https://www.youtube.com/watch?v=mEuIBwln5ts)
    Attached Files
    File Type: zip Little Anti-Cheat.zip (63.2 KB, 101 views)

    Last edited by J_Tanzanite; 07-29-2020 at 04:23. Reason: New version 1.6.1
    J_Tanzanite is offline
    MAGNAT2645
    Senior Member
    Join Date: Nov 2015
    Location: AlliedMods.net
    Old 03-09-2020 , 13:35   Re: [TF2] Little Anti-Cheat
    Reply With Quote #2

    In cvar_change, you can actually replace this type of check:
    Code:
    	if (StrEqual(cvarname, "lilac_enable", false)) {
    		icvar[CVAR_ENABLE] = StringToInt(newValue, 10);
    	} else if (StrEqual(cvarname, "lilac_sourcebans", false)) {
    		icvar[CVAR_SB] = StringToInt(newValue, 10);
    to:
    Code:
    	if ( convar == hCvar[CVAR_ENABLE] ) { // Store ConVar handles globally as Handle or ConVar (on new syntax) -typed
    		icvar[CVAR_ENABLE] = StringToInt(newValue, 10);
    	} else if ( convar == hCvar[CVAR_SB] ) {
    		icvar[CVAR_SB] = StringToInt(newValue, 10);
    
    	// etc...
    	// The thing is that ConVar Handle is never changed after creating so you don't need to check for convar name
    	// just directly check convar handle
    Also, you should probably add translation support for hardcoded messages.
    __________________

    Last edited by MAGNAT2645; 03-09-2020 at 13:41.
    MAGNAT2645 is offline
    CrazyGhostRider
    Member
    Join Date: Apr 2014
    Old 03-17-2020 , 20:40   Re: [TF2] Little Anti-Cheat
    Reply With Quote #3

    Ban through sourcebans ++ does not work. The player was banned in the usual way.
    lilac_sourcebans = 1
    CrazyGhostRider is offline
    J_Tanzanite
    Member
    Join Date: Aug 2018
    Location: Norway
    Old 03-23-2020 , 09:29   Re: [TF2] Little Anti-Cheat
    Reply With Quote #4

    Quote:
    Originally Posted by MAGNAT2645 View Post
    In cvar_change, you can actually replace this type of check:
    Code:
    	if (StrEqual(cvarname, "lilac_enable", false)) {
    		icvar[CVAR_ENABLE] = StringToInt(newValue, 10);
    	} else if (StrEqual(cvarname, "lilac_sourcebans", false)) {
    		icvar[CVAR_SB] = StringToInt(newValue, 10);
    to:
    Code:
    	if ( convar == hCvar[CVAR_ENABLE] ) { // Store ConVar handles globally as Handle or ConVar (on new syntax) -typed
    		icvar[CVAR_ENABLE] = StringToInt(newValue, 10);
    	} else if ( convar == hCvar[CVAR_SB] ) {
    		icvar[CVAR_SB] = StringToInt(newValue, 10);
    
    	// etc...
    	// The thing is that ConVar Handle is never changed after creating so you don't need to check for convar name
    	// just directly check convar handle
    Also, you should probably add translation support for hardcoded messages.
    Ahh, cool, I'll update that then. ^-^

    As for translations... Never really worked with them, I'll look into it tho.
    I am ignorant on the topic of translations, so pardon my dumb question here, but but doesn't using translations also force the plugin to require them in order to load?
    One of the things I wanted Lilac to be, was a single file, so that it would be easier to install.

    Lastly, Sorry for my slow reply, been fairly busy with real life lately (who hasn't been).
    I have been working on a massive update tho, version 1.0.0 is right around the corner.
    I have tested it a bit, but I won't published version 1.0.0 here until I'm certain it isn't going to create problems.
    You can find the latest version here: https://github.com/J-Tanzanite/Littl...lac_rewrite.sp
    J_Tanzanite is offline
    J_Tanzanite
    Member
    Join Date: Aug 2018
    Location: Norway
    Old 03-23-2020 , 09:32   Re: [TF2] Little Anti-Cheat
    Reply With Quote #5

    Quote:
    Originally Posted by CrazyGhostRider View Post
    Ban through sourcebans ++ does not work. The player was banned in the usual way.
    lilac_sourcebans = 1
    OOF...
    Ok so, I've never used sourcebans, and I don't really have a way to test it.
    So it's kinda hard to fix that...
    I'll try to look into it though.
    If anyone else have the same problem, please tell me, and if anyone know how to fix it... pls halp D:
    J_Tanzanite is offline
    venter25
    Member
    Join Date: Jul 2019
    Old 03-27-2020 , 11:31   Re: [TF2] Little Anti-Cheat
    Reply With Quote #6

    Thank you. Running this on my TF2 Server.
    venter25 is offline
    foon
    Member
    Join Date: Dec 2018
    Old 03-29-2020 , 11:24   Re: [TF2] Little Anti-Cheat
    Reply With Quote #7

    Quote:
    Originally Posted by J_Tanzanite View Post
    OOF...
    Ok so, I've never used sourcebans, and I don't really have a way to test it.
    So it's kinda hard to fix that...
    I'll try to look into it though.
    If anyone else have the same problem, please tell me, and if anyone know how to fix it... pls halp D:
    Since you are using the SB++ include, you need to be checking if Sourcebans++ exists, not Sourcebans.
    You have to replace it in three locations. Line 354, 398, 404 (in lilac_rewrite.sp). Replace "sourcebans" with "sourcebans++".

    Last edited by foon; 03-29-2020 at 11:55.
    foon is offline
    J_Tanzanite
    Member
    Join Date: Aug 2018
    Location: Norway
    Old 04-01-2020 , 15:51   Re: [TF2] Little Anti-Cheat
    Reply With Quote #8

    Quote:
    Originally Posted by foon View Post
    Since you are using the SB++ include, you need to be checking if Sourcebans++ exists, not Sourcebans.
    You have to replace it in three locations. Line 354, 398, 404 (in lilac_rewrite.sp). Replace "sourcebans" with "sourcebans++".
    Ahh, thank you!
    I've updated the lines and added you to the credits for that patch (Will be adding a credit listing later).
    Also, added translations.
    Doing some final testing now before releasing version 1.0.0 here.
    J_Tanzanite is offline
    foon
    Member
    Join Date: Dec 2018
    Old 04-04-2020 , 15:24   Re: [TF2] Little Anti-Cheat
    Reply With Quote #9

    You also might want to tone down the log info, it wraps way to easy and makes it a pain to read.

    Code:
    2020/02/29 03:49:32 [Version 0.7.1] {Name: "A user name" | SteamID: STEAM_0:1:528111416 | IP: 72.10.10.10} is suspected of using an aimbot (Detection: 6 | Delta: 50 | TotalDelta: 50 | Detected: Aim-Snap Aim-Snap2 Angle-Repeat).
    
    2020/02/29 03:49:32 [0.7.1] {"A user name" | STEAM_0:1:528111416 | 72.10.10.10} aimbot (Detection: 6 | Delta: 50 | TotalDelta: 50 | Detected: Aim-Snap Aim-Snap2 Angle-Repeat).
    (I don't think you need to add "suspected" since you gave people a warning in your OP that there can be false positives).
    foon is offline
    J_Tanzanite
    Member
    Join Date: Aug 2018
    Location: Norway
    Old 04-05-2020 , 12:33   Re: [TF2] Little Anti-Cheat
    Reply With Quote #10

    Quote:
    Originally Posted by foon View Post
    You also might want to tone down the log info, it wraps way to easy and makes it a pain to read.

    Code:
    2020/02/29 03:49:32 [Version 0.7.1] {Name: "A user name" | SteamID: STEAM_0:1:528111416 | IP: 72.10.10.10} is suspected of using an aimbot (Detection: 6 | Delta: 50 | TotalDelta: 50 | Detected: Aim-Snap Aim-Snap2 Angle-Repeat).
    
    2020/02/29 03:49:32 [0.7.1] {"A user name" | STEAM_0:1:528111416 | 72.10.10.10} aimbot (Detection: 6 | Delta: 50 | TotalDelta: 50 | Detected: Aim-Snap Aim-Snap2 Angle-Repeat).
    (I don't think you need to add "suspected" since you gave people a warning in your OP that there can be false positives).
    Yeah, I might wanna look into shortening those messages a bit...
    Or at least add an option to... Didn't even hit me that might be an issue.

    However, when it comes to "suspected"... I can't really remove that one.

    The first time Lilac is ran, it will add some lines at the top of the log file to reassure admins that there can be false positives for "suspected" detections.
    My reasoning behind doing this, is that I've seen people overreact to minor stuff...
    So I've attempted to make the language used in Lilac to be very clear so that admins don't think Lilac is "perfect" (nothing is).

    Also, I've finished testing version 1.0.0 now, and it is ready. Going to publish it here later today.
    I highly recommend you upgrade to that version, as it fixes some bugs and fixes some potential overhead.
    J_Tanzanite is offline
    Reply


    Thread Tools
    Display Modes

    Posting Rules
    You may not post new threads
    You may not post replies
    You may not post attachments
    You may not edit your posts

    BB code is On
    Smilies are On
    [IMG] code is On
    HTML code is Off

    Forum Jump


    All times are GMT -4. The time now is 04:27.


    Powered by vBulletin®
    Copyright ©2000 - 2020, vBulletin Solutions, Inc.
    Theme made by Freecode