[The Solid lad]

Originally Posted by J_Tanzanite There is no spinhack detection in Lilac, and I don't quite see the point of it. While it is possible to detect spinhacks, it's easy for legit players to set it off when messing about. You could add checks to prevent false positives, but cheats then have a very easy time bypassing it. And checking for perfect constant yaw deltas in my testing, false flagged players with controllers. At most, a warning system for spinbot could be used, which I would consider. As for speedhack, it's patched in most source games, with the exception of L4D1&2 I believe.

A warning, publicly printed to chat would be great.
I hate people who use rapid spinning binds... most of the times these are obnoxious trolls who try to mock other players by doing "le spin" after every kill they get.

[larrybrains]

Is the 1.7.4 development version stable? Is it worth updating from 1.7.1 for my L4D2 server or should I wait for the next official release?

[J_Tanzanite]

Originally Posted by CryWolf ... i've downloaded the archives ...

I wasn't sure what you meant by this, the archive branches are not to be downloaded from, you should use the master and development branch.

However, I think I know what's happening, you're downloading from the "releases" tab, which I forgot to update.

You can download it directly here without having to wait for me to update the release build:
https://imgur.com/a/IS9cPco

[J_Tanzanite]

Originally Posted by larrybrains Is the 1.7.4 development version stable? Is it worth updating from 1.7.1 for my L4D2 server or should I wait for the next official release?

Version 1.7.4 is considered stable, it's not a major release, just bug fixes and general polish. It will be pushed as the main version very soon, I've just been slow to do so as I wanted feedback before doing so. So I would recommend updating.

One thing to note about 1.7.4 is that it won't check for angle cheats in L4D2, this is due to an issue that was reported a while ago, and will be fixed in version 1.8.x (which I plan on being a L4D2 update).

Version 1.7.4 was in development for a long time because things came up in my life and I spent less time on development, that's going to change soon.

[Ronas963]

Hi if I download this Little Anti-Cheat for Team Fortress 2 but It can without sourcebans++?

[maclarens]

J_Tanzaniteб, Will there be a antispeedhack in the plans?

[JLmelenchon]

The number of cheaters right now in L4D2 is ridiculous, i will be honest the anti cheat does nothing anymore it will catch barely 10% of them if i had to guess and this is basically only admin work by watching demos. Good luck for next updates.

[BEFOREOUTHILL]

//// lilac.sp
//
// lilac\lilac_string.sp(115) : warning 242: function "event_namechange" should return an explicit value
// lilac\lilac_string.sp(115) : warning 242: function "event_namechange" should return an explicit value
// lilac\lilac_stock.sp(307) : warning 242: function "timer_kick" should return an explicit value
// lilac\lilac_ping.sp(19) : warning 224: user warning: Messy code!
//
// lilac\lilac_noisemaker.sp(37) : warning 242: function "event_inventoryupdate" should return an explicit value
// lilac\lilac_macro.sp(194) : warning 242: function "timer_decrement_macro" should return an explicit value
// lilac\lilac_convar.sp(19) : warning 224: user warning: Messy code! Considering re-writing this entire system.
//
// lilac\lilac_config.sp(481) : warning 242: function "lilac_date_list" should return an explicit value
// lilac\lilac_bhop.sp(161) : warning 242: function "timer_decrement_bhop" should return an explicit value
// lilac\lilac_bhop.sp(161) : warning 242: function "timer_decrement_bhop" should return an explicit value
// lilac\lilac_aimlock.sp(262) : warning 242: function "timer_decrement_aimlock" should return an explicit value
// lilac\lilac_aimlock.sp(262) : warning 242: function "timer_decrement_aimlock" should return an explicit value
// lilac\lilac_aimbot.sp(143) : warning 242: function "timer_check_aimbot" should return an explicit value
// lilac\lilac_aimbot.sp(143) : warning 242: function "timer_check_aimbot" should return an explicit value
// lilac\lilac_aimbot.sp(371) : warning 242: function "timer_decrement_aimbot" should return an explicit value
// lilac\lilac_aimbot.sp(371) : warning 242: function "timer_decrement_aimbot" should return an explicit value
// C:\Users\Before\Desktop\compilka\addons\sourc emod\scripting\lilac.sp(282) : warning 242: function "event_teleported" should return an explicit value
// C:\Users\Before\Desktop\compilka\addons\sourc emod\scripting\lilac.sp(29 : warning 242: function "timer_welcome" should return an explicit value
// Code size: 112736 bytes
// Data size: 759236 bytes
// Stack/heap size: 49092 bytes
// Total requirements: 921064 bytes
//
// 18 Warnings.



Isn't that critical? It's been on the server for a week and there are no detects.

[maclarens]

Originally Posted by BEFOREOUTHILL //// lilac.sp // // lilac\lilac_string.sp(115) : warning 242: function "event_namechange" should return an explicit value // lilac\lilac_string.sp(115) : warning 242: function "event_namechange" should return an explicit value // lilac\lilac_stock.sp(307) : warning 242: function "timer_kick" should return an explicit value // lilac\lilac_ping.sp(19) : warning 224: user warning: Messy code! // // lilac\lilac_noisemaker.sp(37) : warning 242: function "event_inventoryupdate" should return an explicit value // lilac\lilac_macro.sp(194) : warning 242: function "timer_decrement_macro" should return an explicit value // lilac\lilac_convar.sp(19) : warning 224: user warning: Messy code! Considering re-writing this entire system. // // lilac\lilac_config.sp(481) : warning 242: function "lilac_date_list" should return an explicit value // lilac\lilac_bhop.sp(161) : warning 242: function "timer_decrement_bhop" should return an explicit value // lilac\lilac_bhop.sp(161) : warning 242: function "timer_decrement_bhop" should return an explicit value // lilac\lilac_aimlock.sp(262) : warning 242: function "timer_decrement_aimlock" should return an explicit value // lilac\lilac_aimlock.sp(262) : warning 242: function "timer_decrement_aimlock" should return an explicit value // lilac\lilac_aimbot.sp(143) : warning 242: function "timer_check_aimbot" should return an explicit value // lilac\lilac_aimbot.sp(143) : warning 242: function "timer_check_aimbot" should return an explicit value // lilac\lilac_aimbot.sp(371) : warning 242: function "timer_decrement_aimbot" should return an explicit value // lilac\lilac_aimbot.sp(371) : warning 242: function "timer_decrement_aimbot" should return an explicit value // C:\Users\Before\Desktop\compilka\addons\sourc emod\scripting\lilac.sp(282) : warning 242: function "event_teleported" should return an explicit value // C:\Users\Before\Desktop\compilka\addons\sourc emod\scripting\lilac.sp(29 : warning 242: function "timer_welcome" should return an explicit value // Code size: 112736 bytes // Data size: 759236 bytes // Stack/heap size: 49092 bytes // Total requirements: 921064 bytes // // 18 Warnings. Isn't that critical? It's been on the server for a week and there are no detects.

he fix already in next reliase

[Sajmooooon]

After latest update plugin doesn't work, version 1.7.1

L 02/04/2023 - 151:21: [SM] Blaming: lilac.smx L 02/04/2023 - 151:21: [SM] Call stack trace: L 02/04/2023 - 151:21: [SM] [0] HookEntityOutput L 02/04/2023 - 151:21: [SM] [1] Line 138, lilac.sp::OnPluginStart [SM] Plugin lilac.smx failed to reload: Error detected in plugin startup (see error logs).