I guess we can just continue the discussion here:
I'm guessing turning off the server from the master list would be good, but what about the players that bookmark servers. They won't be able to see it on the master list not knowing there is a tournament.
How about password protected servers. As 2020 said, it might attract players.
Or, just changing the port to a different # so the bookmarks won't work, but custom connect will.
Post your comments below.
Ladle 12 - Private?
Moderator: Light
I guess the ip/password would have to be handed out somehow, email or a forum pm. Either could also just be distibuted by each teams captain though.
If it was individual then every player would have to be 'signed up' therefore eliminating confusion about player numbers (an issue that i think was raised on the ladle 11 feedback page).
However this in turn may hinder the tournament as extra players may not be able to connect, for example 2020 & wrtl helping us out last ladle.
Maybe the best option would be to have a system like the TST. This might kill the wiki element though.
Even so i think every player has the brains to use custom conect or use the password; maybe this will test 2020's concept on a self organised tournament
If it was individual then every player would have to be 'signed up' therefore eliminating confusion about player numbers (an issue that i think was raised on the ladle 11 feedback page).
However this in turn may hinder the tournament as extra players may not be able to connect, for example 2020 & wrtl helping us out last ladle.
Maybe the best option would be to have a system like the TST. This might kill the wiki element though.
Even so i think every player has the brains to use custom conect or use the password; maybe this will test 2020's concept on a self organised tournament
- wrtlprnft
- Reverse Outside Corner Grinder
- Posts: 1679
- Joined: Wed Jan 04, 2006 4:42 am
- Location: 0x08048000
- Contact:
We can already prevent players to switch teams/prevent new players to join a team no matter what by a simple setting. At least all servers built from a recent SVN checkout can.
If you start to complain about lag now, noone has ever proven that spectators significantly increase it.
If you start to talk about the fact that spectators can chat and disturb you I suggest you enable the SILENCE_ALL setting as soon as the match starts. It won't silence people already on the server, but it will silence any player who joins the game after you set it. You'll still see the join and leave messages, but there's more redundand talk by actual players than join/leave messages, so I doubt it would matter a lot.
You won't ever attract new players to the ladle if you stop them from watching or even knowing that there is a match.
z-man: why doesn't the SILENCE_ALL setting on the server act like it does on the client?
If you start to complain about lag now, noone has ever proven that spectators significantly increase it.
If you start to talk about the fact that spectators can chat and disturb you I suggest you enable the SILENCE_ALL setting as soon as the match starts. It won't silence people already on the server, but it will silence any player who joins the game after you set it. You'll still see the join and leave messages, but there's more redundand talk by actual players than join/leave messages, so I doubt it would matter a lot.
You won't ever attract new players to the ladle if you stop them from watching or even knowing that there is a match.
z-man: why doesn't the SILENCE_ALL setting on the server act like it does on the client?
There's no place like ::1
Most spectators who joined this time were in fact other ladle players, they'd be informed about the secret servers anyway and won't be kept out. I'm with wrtl, it doesn't make too much sense to keep the servers locked or secret.
Because I'm inconsistent and lazy. Really, the effect SILENCE_ALL currently has on the client should come from a setting called SILENCE_ALL_NEW, and both effects should be available on server and client.wrtlprnft wrote:why doesn't the SILENCE_ALL setting on the server act like it does on the client?
- 2020
- Outside Corner Grinder
- Posts: 1322
- Joined: Thu Dec 29, 2005 9:21 pm
- Location: the present, finally
captains should be turning up at ircHoAX wrote:I guess the ip/password would have to be handed out somehow, email or a forum pm. Either could also just be distibuted by each teams captain though.
where they could get the passwords...
this also might encourage players to turn up to an irc chatroom
though the captain may use whatever system they want to in distributinng the info...
i don't think we can draw a hard line with player-named entriesHoAX wrote: If it was individual then every player would have to be 'signed up' therefore eliminating confusion about player numbers (an issue that i think was raised on the ladle 11 feedback page).
However this in turn may hinder the tournament as extra players may not be able to connect, for example 2020 & wrtl helping us out last ladle.
if we had
the ladle series would have come to an end by number 3 or 4 if i remember...
maybe one day we are popular enough to enforce this kind of thing
imho it can work with pairs but no larger...
i like the tst system with private emails going to players...HoAX wrote: Maybe the best option would be to have a system like the TST. This might kill the wiki element though.
though i think this could be used by teamcaptains...
cheeky )HoAX wrote: Even so i think every player has the brains to use custom conect or use the password; maybe this will test 2020's concept on a self organised tournament
one thing is to get your ass at a server on time with your teammates
another is fiddling around with technical stuff...
i mean...
i only was able to use irc because of joda's interface
otherwise it was impenetrable
(to my little mind)
hold the line
- 2020
- Outside Corner Grinder
- Posts: 1322
- Joined: Thu Dec 29, 2005 9:21 pm
- Location: the present, finally
wrtlprnft wrote: You won't ever attract new players to the ladle if you stop them from watching or even knowing that there is a match.
secret servers will not only make games invisiblez-man wrote:Most spectators who joined this time were in fact other ladle players, they'd be informed about the secret servers anyway and won't be kept out. I'm with wrtl, it doesn't make too much sense to keep the servers locked or secret.
it makes the entire competition invisible...
players unaware of fortress tournaments will be none the wiser
hence
password protected servers will show on the master list
and new players will want to know what is going on...
and i suspect some will visit the wiki to find out if there is a link
regarding live spectating of games...
at this stage
my guess is that a game report video might be best...
until we can get some kind of server-mirror thing
so
if we can not get passwords written in to server code
then let's do the secret thing
though i hope to god it is easy...
perhaps we can consider passwords and spectator solutions for the next run...?
hold the line
- wrtlprnft
- Reverse Outside Corner Grinder
- Posts: 1679
- Joined: Wed Jan 04, 2006 4:42 am
- Location: 0x08048000
- Contact:
Given that we can't change the meaning of the clientside SILENCE_ALL and we want to keep it consistent, I'd suggest we make the serverside SILENCE_ALL act like the current clientside setting.z-man wrote:Because I'm inconsistent and lazy. Really, the effect SILENCE_ALL currently has on the client should come from a setting called SILENCE_ALL_NEW, and both effects should be available on server and client.wrtlprnft wrote:why doesn't the SILENCE_ALL setting on the server act like it does on the client?
The setting to really silence everyone (current serverside SILENCE_ALL behavior) could be called ENABLE_CHAT (inverted, of course) and work the same way on the server and client.
Also, while we're at it, what about a serverside WEAK_SILENCING? If enabled, silenced people could still send messages, but only other silenced players and logged in people would be able to read them. This would be useful for spectator to spectator chat and asking the admin to unsilence you.
By the way, I doubt a password-protected server would have any more attractive effect than an invisible one.
There's no place like ::1