[J_Tanzanite]

Originally Posted by finishlast I use lilac with lilac_ban "0" and therefor the welcome message isn't working because you check for BAN to be enabled: Welcome setting is 1 and shouldn't be connected to lilac_ban "0" - mb you did it for some reason, but logically I would assume setting welcome to 1 should always work , when lilac_enable "1". I think that would make sense since the "macro detection kick" still works with lilac_ban "0", so the actual message "Protected by Lilac blablabla" is still valid then, even when lilac_ban "0" is set to 0. So as I understood setting it to lilac_ban "0", it still kicks, so maybe instead of setting lilac_ban "0", it would be better to make something like lilac_punishingmethod 1 /// 0 disable log only 1 ban 2 kick lilac_bantime 15 / minutes or 0 perm lilac_kicktime 15 / 1-x minutes For the Welcome Message I just leave the ban out for now. public Action timer_welcome(Handle timer, int userid) { int client = GetClientOfUserId(userid); /* Todo: Considering there are log-only options now... * Perhaps I should check if ANYTHING can ban at all. */ if (is_player_valid(client) && icvar[CVAR_WELCOME] && icvar[CVAR_ENABLE] ) PrintToChat(client, "[Lilac] %T", "welcome_msg", client, PLUGIN_VERSION); }

Yeah the reason behind doing this is that the message is "This server is protected by Little Anti-Cheat", and if banning isn't enabled, well then it isn't protecting against anything.
It would be deceptive to say "This server is protected" when it isn't :')

I haven't gotten around to updating the logic of when the message is displayed or not; but I suppose I should do it in version 1.7.2

And I guess you're right, if macro kicks are enabled, then the message should show. Even tho it isn't a cheat, lilac is protecting against macros / exploits... So sure, I'll fix that :)

[OneMore]

There is an absent entity in translation:
[SM] Exception reported: Language phrase "kick_bad_name" not found (arg 5)
L 08/14/2021 - 20:41:40: [SM] Blaming: lilac.smx
L 08/14/2021 - 20:41:40: [SM] Call stack trace:
L 08/14/2021 - 20:41:40: [SM] [0] KickClient
L 08/14/2021 - 20:41:40: [SM] [1] Line 203, lilac/lilac_string.sp::check_name
L 08/14/2021 - 20:41:40: [SM] [2] Line 125, lilac/lilac_string.sp::event_namechange
L 08/14/2021 - 20:41:40: [SM] [4] SetClientName
L 08/14/2021 - 20:41:40: [SM] [5] Line 40, /home/builds/sourcemod/linux-1.10/build/plugins/playercommands/rename.sp:erformRename
L 08/14/2021 - 20:41:40: [SM] [6] Line 112, /home/builds/sourcemod/linux-1.10/build/plugins/playercommands/rename.sp::MenuHandler_Rename

Would you please check?

[J_Tanzanite]

Originally Posted by OneMore There is an absent entity in translation: [SM] Exception reported: Language phrase "kick_bad_name" not found (arg 5) L 08/14/2021 - 20:41:40: [SM] Blaming: lilac.smx L 08/14/2021 - 20:41:40: [SM] Call stack trace: L 08/14/2021 - 20:41:40: [SM] [0] KickClient L 08/14/2021 - 20:41:40: [SM] [1] Line 203, lilac/lilac_string.sp::check_name L 08/14/2021 - 20:41:40: [SM] [2] Line 125, lilac/lilac_string.sp::event_namechange L 08/14/2021 - 20:41:40: [SM] [4] SetClientName L 08/14/2021 - 20:41:40: [SM] [5] Line 40, /home/builds/sourcemod/linux-1.10/build/plugins/playercommands/rename.sp:erformRename L 08/14/2021 - 20:41:40: [SM] [6] Line 112, /home/builds/sourcemod/linux-1.10/build/plugins/playercommands/rename.sp::MenuHandler_Rename Would you please check?

The "kick_bad_name" is in the translations, did you install the latest translations from version 1.7?
Version 1.6 and version 1.7 have different translations; and you need to place the new translations in the translations folder.

If you did install them, then try "sm_reload_translations" to reload the translations.

[OneMore]

Originally Posted by J_Tanzanite The "kick_bad_name" is in the translations...

Yes, apologies. I checked on github and missed it. I'll update the translations.

[OneMore]

By the way, there are not all phrases in the Russian translation file. Do you need help to update them?

[The Solid lad]

Updated Hungarian translation. (has the new phrases and it's prettier)

[The Solid lad]

Updated my (imo prettier) English translation file.

[The Solid lad]

Btw, I'm really grateful to you J_Tanzanite, for both making and maintaining this plugin!
Next to VAC Status Checker, it is the most useful plugin for keeping cheaters at bay on our CS:GO server.

As a side note... I don't get why do we even need to have a plugin like VSC.
VAC banned players shouldn't be able to join VAC protected servers in the first place... it makes no sense that they can, and we need a 3rd party plugin to autokick/ban them.
Anyways, I'm grateful to StevoTVR as well, for creating that plugin.

[J_Tanzanite]

TheSolidLad, firstly, thanks c:

I've glanced the updated English translations you've provided; some of the changes I like, others not so much.
However, the biggest issue is the periods at the end, as SM automatically adds them, so by including them, we're getting two periods.
I wouldn't mind accepting some of the changes tho, seems nice c:

Anyway, I thought I should put this here, so people are at least aware - for the next week or two, I'll be offline and can't update Lilac - as I'm moving.
I'll be back after that tho, just FYI

[azalty]

Originally Posted by The Solid lad Btw, I'm really grateful to you J_Tanzanite, for both making and maintaining this plugin! Next to VAC Status Checker, it is the most useful plugin for keeping cheaters at bay on our CS:GO server. As a side note... I don't get why do we even need to have a plugin like VSC. VAC banned players shouldn't be able to join VAC protected servers in the first place... it makes no sense that they can, and we need a 3rd party plugin to autokick/ban them. Anyways, I'm grateful to StevoTVR as well, for creating that plugin.

Players VAC banned from CS:GO (or other recent source games) can’t play already if your server is marked as «*secured by VAC*» (which is the case by default). I suspect you prevent people with VAC bans on other games from playing which is often a bad idea since most of them got banned from COD back in the days for stupid DLC unlockers. I personally know a lot of legit people that have already been vac banned from another game.

However, a recent vac ban is a good indicator of potential cheating

Your decisions though!