[J_Tanzanite]

Originally Posted by MaloModo How would this be with Fistful of Frags? I am running SMAC which seems fine. https://store.steampowered.com/app/2...tful_of_Frags/

Fistful of Frags has not been tested, so I don't know.

I don't see a reason why it wouldn't work, so I suspect that Lilac would work for that game...
But the only way to know for sure would be to test it.

[Rav1sh]

Hello, I've been experiencing these errors the last few days.

L 11/02/2020 - 23:47:20: [SM] Exception reported: Translation failed: invalid client index 1601069410 (arg 6)
L 11/02/2020 - 23:47:20: [SM] Blaming: lilac.smx
L 11/02/2020 - 23:47:20: [SM] Call stack trace:
L 11/02/2020 - 23:47:20: [SM]   [0] Format
L 11/02/2020 - 23:47:20: [SM]   [1] Line 2236, C:\scripting\lilac.sp::lilac_ban_client
L 11/02/2020 - 23:47:20: [SM]   [2] Line 1796, C:\scripting\lilac.sp::lilac_detected_anti_duck_delay
L 11/02/2020 - 23:47:20: [SM]   [3] Line 1573, C:\scripting\lilac.sp::OnPlayerRunCmd
L 11/02/2020 - 23:48:08: [SM] Exception reported: Translation failed: invalid client index 1601069410 (arg 6)
L 11/02/2020 - 23:48:08: [SM] Blaming: lilac.smx
L 11/02/2020 - 23:48:08: [SM] Call stack trace:
L 11/02/2020 - 23:48:08: [SM]   [0] Format
L 11/02/2020 - 23:48:08: [SM]   [1] Line 2230, C:\scripting\lilac.sp::lilac_ban_client
L 11/02/2020 - 23:48:08: [SM]   [2] Line 1903, C:\scripting\lilac.sp::lilac_detected_bhop
L 11/02/2020 - 23:48:08: [SM]   [3] Line 1628, C:\scripting\lilac.sp::OnPlayerRunCmd
L 11/02/2020 - 23:58:07: [SM] Exception reported: Translation failed: invalid client index 1601069410 (arg 6)
L 11/02/2020 - 23:58:07: [SM] Blaming: lilac.smx
L 11/02/2020 - 23:58:07: [SM] Call stack trace:
L 11/02/2020 - 23:58:07: [SM]   [0] Format
L 11/02/2020 - 23:58:07: [SM]   [1] Line 2232, C:\scripting\lilac.sp::lilac_ban_client
L 11/02/2020 - 23:58:07: [SM]   [2] Line 1994, C:\scripting\lilac.sp::lilac_detected_aimbot
L 11/02/2020 - 23:58:07: [SM]   [3] Line 1501, C:\scripting\lilac.sp::timer_check_aimbot
L 11/03/2020 - 00:04:48: Error log file session closed.

[freak.exe_uLow]

Originally Posted by Rav1sh Hello, I've been experiencing these errors the last few days. L 11/02/2020 - 23:47:20: [SM] Exception reported: Translation failed: invalid client index 1601069410 (arg 6) L 11/02/2020 - 23:47:20: [SM] Blaming: lilac.smx L 11/02/2020 - 23:47:20: [SM] Call stack trace: L 11/02/2020 - 23:47:20: [SM] [0] Format L 11/02/2020 - 23:47:20: [SM] [1] Line 2236, C:\scripting\lilac.sp::lilac_ban_client L 11/02/2020 - 23:47:20: [SM] [2] Line 1796, C:\scripting\lilac.sp::lilac_detected_anti_duck_delay L 11/02/2020 - 23:47:20: [SM] [3] Line 1573, C:\scripting\lilac.sp::OnPlayerRunCmd L 11/02/2020 - 23:48:08: [SM] Exception reported: Translation failed: invalid client index 1601069410 (arg 6) L 11/02/2020 - 23:48:08: [SM] Blaming: lilac.smx L 11/02/2020 - 23:48:08: [SM] Call stack trace: L 11/02/2020 - 23:48:08: [SM] [0] Format L 11/02/2020 - 23:48:08: [SM] [1] Line 2230, C:\scripting\lilac.sp::lilac_ban_client L 11/02/2020 - 23:48:08: [SM] [2] Line 1903, C:\scripting\lilac.sp::lilac_detected_bhop L 11/02/2020 - 23:48:08: [SM] [3] Line 1628, C:\scripting\lilac.sp::OnPlayerRunCmd L 11/02/2020 - 23:58:07: [SM] Exception reported: Translation failed: invalid client index 1601069410 (arg 6) L 11/02/2020 - 23:58:07: [SM] Blaming: lilac.smx L 11/02/2020 - 23:58:07: [SM] Call stack trace: L 11/02/2020 - 23:58:07: [SM] [0] Format L 11/02/2020 - 23:58:07: [SM] [1] Line 2232, C:\scripting\lilac.sp::lilac_ban_client L 11/02/2020 - 23:58:07: [SM] [2] Line 1994, C:\scripting\lilac.sp::lilac_detected_aimbot L 11/02/2020 - 23:58:07: [SM] [3] Line 1501, C:\scripting\lilac.sp::timer_check_aimbot L 11/03/2020 - 00:04:48: Error log file session closed.

i think you need to update the translation file (Translation failed)

[JLmelenchon]

Question: Does it ban isntantly on angle cheat detection ? Because I can't remember how many times there were false positives with that on SMAC. That will be better if it bans after x detections in my opinion just for safety.

[J_Tanzanite]

Originally Posted by JLmelenchon Question: Does it ban isntantly on angle cheat detection ? Because I can't remember how many times there were false positives with that on SMAC. That will be better if it bans after x detections in my opinion just for safety.

If I remember correctly, SMAC had issues with that due to the fact that it checked yaw angles.
Lilac doesn't check if yaw angles are "out of bounds", as they get normalized anyway and yaw doesn't work like pitch does.

Lilac bans on the first invalid angle detection, as there is no need to wait until the N'th detection if the check is done properly in the first place.

Lilac has been out for approx 8-9 months now, and the only issue that has been reported for Angle-Cheat detections was for L4D 1&2.. That was fixed a month ago I think, or two months ago.
Since then, there has been no reports of any problems.

[Sreaper]

Is there any way you can make it disallow cl_interp, 5 values past the decimal? I have someone using 0.00000000001 who's constantly accused of cheating with spy. I don't know if that overflows the cl_interp value or not but restricting the decimal places would be a lot more reassuring. Thank you.

[HarryPotter]

Originally Posted by J_Tanzanite If I remember correctly, SMAC had issues with that due to the fact that it checked yaw angles. Lilac doesn't check if yaw angles are "out of bounds", as they get normalized anyway and yaw doesn't work like pitch does. Lilac bans on the first invalid angle detection, as there is no need to wait until the N'th detection if the check is done properly in the first place. Lilac has been out for approx 8-9 months now, and the only issue that has been reported for Angle-Cheat detections was for L4D 1&2.. That was fixed a month ago I think, or two months ago. Since then, there has been no reports of any problems.

I think there are still many false positives with Angle-Cheat detections,
my server just launches within an hour, and too many people angle cheat in l4d2, I doubt they use cheat really.

maybe you can just add an option: log warning "XXX is suspected of using an angle-cheat" instead of instantly ban.

Spoiler

PHP Code:

2020/12/02 20:37:00 [Version 1.6.1] {Name: "tilealyan" | SteamID: STEAM_1:1:208747500 | IP: XXX.XXX.XX.X} was detected and banned for Angle-Cheats (Pitch: 382.38, Yaw: 46.85, Roll: 359.64).
    Pos={-1009,-2341,-1087}, Angles={382.38476,46.85274,359.64843}, Map="c2m1_highway", Team={2}, Weapon="weapon_autoshotgun", Latency={Inc:0.000017,Out:0.064533}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.000000,Out:0.000079}, ConnectionTime={1220.858642 seconds}, GameTime={1189.733398 seconds}

2020/12/02 20:37:16 [Version 1.6.1] {Name: "DolphFury" | SteamID: STEAM_1:1:152049476 | IP: XXX.XXX.XX.X} was detected and banned for Angle-Cheats (Pitch: 373.61, Yaw: 58.34, Roll: 359.64).
    Pos={-1009,-2341,-1087}, Angles={373.61807,58.34549,359.64843}, Map="c2m1_highway", Team={2}, Weapon="weapon_grenade_launcher", Latency={Inc:0.000014,Out:0.067210}, Loss={Inc:0.001440,Out:0.000000}, Choke={Inc:0.000000,Out:0.000000}, ConnectionTime={817.549377 seconds}, GameTime={1205.416748 seconds}

2020/12/02 20:44:36 [Version 1.6.1] {Name: "sehjetkong" | SteamID: STEAM_1:0:520829314 | IP: XXX.XXX.XX.X} was detected and banned for Angle-Cheats (Pitch: 384.09, Yaw: 95.63, Roll: 359.64).
    Pos={-1059,-2309,-1087}, Angles={384.09194,95.63907,359.64843}, Map="c2m1_highway", Team={2}, Weapon="weapon_rifle_m60", Latency={Inc:0.000040,Out:0.233486}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.243447,Out:0.001061}, ConnectionTime={180.501846 seconds}, GameTime={1645.400146 seconds}

2020/12/02 21:12:33 [Version 1.6.1] {Name: "not _ Prince" | SteamID: STEAM_1:1:98399530 | IP: XXX.XXX.XX.X} was detected and banned for Angle-Cheats (Pitch: 387.21, Yaw: 85.68, Roll: 359.64).
    Pos={-1060,-2305,-1087}, Angles={387.21820,85.68089,359.64843}, Map="c2m1_highway", Team={2}, Weapon="weapon_shotgun_spas", Latency={Inc:0.000028,Out:0.131574}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.151384,Out:0.000000}, ConnectionTime={875.834350 seconds}, GameTime={3317.416748 seconds}

2020/12/02 21:14:06 [Version 1.6.1] {Name: "Xar" | SteamID: STEAM_1:0:194070257 | IP: XXX.XXX.XX.X} was detected and banned for Angle-Cheats (Pitch: 381.90, Yaw: 87.11, Roll: 359.64).
    Pos={-1059,-2309,-1087}, Angles={381.90179,87.11352,359.64843}, Map="c2m1_highway", Team={2}, Weapon="weapon_melee", Latency={Inc:0.000033,Out:0.054768}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.105652,Out:0.000000}, ConnectionTime={1019.616455 seconds}, GameTime={3410.050292 seconds} 


[J_Tanzanite]

Originally Posted by HarryPotter I think there are still many false positives with Angle-Cheat detections, my server just launches within an hour, and too many people angle cheat in l4d2, I doubt they use cheat really. maybe you can just an cvar option: log warning "XXX is suspected of using an angle-cheat" instead of instantly ban. Spoiler PHP Code: 2020/12/02 20:37:00 [Version 1.6.1] {Name: "tilealyan" | SteamID: STEAM_1:1:208747500 | IP: 111.184.182.31} was detected and banned for Angle-Cheats (Pitch: 382.38, Yaw: 46.85, Roll: 359.64).     Pos={-1009,-2341,-1087}, Angles={382.38476,46.85274,359.64843}, Map="c2m1_highway", Team={2}, Weapon="weapon_autoshotgun", Latency={Inc:0.000017,Out:0.064533}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.000000,Out:0.000079}, ConnectionTime={1220.858642 seconds}, GameTime={1189.733398 seconds} 2020/12/02 20:37:16 [Version 1.6.1] {Name: "DolphFury" | SteamID: STEAM_1:1:152049476 | IP: 203.185.43.184} was detected and banned for Angle-Cheats (Pitch: 373.61, Yaw: 58.34, Roll: 359.64).     Pos={-1009,-2341,-1087}, Angles={373.61807,58.34549,359.64843}, Map="c2m1_highway", Team={2}, Weapon="weapon_grenade_launcher", Latency={Inc:0.000014,Out:0.067210}, Loss={Inc:0.001440,Out:0.000000}, Choke={Inc:0.000000,Out:0.000000}, ConnectionTime={817.549377 seconds}, GameTime={1205.416748 seconds} 2020/12/02 20:44:36 [Version 1.6.1] {Name: "sehjetkong" | SteamID: STEAM_1:0:520829314 | IP: 14.192.209.131} was detected and banned for Angle-Cheats (Pitch: 384.09, Yaw: 95.63, Roll: 359.64).     Pos={-1059,-2309,-1087}, Angles={384.09194,95.63907,359.64843}, Map="c2m1_highway", Team={2}, Weapon="weapon_rifle_m60", Latency={Inc:0.000040,Out:0.233486}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.243447,Out:0.001061}, ConnectionTime={180.501846 seconds}, GameTime={1645.400146 seconds} 2020/12/02 21:12:33 [Version 1.6.1] {Name: "not _ Prince" | SteamID: STEAM_1:1:98399530 | IP: 183.171.64.152} was detected and banned for Angle-Cheats (Pitch: 387.21, Yaw: 85.68, Roll: 359.64).     Pos={-1060,-2305,-1087}, Angles={387.21820,85.68089,359.64843}, Map="c2m1_highway", Team={2}, Weapon="weapon_shotgun_spas", Latency={Inc:0.000028,Out:0.131574}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.151384,Out:0.000000}, ConnectionTime={875.834350 seconds}, GameTime={3317.416748 seconds} 2020/12/02 21:14:06 [Version 1.6.1] {Name: "Xar" | SteamID: STEAM_1:0:194070257 | IP: 36.231.221.127} was detected and banned for Angle-Cheats (Pitch: 381.90, Yaw: 87.11, Roll: 359.64).     Pos={-1059,-2309,-1087}, Angles={381.90179,87.11352,359.64843}, Map="c2m1_highway", Team={2}, Weapon="weapon_melee", Latency={Inc:0.000033,Out:0.054768}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.105652,Out:0.000000}, ConnectionTime={1019.616455 seconds}, GameTime={3410.050292 seconds}

This is the first report I've gotten about Roll angles being out of bounds.
According to your log, this is all on the map "c2m1_highway", does this happen anywhere else?

[HarryPotter]

Originally Posted by J_Tanzanite This is the first report I've gotten about Roll angles being out of bounds. According to your log, this is all on the map "c2m1_highway", does this happen anywhere else?

it happenes every map, I will investigate

[JLmelenchon]

If you can patch angles so they can't be used to cheat, why it will need to ban anyway ? I disabled the detection of it but it will still be good to have the log.