[loio]

D:\compile 1.11 6453(2)\lilac.sp(47) : fatal error 183: cannot read from file: "lilac/lilac_globals.sp"

[J_Tanzanite]

Originally Posted by loio D:\compile 1.11 6453(2)\lilac.sp(47) : fatal error 183: cannot read from file: "lilac/lilac_globals.sp"

You need to include the "lilac" folder into the "scripting" folder.
The folder structure should look something like this:

sourcemod/scripting/lilac.sp
sourcemod/scripting/lilac/lilac_aimbot.sp
sourcemod/scripting/lilac/lilac_aimlock.sp
sourcemod/scripting/lilac/lilac_angles.sp
...

[J_Tanzanite]

Originally Posted by Ryan2 @J_Tanzanite do you recommend running SMAC along with LAC as it may catch more cheaters or is running just LAC allow enough?

SMAC is bypassed by a LOT of cheats, due to how old and unchanged it is.
However, it's still useful in some areas.

Both Lilac and SMAC queries players for ConVars, and bans players if they have invalid ones. However, SMAC's ConVar checker is far more in-depth and better, and I recommend using SMAC's ConVar checker over Lilac's.
I may change Lilac's ConVar checker in the future to be better, but as of right now, SMAC does a better job in this regard. You can disable Lilac's ConVar checker by setting lilac_convar to 0.

If you're running TF2 or CS:GO, then you shouldn't run the smac_eyetest module, as it has issues with those games nowadays (at least as far as I have seen and been told).
The smac_eyetest module also conflicts with Lilac's Backtrack patch, which I highly recommend you use, as the patch prevents subtle cheaters from being too subtle and helps deal with some rage hackers too. But if you are going to run the smac_eyetest module, then keep the backtracking patch disabled (it is disabled by default).

As for aimbots, SMAC's method is super easily bypassed and only catches the absolute most obvious aimbotters (*). Lilac's method is far better and catches more things.
SMAC will ban on the 4th detection tho, and Lilac will only do so on the 5th, and Lilac's aimbot tester is delayed by a second (for technical reasons I won't get into, but it's intentional and required).

SMAC also as a wallhack module, which blocks some wallhacks from working. It's not perfect, and has some flaws, but if that's something you're interested in, then you can use it (Warning tho, some people have said it is expensive on the CPU).

Lastly, while speedhacks were patched in most Source games, they weren't in L4D1/2 (I haven't checked if this is still the case), so the speedhack module might be somewhat helpful for those games? Not sure.

[Fastkill91]

Hello J_Tanzanite , after the last update in csgo, it became a ban for vip bhop from riko, the inclusion is registered in the source code, but it stopped helping!

[J_Tanzanite]

Originally Posted by Fastkill91 Hello J_Tanzanite , after the last update in csgo, it became a ban for vip bhop from riko, the inclusion is registered in the source code, but it stopped helping!

I am assuming the inclusion is registered in the riko-bhop plugin, and not in Lilac (As that is the correct way to do it). But was the update for the game itself or Sourcemod?

[Fastkill91]

Originally Posted by J_Tanzanite I am assuming the inclusion is registered in the riko-bhop plugin, and not in Lilac (As that is the correct way to do it). But was the update for the game itself or Sourcemod?

the update was in csgo and sm itself

[Ryan2]

Can something like this be integrated?

https://github.com/Silenci0/SMAC/blo...ac_wallhack.sp

[USER555]

Just use https://github.com/sapphonie/StAC-tf2

[CryWolf]

Why does he gave that?

//SourceMod Batch Compiler
// by the SourceMod Dev Team


//// lilac.sp
//
// lilac/lilac_convar.sp(19) : warning 224: user warning: Messy code! Considering re-writing this entire system.
//
// lilac/lilac_ping.sp(19) : warning 224: user warning: Messy code!
//
// Code size:            86260 bytes
// Data size:           756192 bytes
// Stack/heap size:      16384 bytes
// Total requirements:  858836 bytes
//
// 2 Warnings.
//
// Compilation Time: 0.23 sec
// ----------------------------------------

Press enter to exit ...

??? ver 1.7.1 but compiles

[J_Tanzanite]

Originally Posted by CryWolf Why does he gave that? //SourceMod Batch Compiler // by the SourceMod Dev Team //// lilac.sp // // lilac/lilac_convar.sp(19) : warning 224: user warning: Messy code! Considering re-writing this entire system. // // lilac/lilac_ping.sp(19) : warning 224: user warning: Messy code! // // Code size: 86260 bytes // Data size: 756192 bytes // Stack/heap size: 16384 bytes // Total requirements: 858836 bytes // // 2 Warnings. // // Compilation Time: 0.23 sec // ---------------------------------------- Press enter to exit ... ??? ver 1.7.1 but compiles

These are just warnings to remind myself to update some messy code.
They're non-critical warnings, not errors, you can ignore them.