Well, we've now had an instance of someone impostoring and playing on two different teams. It may be an isolated incident, or the start of a trend. A tournament website has been talked about numerous times and ultimately might be best for Ladle. But maybe it's best to just think in the short term for now. What can we do to deter this type of trouble making?dlh wrote:What level of control is needed for the Ladle?
I propose something that, while not a final solution, isn't too inconvenient for players (and doesn't require any development).
Start by setting ACCESS_LEVEL_PLAY 15. Most of us are used to this by now anyway. Then, ask players to sign up on the wiki using their authentication name. In most cases, this is the same or similar as their player name (example: -=}ID< Robo would register as Robot69). Since players are required to login to play, and their login name may differ from their player name, we can abandon any rule on aliases during Ladle (team binary player can be named t:00000000 if logged in as 1200@forums). Any team that wants to be totally anonymous will just make new forum accounts anyway.
This adds a layer of protection for teams so they don't get duped like uNk did. And, it's a good habit to get into for when we have that awesome tournament website. But I wonder if there is a way to force auth names to be visible? Because if people can play hidden, this idea is useless.
And another deterrent against impostoring might be minimal disciplinary action for violation. If you are discovered playing on two teams, then you get "shunned" and IP banned for the following Ladle. There is no need to go to extremes (yet), but we should send a clear message that this is considered poor sportsmanship.
@Lackadaisical: I'm cool with date voting every quarter. We should find an easy way or a good place to record the dates after the vote (although I predict few few changes from the first Sunday).