[Weasel]

Just an FYI ... testing this (version 1.7.4-3) on Team Fortress 2 Classic, and it seems to be working fine - for anyone quasi-interested.

.

[Weasel]

I can report Little Anti-Cheat (Lilac) working reasonably well on Fistful of Frags, with one exception:

When I first enabled it, I got a slew of "Angle-Cheat" detections, including a several regular players I'm sure are not cheating in any way. So, I treaded those as "false-positive", re-configured Lilac to not detect "Angle-Cheats", and unbanned everybody Lilac auto-banned for that detection.

In fof/cfg/sourcemod/lilac_config.cfg updated this section:

// Detect Angle-Cheats (Basic Anti-Aim, Legit Anti-Backstab and Duckspeed).
// -1 = Log only.
// 0 = Disabled.
// 1 = Enabled.
// -
// Default: "1"
// Minimum: "-1.000000"
// Maximum: "1.000000"
lilac_angles "0"   // <--- set to zero to disable.

PS: I opened an issue in the GitHub for this (Issue #177).

[Weasel]

Originally Posted by Weasel Just an FYI ... testing this (version 1.7.4-3) on Team Fortress 2 Classic, and it seems to be working fine - for anyone quasi-interested. .

Just updating the I have been running Little Anti-Cheat (Lilac) for some time now on Team Fortress 2 Classic. I have not encountered any apparent "false-positives" or other issues to report.

[micmacx]

Hi,
On 1.7.4 version :

PHP Code:

L 05/12/2023 - 13:05:43: SourceMod error session started
L 05/12/2023 - 13:05:43: Info (map "dod_fightzone_voodoo_final") (file "/home/micmacx/steam/dod_s/dod/addons/sourcemod/logs/errors_20230512.log")
L 05/12/2023 - 13:05:43: [SM] Exception reported: Client 4 is not connected
L 05/12/2023 - 13:05:43: [SM] Blaming: lilac.smx
L 05/12/2023 - 13:05:43: [SM] Call stack trace:
L 05/12/2023 - 13:05:43: [SM]   [0] GetClientUserId
L 05/12/2023 - 13:05:43: [SM]   [1] Line 304, lilac/lilac_stock.sp::lilac_ban_client
L 05/12/2023 - 13:05:43: [SM]   [2] Line 123, lilac/lilac_lerp.sp::detected_nolerp
L 05/12/2023 - 13:05:43: [SM]   [3] Line 77, lilac/lilac_lerp.sp::timer_check_lerp
L 05/12/2023 - 13:20:44: Error log file session closed. 


PHP Code:

=========[Notice]=========
Thank you for installing Little Anti-Cheat 1.7.4!
Just a few notes about this Anti-Cheat:

If a player is logged as "suspected" of using cheats, they are not necessarily cheating.
If the suspicions logged are few and rare, they are likely false positives.
An automatic ban is triggered by 5 or more "suspicions" or by one "detection".
If you think a ban may be incorrect, please do not hesitate to let me know.

That is all, have a wonderful day~



2023/05/12 13:05:43 [Version 1.7.4] {Name: "TheBrave" | SteamID: STEAM_ID_STOP_IGNORING_RETVALS | IP: 89.156.250.159} was detected and banned for NoLerp (0.000000ms).
    Pos={232,-315,-351}, Angles={4.60949,64.58837,0.00000}, Map="dod_fightzone_voodoo_final", Team={2}, Weapon="weapon_garand", Latency={Inc:-1.000000,Out:-1.000000}, Loss={Inc:-1.000000,Out:-1.000000}, Choke={Inc:-1.000000,Out:-1.000000}, ConnectionTime={0.000000 seconds}, GameTime={5.909999 seconds} 


A second bug :
I have a friend, he have a mouse with rapid fire, with 8clics/300ms ==> 26clics/s, he was kicked.
With 62clics/300ms ==> 206 clics/s he's not kicked.

[Weasel]

My cfg/sourcemod/lilac_config.cfg file seemingly keeps getting over-written with the default configuration? Not sure where this is coming-from, does Lilac have a built-in auto-update that would over-write the .CFG?

This is a big deal for some of my servers. In particular for Fistful of Frags (FoF), where I have to disable angle-cheats detection due to false-positives in that game. Consequently, I have to keep lilac_angles set to "0" in my FoF servers - which keeps getting messed-up when the default config keeps getting slammed on it.

[azalty]

Originally Posted by Weasel My cfg/sourcemod/lilac_config.cfg file seemingly keeps getting over-written with the default configuration? Not sure where this is coming-from, does Lilac have a built-in auto-update that would over-write the .CFG? This is a big deal for some of my servers. In particular for Fistful of Frags (FoF), where I have to disable angle-cheats detection due to false-positives in that game. Consequently, I have to keep lilac_angles set to "0" in my FoF servers - which keeps getting messed-up when the default config keeps getting slammed on it.

The plugin recently changed to another config system that could better handle convar changes.
This change was implemented by myself as I know this config system worked well for me in the past.

I'm not aware of any bug that could reset your convars, but I do know convars from other plugins or comments WILL be erased by this system IF entered in lilac's config file.
The config file will be rebuilt entirely when the plugin is first started, but it will get every convar that is in it and save their values when rebuilding the config file.

Version updating should be seemless and shouldn't reset your config file as well.

Do you mind sharing more information or discussing about this with me? You can reach me on discord: azalty#9721 - might be better to talk.

[Weasel]

Originally Posted by azalty The config file will be rebuilt entirely when the plugin is first started

I noticed that, because my comment changes also kept getting reverted too.
But, the CVAR was definitely getting rolled-back from "0" to "1".
Like over-writing the entire contents, and not making the expected changes for altered CVAR values.

Just checked it again today, and at this point, seems to be working as expected though (preserving the CVAR as "0").

PS: I am going to set lilac_angles to "-1" (log only), and see if it stays preserved.

[Weasel]

Originally Posted by Weasel I am going to set lilac_angles to "-1" (log only), and see if it stays preserved.

Just a quick update to close the issue out, it appears now to be preserving the existing CVAR's as expected. Various changes I made to CVARs were preserved after my nightly restarts (of course all comment changes are lost, but no big deal there). Thanks for the follow up!

PS: Sorry I never opened a GitHub issue for this one, because I wasn't sure if it was something up with my own configuration. (unlike the false-positive issues with FoF reported there: https://github.com/J-Tanzanite/Littl...eat/issues/185, and https://github.com/J-Tanzanite/Littl...eat/issues/177)

[JLmelenchon]

Hardware macro is not detected, a simple turbo button on gamepad will bypass detections.

[finishlast]

I upgraded from 1.7.1 to 1.7.4 from the github and the server now basically clears the whole (l4d1) infected team every now and then (if the round is long enough for 5 detections).

It banned myself too and I am pretty sure I'm not cheating.

Almost every entry in lilac.log is about supstected aimlock but only for infected team it seems.

Same people on survivor teams won't get detected.

Maybe it happens when you rightclick teleport to players while in ghost mode? And do that very fast? I dont see a reason to check infected for that anyways, maybe disable it for infected completely.

2023/10/26 22:48:51 [Version 1.7.4] {Name: "xxxxxxxxx" | SteamID: xxxxxxxxx | IP: x} is suspected of using an aimlock (Detection: 4).
	Pos={6375,1256,238}, Angles={2.65319,45.57678,0.00000}, Map="l4d_vs_farm05_cornfield", Team={3}, Weapon="weapon_boomer_claw", Latency={Inc:0.000473,Out:0.116188}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.008581,Out:0.000000}, ConnectionTime={3845.219482 seconds}, GameTime={1104.250000 seconds}
2023/10/26 22:49:00 [Version 1.7.4] {Name: "xxxxxxxxx" | SteamID: xxxxxxxxx | IP: x} is suspected of using an aimlock (Detection: 4).
	Pos={6809,1000,238}, Angles={4.29016,23.53271,0.00000}, Map="l4d_vs_farm05_cornfield", Team={3}, Weapon="weapon_smoker_claw", Latency={Inc:0.000413,Out:0.042605}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.412110,Out:0.000000}, ConnectionTime={648.019653 seconds}, GameTime={1113.750000 seconds}
2023/10/26 22:50:03 [Version 1.7.4] {Name: "xxxxxxxxx" | SteamID: xxxxxxxxx | IP: x} is suspected of using an aimlock (Detection: 5).
	Pos={5443,1733,203}, Angles={1.17553,74.89929,0.00000}, Map="l4d_vs_farm05_cornfield", Team={3}, Weapon="weapon_hunter_claw", Latency={Inc:0.000474,Out:0.114811}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.009129,Out:0.000000}, ConnectionTime={3917.219238 seconds}, GameTime={1176.250000 seconds}
2023/10/26 22:50:03 [Version 1.7.4] {Name: "xxxxxxxxx" | SteamID: xxxxxxxxx | IP: x} was banned for Aimlock.
	Pos={5443,1733,203}, Angles={1.17553,74.89929,0.00000}, Map="l4d_vs_farm05_cornfield", Team={3}, Weapon="weapon_hunter_claw", Latency={Inc:0.000474,Out:0.114811}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.009129,Out:0.000000}, ConnectionTime={3917.219238 seconds}, GameTime={1176.250000 seconds}
2023/10/26 22:50:17 [Version 1.7.4] {Name: "xxxxxxxxx" | SteamID: xxxxxxxxx | IP: x} is suspected of using an aimlock (Detection: 5).
	Pos={4729,1219,443}, Angles={16.15539,73.28979,0.00000}, Map="l4d_vs_farm05_cornfield", Team={3}, Weapon="weapon_hunter_claw", Latency={Inc:0.000559,Out:0.043417}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.407300,Out:0.000000}, ConnectionTime={724.519775 seconds}, GameTime={1190.250000 seconds}
2023/10/26 22:50:17 [Version 1.7.4] {Name: "xxxxxxxxx" | SteamID: xxxxxxxxx | IP: x} was banned for Aimlock.
	Pos={4729,1219,443}, Angles={16.15539,73.28979,0.00000}, Map="l4d_vs_farm05_cornfield", Team={3}, Weapon="weapon_hunter_claw", Latency={Inc:0.000559,Out:0.043417}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.407300,Out:0.000000}, ConnectionTime={724.519775 seconds}, GameTime={1190.250000 seconds}

As for now I go back to 1.7.1