[Alex101192]

Originally Posted by whiteskypony https://forums.alliedmods.net/showthread.php?p=1818793

Ah ok. That's very useful, didn't know about this feature. Thank you.

[whiteskypony]

Where does the anti cheat look for invalid convars? Im having problems in one of our servers the AC always bans me for invalid convar (sv_cheats 1),
we have it installed on 3 servers and only one of them does this. The only temp solution was to disable the convar ban check.

Im root admin on those.

I was not sure if i have an .cfg file on my end that may cause this but nothing.

*PD: This happen with version 1.5.1 and now with 1.6.1

[Sreaper]

I'm having the same issue as the above poster. Can you please add code to exclude admins from the checks? Thank you for the plugin.

[J_Tanzanite]

Originally Posted by whiteskypony Where does the anti cheat look for invalid convars?

Queries are sent here: https://github.com/J-Tanzanite/Littl.../lilac.sp#L971
Queries are checked here: https://github.com/J-Tanzanite/Littl...lilac.sp#L1022

Originally Posted by whiteskypony Where does the anti cheat look for invalid convars? Im having problems in one of our servers the AC always bans me for invalid convar (sv_cheats 1), we have it installed on 3 servers and only one of them does this. The only temp solution was to disable the convar ban check. Im root admin on those. I was not sure if i have an .cfg file on my end that may cause this but nothing. *PD: This happen with version 1.5.1 and now with 1.6.1

Originally Posted by Sreaper I'm having the same issue as the above poster. Can you please add code to exclude admins from the checks? Thank you for the plugin.

I'm not sure what the underlying issue is, but it kinda sounds like you two have a plugin or something that gives you sv_cheats 1 access since you are admins... Tho, it's hard to tell.
If you disable Lilac ConVar checks "lilac_convar 0" and go on your servers, and type "sv_cheats" in your game console (Not server console!), if it says it's 1 but others (like non-admins/normal players) have it as 0 - then that would suggest it's you giving yourselves sv_cheats access, probably via another plugin.

As for code to exclude admins from checks, no, there is however already a system in place which you could use to disable certain detections on specific players, and that's the forwards Lilac provides.
Here is some psudocode:

#include <sourcemod>

#define CHEAT_CONVAR 	2 // From the lilac.sp file, this value is set in stone and won't ever be changed.

public Action lilac_allow_cheat_detection(int client, int cheat)
{
	// Only check ConVar detections.
	if (cheat == CHEAT_CONVAR) {

		// This function "is_client_admin()" doesn't exist!
		// Not sure how you check for admins, been told you
		// should use "CheckCommandAccess()"
		if (is_client_admin(client)) {

			// Client is an admin and the cheat detected
			// was a ConVar violation.
			// This tells Lilac to ignore the detection (and not ban).
			return Plugin_Handled;
		}
	}

	// Cheat detected wasn't a ConVar or the client wasn't an admin.
	// Allow the cheat detection to happen.
	return Plugin_Continue;
}

You can make your own plugins with this code or add this directly to Lilac, tho the former is cleaner.

[whiteskypony]

You can make your own plugins with this code or add this directly to Lilac, tho the former is cleaner.

It was as you say early, when i typed sv_cheats it was to "1" on my end, im not sure what plugin does this.

Anyways the code seems to work perfect THANKS alot, i include it in lilac main plugin:

public Action lilac_allow_cheat_detection(int client, int cheat)
{
	if (cheat == CHEAT_CONVAR) {

		if (CheckCommandAccess(client, "CVAR_ENABLE", ADMFLAG_CHEATS)) {
			return Plugin_Handled;
		}
	}
	return Plugin_Continue;
}

[Teamkiller324]

Originally Posted by Sreaper I'm having the same issue as the above poster. Can you please add code to exclude admins from the checks? Thank you for the plugin.

Should be fairly easy to do, just make a bool with admin access and then you make so it checks if the target is an admin or not

[BigHeartEnergy]

Hey, J_Tanzanite. Great mod! I'm glad that someone is picking up Valve's slack.

I don't mean to hijack the discussion, but I'm an anti-cheat developer working to port my state of the art Fog of War (anti-wallhack) system from UE4 to Source. It's much better than VALORANT and CS:GO's current solutions, and it makes it almost impossible to wallhack. I'm talking to some ESL people, and they want a demo in Source. The goal is to get it into SourceMod, then ESL, and then CS:GO. If the press publishes an embarrassing side-by-side demo, Valve will be shamed into implementing it. Alternatively, I'm working with Riot people to implement it in VALORANT, which will also force Valve's hand.

Do you have time to chat? My Discord is Quantum, hashtag six zero eight six.

[Sreaper]

Originally Posted by Teamkiller324 Should be fairly easy to do, just make a bool with admin access and then you make so it checks if the target is an admin or not

I was hoping to take the lazy route rather than code it myself. Thanks to all who responded to me and once again for the plugin!
Also J_Tanzanite you would be correct. I did make a plugin that removes all restrictions from root level admins and automatically sends sv_cheats 1 upon joining.

[Devious_Toast]

Recently encountered this issue with a player using hacks.

SteamID: STEAM_ID_STOP_IGNORING_RETVALS

[J_Tanzanite]

Originally Posted by Devious_Toast Recently encountered this issue with a player using hacks. SteamID: STEAM_ID_STOP_IGNORING_RETVALS

This hacker might be using an exploit that is well known, that lets you bypass bans.
Or it could legitimately just be some problems.

I wrote a plugin a while back that handles this exploit: https://forums.alliedmods.net/showthread.php?t=312051

Basically, it doesn't let players with invalid SteamIDs walk around, shoot etc, or speak in text chat.
Sadly it has some rather sad side-effects, if the steam network is down, then everyone will be locked in place.
Maybe I should update it so it checks if the steam network is available, and if it isn't, disable itself.

Also, the coding style in that plugin... I am so sorry for your eyes and mind ):
I no longer code like that, please forgive my sins.