[J_Tanzanite]

Originally Posted by BReeZ 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?

Depends, if your plugin does this by inserting IN_BULLRUSH into usercmds, then yes.
But I'm guessing your plugin doesn't go about it this way... Would have to see the source to be sure.

If your plugin doesn't insert that button press, then no, everything should be fine.

Here's the Anti-Duck-Delay/FastDuck detection code of Lilac btw:

if (ggame == GAME_CSGO && icvar[CVAR_ANTI_DUCK_DELAY] && (buttons & IN_BULLRUSH))
	lilac_detected_anti_duck_delay(client);

If your plugin does actually insert IN_BULLRUSH, then you can disable the Anti-Duck-Delay/FastDuck detection in lilac by this convar: "lilac_anti_duck_delay" "0"
Which you can change in the config file, found at: "cfg/sourcemod/lilac_config.cfg"

[enderandrew]

Originally Posted by BReeZ 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?

In your particular case I'd recommend disabling a check if you know it isn't appropriate for your server.

lilac_angles "0"
lilac_angles_patch "0"

Though I suppose you could request a convar to separate duck checks from the rest of angle checks.

[J_Tanzanite]

Originally Posted by enderandrew In your particular case I'd recommend disabling a check if you know it isn't appropriate for your server. lilac_angles "0" lilac_angles_patch "0" Though I suppose you could request a convar to separate duck checks from the rest of angle checks.

Angle checks and Duck checks aren't done through the same ConVar tho, setting lilac_angles and lilac_angles_patch to 0 doesn't disable ADD/FastDuck checks...

You can disable ADD/FastDuck detections through the ConVar lilac_anti_duck_delay

[xSLOW]

Hi, I want to make BHOP detector more safe, can I modify this value from 5 to a bigger number if im using "lilac_bhop 2"?

https://github.com/J-Tanzanite/Littl.../lilac.sp#L411

[J_Tanzanite]

Originally Posted by xSLOW Hi, I want to make BHOP detector more safe, can I modify this value from 5 to a bigger number if im using "lilac_bhop 2"? https://github.com/J-Tanzanite/Littl.../lilac.sp#L411

You could, but you should also then modify this line: https://github.com/J-Tanzanite/Littl...lilac.sp#L1879
Because "lilac_bhop 2" means it will also consider how many ticks you held down your jump key while doing perfect bhops.
There really isn't any point of modifying the bhop max counter if you're using "lilac_bhop 2", though.

If you really wanna stay on the safe side... The best option would be to not ban for Bhop at all...
Bhop detections really just come down to statistics, and there is no 100% safe option.
The default settings are the most optimal.

That said, if you do still wish to ban for Bhop and be safe, use "lilac_bhop 1", setting this to 1 doesn't make any difference for legit players, but it does for cheaters.
Doing this also means fewer cheaters who use bhop will get banned though.

If you are REALLY concerned about these things and wanna be near 99,999999999% sure bans are valid, use "lilac_bhop 1" and modify this line from 10 to 15+: https://github.com/J-Tanzanite/Littl.../lilac.sp#L410
Doing this will cause most cheaters who bhop to not get caught, but it lowers the chance of a false positive drastically... Honestly, no idea why you would do this if it just ends up catching few or no cheaters. But if that's your preference, then this is is the best way to be sure bans are valid.

[xSLOW]

Thanks for your reply!
I want to be sure when someone gets banned for something. Making it to ban only obvious cheaters would be okay for me.

[J_Tanzanite]

Originally Posted by xSLOW Thanks for your reply! I want to be sure when someone gets banned for something. Making it to ban only obvious cheaters would be okay for me.

In that case, you might wanna set "lilac_aimbot_autoshoot" to "0" as well.
Autoshoot is a part of aimbot detections, and it detects when a cheat is shooting for the player.
This isn't visible to spectators or SourceTV demos.
You can get this detection on rage hackers, but you can also get it on legit cheaters (cheaters who try to look legit).
So if you only wanna deal with rage hackers, then disabling autoshoot detections might be ideal for your purpose.

Also, this might be ideal for you if you wanna record aimbotters automatically: https://forums.alliedmods.net/showthread.php?t=325115

[Alex101192]

Some people got banned for 8 hours with this reason " [SourceSleuth] Duplicate account ". I have never seen this before. Is that a false?

[J_Tanzanite]

Originally Posted by Alex101192 Some people got banned for 8 hours with this reason " [SourceSleuth] Duplicate account ". I have never seen this before. Is that a false?

SourceSleuth is a different plugin, and is not a part of Lilac.

[whiteskypony]

Originally Posted by Alex101192 Some people got banned for 8 hours with this reason " [SourceSleuth] Duplicate account ". I have never seen this before. Is that a false?

https://forums.alliedmods.net/showthread.php?p=1818793

SourceSleuth: This plugin allows you to automatic ban players who create new account or simple just join with another account when they are banned. The plugin will search for the ip in sourcebans and if found you can chose between some different options trought the cVars.