[RedSword]

1.4.0 is out :

• Added SteamWorks[DL] support. This allows Steam groups usage in the newly SteamWorks-supported mods CSGO & L4D(2) (previously only TF2/CSS/DODS). Need to use 'whitelist_steamgroup 2' for SteamWorks, which is also the new default for whitelist_steamgroup.
• SteamWorks fallback on SteamTools if possible. Note however that it is NOT recommended to run both (even though it works ^^).
• Changed default whitelist.txt so it doesn't have a groupId too big (last one did)
• Fixed reading too-big small SteamGroup id, as they were causing problem (this caused spam to Valve server)
• Slightly optimized/improved reading whitelist.txt (whitespace, logging big int)
• Changed the way Steam groups are added to avoid too big groupId
• Fixed an improbable bug/exploit with autovouchers == 3
  Spoiler

  A previously autovouched client could (with some luck or will) reconnect in the same client slot way past a simple map change, if that client slot had not been use by another client between the moment where the client was autovouched the first time and the moment he rejoined, which would need to be after 65535 user connections
• Slightly optimized autovouchers == 3

Originally Posted by midnight9 Well thats what i thought, and since in l4d2 usualy 8 players connects at the same time from lobby, there is no guarantee that the first players that will connect is the whitelisted one, so it has to be on timer, so all players can connect before it will check. I will have a look, if setting it to 3 wont be any good i may try something else. As for cURL glad to hear that

Would you still want cURL ? I might wait for someone to tell me it doesn't work with SteamWorks :$ /considering-it...

The problem with cURL is : if someone recently a group; you'd need to wait for the server to either automatically reload the list (I would probably do it on map change; or an admin would have to do it; which I expect to be annoying).

EDIT : 1.4.0b is out :

Changed sm_whitelist_reload command description to bring awareness to the fact that it can invalidate SteamGroups cache (might be needed if someone is recently added). Cache is automatically invalidated when map changes. (10-03-2015)

[midnight9]

Originally Posted by RedSword 1.4.0 is out : Added SteamWorks[DL] support. This allows Steam groups usage in the newly SteamWorks-supported mods CSGO & L4D(2) (previously only TF2/CSS/DODS). Need to use 'whitelist_steamgroup 2' for SteamWorks, which is also the new default for whitelist_steamgroup. SteamWorks fallback on SteamTools if possible. Note however that it is NOT recommended to run both (even though it works ^^). Changed default whitelist.txt so it doesn't have a groupId too big (last one did) Fixed reading too-big small SteamGroup id, as they were causing problem (this caused spam to Valve server) Slightly optimized/improved reading whitelist.txt (whitespace, logging big int) Changed the way Steam groups are added to avoid too big groupId Fixed an improbable bug/exploit with autovouchers == 3 Spoiler A previously autovouched client could (with some luck or will) reconnect in the same client slot way past a simple map change, if that client slot had not been use by another client between the moment where the client was autovouched the first time and the moment he rejoined, which would need to be after 65535 user connections Slightly optimized autovouchers == 3 Would you still want cURL ? I might wait for someone to tell me it doesn't work with SteamWorks :$ /considering-it... The problem with cURL is : if someone recently a group; you'd need to wait for the server to either automatically reload the list (I would probably do it on map change; or an admin would have to do it; which I expect to be annoying). EDIT : 1.4.0b is out : Changed sm_whitelist_reload command description to bring awareness to the fact that it can invalidate SteamGroups cache (might be needed if someone is recently added). Cache is automatically invalidated when map changes. (10-03-2015)

Well since the steamworks supports L4D2, then there is really no need for cURL Thanks for asking and thanks for all your work

[RedSword]

Originally Posted by midnight9 Well since the steamworks supports L4D2, then there is really no need for cURL Thanks for asking and thanks for all your work

You're welcomed. Thanks for your feedback.

[RedSword]

1.4.1 is out :

Fixed an improbable bug with hibernation where a reconnecting client (after waking up the server) would trigger KillTimer on an invalid timer at L255. Discovered in NMRIH (Steam Groups do NOT work in NMRIH), but I expect the problem to be possible in CSGO.

Also adding cURL to my todo list as NMRIH do not support SteamWorks correctly .

[RedSword]

Actually NMRiH works correctly with SteamTools (but not SteamWorks), so I don't think I'll add the cURL feature (unless someone reports that it starts failing).

[medic917]

------------------nvm it was because i put the config file in the config folder instead of the whitelist folder.
I tried reloading whitelist and it was showing 1 steamgroup added.
I used the steamgroup ID which was 7 digits, and it did not work even though I was in the steamgroup. I tried restarting and reloading whitelist.

I use sourcemod 1.7.1, perhaps that is why?

Any idea why it won't work? Any way to whitelist people with certain flags?

[riten]

I've installed plugin on my CS:GO server and it doesn't works for some reason. I've placee .smx in the plugin folder and I've also deleted all SteamID's from whitelist and it still doesn't kicks when I join server to test it out. CVAR's looks good and should be working, what should I do? I haven't installed SteamWorks/SteamTools, because I need only to restrict STEAM id's for my server.

All I want is to get list of steam id's that will be able to join server, everyone else should be kicked (it's for tuournament).

Any help?Any ideas?

[RedSword]

Is the plugin considered active ? (when typing "sm plugins list")

Also I hope you didn't install the "sampleDenyKick.sp" ? This would deny kicking a client.

Are you an admin ? You might be allowed in because you're an admin (whitelist_immunity).

Do you get an error in console ?

Red

[riten]

Is the plugin considered active ? (when typing "sm plugins list") - Yes

Also I hope you didn't install the "sampleDenyKick.sp" ? This would deny kicking a client. - Yes (uninstalling, I'll see if it works without it)

Are you an admin ? You might be allowed in because you're an admin (whitelist_immunity). No, I haven't add any Admins and I was not connected with rcon rights as well

Do you get an error in console ? - No

EDIT:

It was sampleDenyKick fault, works fine. Sorry for bothering you

[RedSword]

I guess I'll rename that file name then (to make it clearer).