[8guawong]

Originally Posted by J_Tanzanite Yes. Anti-Duck-Delay (more commonly known as FastDuck) is an exploit cheats in CS:GO have that allows you to spam your duck key without being slowed down. Normally in CS:GO, you have some sort of "stamina" for ducking, and the more you duck, the slower it gets. However, cheats can bypass this restriction by sending a key input to the server (that for some reason bypasses it). I've tested this out, and this key cannot be sent by normal players without cheats (If anyone can disprove this, tell me... And VALVe). Which... Makes sense. VALVe did put in an anti-duck-spam mechanism, and having a key input that would effectively disable that wouldn't make any sense. So yeah, the bans are legit.

ok thx

[NeQ]

Hi, the 1.6.0 version of LilAC is beta or not? And so, could something be untested? I don't want to have many not accurate bans on my server. When will 1.6.0 be released on this forum?

[J_Tanzanite]

Originally Posted by NeQ Hi, the 1.6.0 version of LilAC is beta or not? And so, could something be untested? I don't want to have many not accurate bans on my server. When will 1.6.0 be released on this forum?

I was actually planing on releasing version 1.6.0 on this forum today.
When I released version 1.6.0 on my github's master branch, I decided to wait a week before releasing it here.
This is just so I can get general feedback before it's published here, in case something comes up.

So far, there have been no issues reported.

Basically, to summarize how I do releases:
Github Development Branch: Latest changes, features and detection methods. These may not be stable.
Github Master Branch: Stable release.
This forum: Stable release that I am confident on.

[freak.exe_uLow]

Originally Posted by J_Tanzanite I was actually planing on releasing version 1.6.0 on this forum today. When I released version 1.6.0 on my github's master branch, I decided to wait a week before releasing it here. This is just so I can get general feedback before it's published here, in case something comes up. So far, there have been no issues reported. Basically, to summarize how I do releases: Github Development Branch: Latest changes, features and detection methods. These may not be stable. Github Master Branch: Stable release. This forum: Stable release that I am confident on.

I have been able to test it since the dev version and hadn't noticed an error in the 1.6.0 and I'm curious to see how you manage to do that with the Anti Wallhack module ^^

[finishlast]

L4D1:

I updated lilac to dev from GitHub and it insantly gave me this:

2020/07/29 09:52:19 [Version 1.6.0] {Name: " | SteamID: | } was detected and banned for Angle-Cheats (Pitch: 0.22, Yaw: 30.89, Roll: 0.00).
Pos={6801,-642,768}, Angles={0.22457,30.89904,0.00000}, Map="l4d_vs_airport01_greenhouse", Team={3}, Weapon="weapon_smoker_claw", Latency={Inc:0.000099,Out:0.023478}, Loss={Inc:0.004149,Out:0.000000}, Choke={Inc:0.032678,Out:0.139328}, ConnectionTime={9.388998 seconds}, GameTime={10.389999 seconds}

1.5.0 did not do the ban.

[J_Tanzanite]

Originally Posted by finishlast L4D1: I updated lilac to dev from GitHub and it insantly gave me this: 2020/07/29 09:52:19 [Version 1.6.0] {Name: " | SteamID: | } was detected and banned for Angle-Cheats (Pitch: 0.22, Yaw: 30.89, Roll: 0.00). Pos={6801,-642,768}, Angles={0.22457,30.89904,0.00000}, Map="l4d_vs_airport01_greenhouse", Team={3}, Weapon="weapon_smoker_claw", Latency={Inc:0.000099,Out:0.023478}, Loss={Inc:0.004149,Out:0.000000}, Choke={Inc:0.032678,Out:0.139328}, ConnectionTime={9.388998 seconds}, GameTime={10.389999 seconds} 1.5.0 did not do the ban.

Definitely a false ban.

At first, I didn't understand why angle-cheat was triggered, as the angles shown are normal. Especially since pitch detection was removed from L4D.

...

And then it hit me, I had optimized Angle checks recently, and completely forgot to account for L4D&L4D2 non-pitch checks!

Set "lilac_angles" to "0", for now, as in L4D & L4D2 just about everyone will get banned.

I'll fix it right now and release the patch here.
Should only take 5ish minutes.

[Alex101192]

Originally Posted by J_Tanzanite Definitely a false ban. At first, I didn't understand why angle-cheat was triggered, as the angles shown are normal. Especially since pitch detection was removed from L4D. ... And then it hit me, I had optimized Angle checks recently, and completely forgot to account for L4D&L4D2 non-pitch checks! Set "lilac_angles" to "0", for now, as in L4D & L4D2 just about everyone will get banned. I'll fix it right now and release the patch here. Should only take 5ish minutes.

Yeah I had to report this issue some days ago but forgot. Thank you for working on the patch.

[J_Tanzanite]

Version 1.6.1 is done and uploaded to Github, this should fix that bug.
Going to upload version 1.6.1 here too now.

Edit:
The patch is now on this forum as well.
Hopefully this should fix that bug... What an oversight that was :'D

[finishlast]

1.6.1 fixed it for me again.

Good Job. Thx

[BReeZ]

Originally Posted by J_Tanzanite Yes. Anti-Duck-Delay (more commonly known as FastDuck) is an exploit cheats in CS:GO have that allows you to spam your duck key without being slowed down. Normally in CS:GO, you have some sort of "stamina" for ducking, and the more you duck, the slower it gets. However, cheats can bypass this restriction by sending a key input to the server (that for some reason bypasses it). I've tested this out, and this key cannot be sent by normal players without cheats (If anyone can disprove this, tell me... And VALVe). Which... Makes sense. VALVe did put in an anti-duck-spam mechanism, and having a key input that would effectively disable that wouldn't make any sense. So yeah, the bans are legit.

I run a plugin that disables the stamina/restriction of ducks, so you can duck spam with mouswheel as example.

Would the plugin go nuts because of this?