[pedrotski]

Originally Posted by J_Tanzanite I took a quick overview of the plugin, but couldn't find anything super obvious that would cause the issue. When you do the testing btw, try to also use this plugin: https://forums.alliedmods.net/showthread.php?t=325115 It'll help, as you can then share the demo if you manage to trigger something.

I was able to trigger false detections. Needed multiple people on the server. 1v1 wont give false detections. Had 1 team stay AFK in warmup, de_mirage. You can get a false detection within 1 min. You can test it out.

If a cvar could be added to disable in warmup that would be a quick fix.

[J_Tanzanite]

Originally Posted by pedrotski I was able to trigger false detections. Needed multiple people on the server. 1v1 wont give false detections. Had 1 team stay AFK in warmup, de_mirage. You can get a false detection within 1 min. You can test it out. If a cvar could be added to disable in warmup that would be a quick fix.

I wasn't able to trigger it, could you elaborate further on the steps you took?
Also, could you share your splewis pug configs?

As for adding a ConVar to disable in warmup, that would be a quick fix indeed, but I rather actually fix the underlying problem.

Also, I tried to check if the PUG plugin blocks the event for "player_spawn", for you see, Lilac checks for that event to detect when players spawn and respawn, so that it won't test aimlock.
However, PUG doesn't seem to block the event, so that's not where the issue lies.

The PUG plugin also seems to call `CS_RespawnPlayer()`, but after testing, that function does cause the event to fire, so that isn't the issue either...

This is strange... :/

[8guawong]

Originally Posted by J_Tanzanite Hmm... I'm not sure what can be done about it, there isn't anything in Lilac that would mess with demos afaik. This more or less just reminds me of how unstable demos tend to be, at least in my TF2 experience. I know we're talking about CS:GO here, but it does remind me of it quite a lot (plus same engine). I do wonder tho, is this every demo now? Like, all the recent demos or is it just those you shared?

finally took some time to try to debug this
demo still lags if i disable pretty much all unessential plugins
this could be a CSGO bug
here is some more info about it... http://csgo-servers.1073505.n5.nabbl...w-td12283.html
i'm kinda surprised not many reports here

[peterkernel]

Hey, compiled the plugin on my machine and also downloaded the plugin from github yet it doesn't seem to work with sourcebans? It always ends up banning with basebans.

Am I missing something or is there an issue with the plugin? Thx.

[J_Tanzanite]

Originally Posted by peterkernel Hey, compiled the plugin on my machine and also downloaded the plugin from github yet it doesn't seem to work with sourcebans? It always ends up banning with basebans. Am I missing something or is there an issue with the plugin? Thx.

Lilac doesn't support sourcebans, only sourcebans++.
But I assume you mean sourcebans++ when you write sourcebans?

Anyway, you need to install the sourcebans++ include file when you compile to get SB++ to work.

[finishlast]

When the server gets a ddos lilac tends to kick all players with this message:

PlayerXY reason: has left the game, [[Lilac] Error: Query response failure, please restart your game if this issue persists]

Any idea how to prevent that?

[J_Tanzanite]

Originally Posted by finishlast When the server gets a ddos lilac tends to kick all players with this message: PlayerXY reason: has left the game, [[Lilac] Error: Query response failure, please restart your game if this issue persists] Any idea how to prevent that?

You can disable ConVar checking, that will prevent it.
But that also means Lilac won't check players if they are exploiting ConVars.

You can do so by setting:

PHP Code:

lilac_convar 0 


Honestly, although some cheaters do get caught by the ConVar checker, it's not really that useful.
Most cheats nowadays just spoof the query reply, thus bypassing it.
There are bad cheats out there that don't, but those kinds of cheats tend to get banned for aimbot or Bhop anyway.

ConVar checking is only really useful for detecting bad-cheats and exploiters.

The reason for the kick is simple, if a player doesn't respond to a query, then we can't "trust them".
Although spoofing is a thing, having such a kick system means that bad cheats can't just bypass it by not replying to the query.
But information on how to spoof query responses is sooo readily available nowadays, that it's really just there to check for exploiters.

You can turn it off and not really worry too much about it.

[finishlast]

That did the trick, thx man.

[PootisGod]

I'm having some problems of the plugin detecting my sourcebans++
I have tried both v1.6.3 and v1.x (DEV) of sourcebans++ but it still doesn't seem to detect it.
Is there something that I need to enter so that it detects sourcebans++? (In the config itself the detection is set to 1). If you wish add me on discord or on steam for faster discussion. (PootisGodAnimations#8253)

[J_Tanzanite]

Originally Posted by PootisGod I'm having some problems of the plugin detecting my sourcebans++ I have tried both v1.6.3 and v1.x (DEV) of sourcebans++ but it still doesn't seem to detect it. Is there something that I need to enter so that it detects sourcebans++? (In the config itself the detection is set to 1). If you wish add me on discord or on steam for faster discussion. (PootisGodAnimations#8253)

Sorry for the late response.
If you compiled it yourself, then you have to install the sourcebanspp.inc before compiling.

If you didn't compile it yourself, then there is a command you can use to diagnose where the problem is:

lilac_ban_status

Type that into the server console, and it will give you some output, you can share that here.