It would be really nice if we could get the opposite of this feature. I'd like to see cvars where you cannot join a server unless you belong to a specific group.
On Fri, Mar 16, 2012 at 3:46 PM, hlds <[email protected]> wrote: > This is useless for TF2 servers. No sane server admin will enable the > auto-kicking mechanism for his server.**** > > ** ** > > The problem is that we cannot ban the griefers or cheaters. It takes less > than 3 minutes to create a new Steam account, to restart the network > connection (to get a new IP) and to reconnect to server. We need access to > some hardware fingerprint, but something more serious than the SHA1 digest > for MachineGuid registry key or for MAC, because these can be changed > easily.**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Rich Kaethler > *Sent:* Friday, March 16, 2012 10:43 PM > *To:* '[email protected]' > *Subject:* Re: [hlds] New feature in TF2 Beta dedicated server update**** > > ** ** > > I think there is some confusion about how this works.**** > > ** ** > > First off, there is no “kicking power”. The check is only made on initial > connection to the server. Once on the server it does not give anyone power > to kick anyone else.**** > > If while on the server, you discover people you never wish to play with > again: you block them, then you are free to leave the server right then or > endure them until you leave and find another server that does not contain > people you have blocked.**** > > ** ** > > If the server sets sv_steamblockingcheck = 2 then only members of the clan > that “owns” the server may prevent people from playing on that server.**** > > Yes this is currently limited to checking the block lists of clan members > who are on that server, we will look at improving that in the future.**** > > Clearly it is best to use this feature with a non-public group, using it > with a public group would be silly.**** > > This can be improved by ignoring a blocking relationship between two > members of the group.**** > > ** ** > > If the server sets sv_steamblockingcheck = 4 then that stops a new player > from joining a server if one of the people already on that server is > blocked by the new player.**** > > The players already on that server will be totally unaffected. This is to > prevent a new player from ever being matchmade onto a server with people > they have blocked – in case of a race condition in the matchmaking.**** > > ** ** > > Lastly, this is primarily intended to be used on servers that have minimal > administration / running no admin mods. Servers that are heavily > administered already may not need to use this system at all.**** > > The sv_steamblockingcheck = 1 functionality is provided so that it can be > used in conjunction with existing mods for servers that want to allow the > general population to coexist with the servers preferred clients. If your > server has some list of preferred clients, you can make them immune from > blocking and still allow the general population to block each other – and > allow your preferred clients to block who they like.**** > > ** ** > > Please feel free to continue sending constructive feedback.**** > > ** ** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Rich Kaethler > *Sent:* Thursday, March 15, 2012 5:19 PM > *To:* '[email protected]' > *Subject:* [hlds] New feature in TF2 Beta dedicated server update**** > > ** ** > > We have added support for Steam community blocking in the dedicated > server. This functionality is in testing and is controlled by convar ( off > by default ). If the convar is enabled, every new player at connect time ( > once authenticated ) will be tested against the block list of every player > already authenticated on the server. If any of the players on the server > have blocked this player, the dedicated server is notified, and that new > player may be kicked from the server depending on the convar settings.**** > > It is assumed that the most popular setting will take advantage of steam > groups. To do this, use the new “sv_steamgroup” convar to set the group > that your server belongs to, and set “sv_steamblockingcheck” to 2. With > this setting only members of the group that “owns” the server may deny > other players access to the server. If a group has been selected and > “sv_steamblockingcheck” is set to 1, the console text will distinguish a > new player that is blocked by a clan member vs a non-clan member.**** > > ** ** > > Here are the details of the options:**** > > ** ** > > sv_steamblockingcheck**** > > 1 = print results to console only**** > > 2 = kick the new player from the server if anyone already on the server > who is a member of the associated clan has blocked the new player**** > > 3 = kick the new player from the server if anyone already on the server > has blocked the new player**** > > 4 = kick the new player from the server if anyone already on the server > has blocked the new player or the new player has blocked any existing > player on the server**** > > ** ** > > sv_steamgroup**** > > Set this convar to the group ID of the group that this server belongs to. > You can find your group’s ID on the admin profile page in the steam > community.**** > > ** ** > > Please send feedback about blocking in dedicated servers directly to me.** > ** > > ** ** > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > >
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
