[borzaka]

Originally Posted by Ejziponken I still want the detection in the log tho.

I think you can have that:

lilac_log "1"		// Enable cheat logging.
lilac_log_extra "2"	// 2 = Log extra information on everything.
lilac_log_misc "1"	// Log when players are kicked for misc features, like interp exploits, too high ping and on convar response failure.

I'am using this way for the moment; no banning, just logging and monitoring everything.

Unfortunately it's missed another aimbotter yesterday from banning automatically:

SMAC:

L 06/10/2020 - 20:11:12: [smac_aimbot.smx | 0.8.7.3] HUH? (ID: STEAM_1:0:xxxxxxxxx | IP: 0.0.0.0) is suspected of using an aimbot. (Detection #2 | Deviation: 173° | Weapon: weapon_deagle)
L 06/10/2020 - 20:11:15: [smac_aimbot.smx | 0.8.7.3] HUH? (ID: STEAM_1:0:xxxxxxxxx | IP: 0.0.0.0) is suspected of using an aimbot. (Detection #3 | Deviation: 175° | Weapon: weapon_deagle)
L 06/10/2020 - 20:11:23: [smac_aimbot.smx | 0.8.7.3] HUH? (ID: STEAM_1:0:xxxxxxxxx | IP: 0.0.0.0) is suspected of using an aimbot. (Detection #4 | Deviation: 176° | Weapon: weapon_deagle)
L 06/10/2020 - 20:11:27: [smac_aimbot.smx | 0.8.7.3] HUH? (ID: STEAM_1:0:xxxxxxxxx | IP: 0.0.0.0) is suspected of using an aimbot. (Detection #5 | Deviation: 176° | Weapon: weapon_deagle)
L 06/10/2020 - 20:11:46: [smac_aimbot.smx | 0.8.7.3] HUH? (ID: STEAM_1:0:xxxxxxxxx | IP: 0.0.0.0) is suspected of using an aimbot. (Detection #6 | Deviation: 101° | Weapon: weapon_deagle)
L 06/10/2020 - 20:11:46: [smac_aimbot.smx | 0.8.7.3] HUH? (ID: STEAM_1:0:xxxxxxxxx | IP: 0.0.0.0) was banned for using an aimbot.

LILAC:

2020/06/10 20:11:13 [Version 1.5.1] {Name: "HUH?" | SteamID: STEAM_1:0:xxxxxxxxx | IP: 0.0.0.0} is suspected of using an aimbot (Detection: 2 | Delta: 173 | TotalDelta: 561 | Detected: Aim-Snap Aim-Snap2 Total-Delta).
        Pos={-716,-2105,-179}, Angles={87.73000,-117.30918,0.00000}, Map="de_mirage", Team={2}, Weapon="weapon_deagle", Latency={Inc:0.001196,Out:0.181668}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.094848,Out:0.000000}, ConnectionTime={273.543640 seconds}, GameTime={133.093750 seconds}
2020/06/10 20:11:16 [Version 1.5.1] {Name: "HUH?" | SteamID: STEAM_1:0:xxxxxxxxx | IP: 0.0.0.0} is suspected of using an aimbot (Detection: 3 | Delta: 175 | TotalDelta: 193 | Detected: Aim-Snap Aim-Snap2 Autoshoot Angle-Repeat).
        Pos={-783,-1585,-167}, Angles={87.73000,-25.77954,0.00000}, Map="de_mirage", Team={2}, Weapon="weapon_deagle", Latency={Inc:0.001196,Out:0.181250}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.003417,Out:0.000000}, ConnectionTime={276.645202 seconds}, GameTime={136.195312 seconds}
2020/06/10 20:11:23 [Version 1.5.1] {Name: "HUH?" | SteamID: STEAM_1:0:xxxxxxxxx | IP: 0.0.0.0} is suspected of using an aimbot (Detection: 4 | Delta: 176 | TotalDelta: 178 | Detected: Aim-Snap Aim-Snap2).
        Pos={174,268,-255}, Angles={87.73000,-178.12211,0.00000}, Map="de_mirage", Team={2}, Weapon="weapon_deagle", Latency={Inc:0.001194,Out:0.136344}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.051269,Out:0.000000}, ConnectionTime={284.043640 seconds}, GameTime={143.593750 seconds}
2020/06/10 20:11:28 [Version 1.5.1] {Name: "HUH?" | SteamID: STEAM_1:0:xxxxxxxxx | IP: 0.0.0.0} is suspected of using an aimbot (Detection: 5 | Delta: 176 | TotalDelta: 1365 | Detected: Aim-Snap Aim-Snap2 Autoshoot Angle-Repeat Total-Delta).
        Pos={174,268,-255}, Angles={87.73000,34.47155,0.00000}, Map="de_mirage", Team={2}, Weapon="weapon_deagle", Latency={Inc:0.001196,Out:0.132578}, Loss={Inc:0.000000,Out:0.000000}, Choke={Inc:0.093750,Out:0.000000}, ConnectionTime={288.840515 seconds}, GameTime={148.390625 seconds}

It's looks like 1 second behind the detection from SMAC. I have set LILAC's detection to 6, to match SMAC detection threshold.

And there was some misses today as well. So I'am going to use SMAC and LILAC together for a time being.

[JLmelenchon]

I installed it but didn't activate it for now, it will still write in the logs if it detects something ?
Also is it possible to build an anti-wallhack on this engine ? SMAC anti wallhack was not compatible with Left 4 Dead 2 and CSGO.

[Alex101192]

I have been seeing a lot of bhop bans lately. While some of them are correct as the banned players told me they bhopped, I am not sure about the others.

[J_Tanzanite]

Originally Posted by JLmelenchon I installed it but didn't activate it for now, it will still write in the logs if it detects something ? Also is it possible to build an anti-wallhack on this engine ? SMAC anti wallhack was not compatible with Left 4 Dead 2 and CSGO.

I'm assuming you mean you've set lilac_ban to 0, in which case, yes, it will still log detections.
If you set "lilac_enable" to 0 however, then no.
lilac_enable must be 1 to work.

As for an Anti-Wallhack... Quite a few people have asked me about this, and about two years ago when I originally wrote this Anti-Cheat, I also wrote an Anti-Wallhack.

I've only every used it on TF2.
I'm going to release an Alpha Anti-Wallhack soon on my github page (https://github.com/J-Tanzanite/).

Not sure when I'll get to it.
But it's going to be in Alpha, so don't expect perfection to begin with (Might have some bugs).
Unsure about L4D 1&2 support tho.

[Alex101192]

Originally Posted by J_Tanzanite I'm assuming you mean you've set lilac_ban to 0, in which case, yes, it will still log detections. If you set "lilac_enable" to 0 however, then no. lilac_enable must be 1 to work. As for an Anti-Wallhack... Quite a few people have asked me about this, and about two years ago when I originally wrote this Anti-Cheat, I also wrote an Anti-Wallhack. I've only every used it on TF2. I'm going to release an Alpha Anti-Wallhack soon on my github page (https://github.com/J-Tanzanite/). Not sure when I'll get to it. But it's going to be in Alpha, so don't expect perfection to begin with (Might have some bugs). Unsure about L4D 1&2 support tho.

Be careful with l4d and l4d2. Infected players on versus have wallhack by default. I used kigenac anti cheat before which removed it, and made playing infected just bad.

[borzaka]

I don't think you should use translatable ban reasons. I don't know who wants the ban reason shown on the cheaters language
Kick reason could be on the clients language, but the ban reason shouldn't.

Yesterday an Ukrainian cheater got banned:

[Little Anti-Cheat 1.5.1] Обнаружен Aimbot

This is how it shows in my SourceBans++.

I think it's not a good idea. It should be Aimbot Detected in this case.

SMAC doesn't translate the ban reasons either: https://github.com/Silenci0/SMAC/blo...ac.phrases.txt
It just use it like this, not translatable;

SMAC_Ban(client, "Aimbot Detected");

Only translatable are the kick messages and some other notification to the online admins.

Looking forward to the next release! I hope you can implement some of my feedback!

[Alex101192]

I will be honest, I didn't believe all these bhop bans were legit. But after further investigation, I have come to the sad conclusions that there is really all these people abusing bhop to gain their cheap speedhack. Sure I have had some false positives (reason why I set it to ban for 4 hours only), but at least 95% of these bans are all legit.

Scary to think that exploits are normalized so much to the point where people think I am banning them because of them using bhop scripts instead of the actual actual act of bunny hopping.

[Ejziponken]

Hows it going with the DB logging? I really really want that.

[tornike015]

bhop detector working bad. got banned player only for 10 scroll jump. i turned off bhop detector. fix it dude. cow anticheat is good for bhop detect. and also not showing autoshoot and etc scripts. i think u need update the anti-cheat.

[NeQ]

Hi, I'm using the 1.5.1 version of Lilac and banned players are saved to basebans.cfg instead of sourcebans.

lilac_sourcebans "1"

Checking ban plugins:
Material-Admin:
Loaded: No
ConVar lilac_materialadmin = 1
Sourcebans++:
Loaded: No
ConVar lilac_sourcebans = 1