Difference between revisions of "Ladle/Guidelines"

From Armagetron
m (oops forgot a ])
(me and sinewav's Proposel for guidlines to be changed)
Line 3: Line 3:
 
== Stages ==
 
== Stages ==
  
=== Stage 1 ===
+
===Stage 1 - Preparation===
'''Team-Captains visit the [[Ladle/Challenge Board]] to establish provisional playoffs.'''
+
A Ladle Enthusiast will prepare the wiki for a new event keeping the following in mind: Per tradition, the Ladle will be played on the first Sunday of every month (except for January, which will take place on the Sunday following the first Tuesday of the month). The opening round of play will start at 18:45 GMT for a 16 team bracket, and 18:00 GMT for a 32-team bracket. The start times will change to follow Daylight Savings Time in the EU. Generally, 45 minutes is allowed to complete each round.
  
Again, this is only provisional. Only the Team-Captain is authorised to place your team on the board. S/He may alter this whenever they wish, and this may mean some jostling since placement not only determines who your team goes up against in the first and subsequent rounds, but also which servers you will be playing in. Inform your Team-Captain of your preferences, your favourite servers, and consider ping, stability, and general conditions. '''The cut off for the provisional placement of teams is 00.00am GMT on the day of the event.''' This will allow time for admin to copy out the provisional bracket list, and allows all players to know who they are expected to play and where well before time. The most important thing for players to do is '''elect a Team-Captain who you can trust''', who listens to everyone in the team, who is capable of communicating with other team-captains, and can follow the procedure to the letter on the night. You may also wish to elect a stand-in in-case the Team-Captain can't make it.
 
  
=== Stage 2 ===
+
===Stage 2 - Adding the teams===
'''Ladle Enthusiast meet On [[IRC Channel|IRC Armagetron]] sometime between 18 and 22 GMT the TBA day Prior to the ladle to determine the brackets'''
 
  
Once here one Enthusiast will fill in the servers to play on,
+
Only the Team-Captain is authorized to place your team on the Challenge Board. Team captains must also list their Global ID. Changes to the team roster can happen at any time, however, the cut off for the provisional placement of teams is 18:00 GMT  on Thursday before the event. This will allow time for server admin's to update their servers. Teams will also be able to finalize their players based on the brackets. It will also will allow players and enthusiasts to post their predictions on the forums, if they want to.
*Odd numbered ladles have Finals played in a US server.
 
*Even numbered ladles have Finals played in a Euro server.
 
*servers must flow smoothly.
 
Once servers are set and agreed on by players then someone will check to make sure they have .randomteam working (try to make sure you put testing Prior to this) this divides arguments by spaces so no names can contain spaces or else there will be errors.
 
once confirmed one players does .r and another follows with the .randomteam command, the result of that .randomteam sets the challenge board up. once player adds them in accordingly and others confirm. If a .randomteam error was not caught in the initial testing than test and redo the .r and .randomteam commands.
 
  
=== Stage 3 ===
+
The most important thing for players to do in this stage is to:
'''Team-Captains register at  [[IRC Channel|IRC Armagetron]] at 7pm gmt, then teams play the best of 3 matches.'''
+
*Elect a Team-Captain who you can trust, who listens to everyone in the team, who is capable of communicating with other team-captains, and can follow the procedure to the letter on the night.
 +
**A Team Captain should also be familiar with authentication. (You may also wish to elect a stand-in in-case the Team-Captain can't make it.)
 +
**A team leader should have their team signed up before the deadline
  
Before the first round, all Team-Captains should familiarize themselves with IRC using one of the web interfaces such as [http://java.freenode.net//index.php?channel=armagetron.tourneys '''PJIRC'''] or [http://embed.mibbit.com/?server=irc.freenode.net&channel=%23armagetron%2C%23armagetron.tourneys&noServerTab=false&forcePrompt=true  '''Mibbit'''] . Useful instructions include '''/nick <your name>''' and '''/join #armagetron.tourneys'''. Last minute alterations to brackets should be decided upon, and once confirmed, all players can view the brackets on the wiki at the Challenge Board. Team-Captains return to their teams and confirm who they are playing and where.
+
===Stage 3 - Setting the challenge board===
  
The Final is at 9pm GMT, Semi's at 8.15pm GMT, Quarter's at 7.30pm GMT, and previous rounds every 45mins for as many rounds as required. The Challenge Board has the details of who and where players should be assembled, in case there are problems with IRC chatrooms, or players need to take a leak, etc. Do not listen to random people appearing and changing plans suddenly. Stick to the script -- it has taken a month of preparation to write it...
+
Ladle Enthusiasts meet On [[IRC Channel|IRC Armagetron]] sometime between 18 and 22 GMT the Thursday prior to the Ladle to determine the brackets.
  
Administration will record results on the brackets as they come in. '''The brackets should be followed''', unless Team-Captains have legitimate reason to alter the course of progress. The only thing to be decided, if there is any question, is the server. When approaching the final, teams will rightly wish to play on servers which favour them. This must ultimately be resolved by the Team-Captains involved.
+
Once here one Enthusiast will fill in the servers to play on,
  
On the games on Z-Man's Ladle Frotress, team management is available; designated team captains can choose to lock their teams themselves so no random people can join, can then invite their players without hoping the admin does an ALLOW_TEAM_CHANGE_PLAYER command in time, and substitute players can already participate in team chat. [[Authentication for Players#Benefits|More on that here]].
+
  *Odd numbered ladles have Finals played in a US server.
 +
  *Even numbered ladles have Finals played in a Euro server.
 +
  *servers must flow smoothly.
  
=== Stage 4 ===
+
Once servers are set and agreed on by players then someone will check to make sure they have .randomteam working (try to make sure you put testing Prior to this) this divides arguments by spaces so no names can contain spaces or else there will be errors. once confirmed one players does .r and another follows with the .randomteam command, the result of that .randomteam sets the challenge board up. once player adds them in accordingly and others confirm. If a .randomteam error was not caught in the initial testing than test and redo the .r and .randomteam commands.
'''Winners are celebrated, participants are congratulated, and game-analysis, results and feedback are welcomed!'''
 
  
Hurrah! Well done! Feedback is welcome to improve the system for the next time. Reports on game play, video's, etc, also invests more value in the game.
+
===Stage 4 - Playing the ladle===
  
== Guidelines ==
+
Teams meet at the designated servers on Ladle day and play the best of 3 matches.
 +
 
 +
Administration will record results on the brackets as they come in. The brackets should be followed, unless Team-Captains have legitimate reason to alter the course of progress. The only thing to be decided, if there is any question, is the server. If there is an issue with the primary server Team-Captains can discuss moving to the secondary server (examples: the majority of the players are from the US/EU and want to play on a "home" server, or the primary server becomes unstable).
 +
 
 +
Team management is available on all Ladle servers. Designated team captains should lock their teams so no random people can join, then invite their teammates as they arrive. More on that here.
  
 
The following guidelines for all players may prove useful:
 
The following guidelines for all players may prove useful:
*Only Team-captains should alter the provisional play-offs in the Challenge Room. A spot switching has to be in agreement between both teams interested.
 
*During the event, do not listen to anyone external to your team; rely on your Team-captain for information as to who you are playing and where.
 
*Regarding ping, make sure your team-captain is aware of your server preference when s/he enters your team in the Challenge Board.
 
*Regarding imbalanced teams... anything less than a full of team of 6 is your problem... an obliging opponent may reduce their numbers if they wish...
 
*If opponents don't turn up on time, they forfeit, unless again a team wishes to delay the start... though this causes problems for subsequent timing...
 
*Regarding new players turning up: server admins can make their server private, lock it once all players are in, or kick new players immediately
 
  
If you wish to discuss any of the stages, add to the guidelines or contribute to the rules, please click on the discussion tab above.
+
  *During the event, do not listen to anyone external to your team; rely on your Team-captain for information as to who you are playing and where.
 +
  *Regarding ping, make sure your team-captain is aware of your server preference.
 +
  *Regarding imbalanced teams... anything less than a full of team of 6 is your problem... an obliging opponent may reduce their numbers if they wish...
 +
  *If opponents don't turn up on time, they forfeit, unless again a team wishes to delay the start... though this causes problems for subsequent timing...
 +
  *Regarding new players turning up: server admins can make their server private, lock it once all players are in, or kick new players immediately
 +
 
 +
===Stage 5  - The outcome===
 +
 
 +
Players use the forums to congratulate the winners, discuss issues, and eventually vote for changes where needed.
 +
 
 +
The majority of Ladles run smoothly, however, problems occasionally arise. So far, the most successful way of dealing with problems is quarterly voting (currently every 3 Ladles starting from L-21). A Ladle Enthusiast creates a "voting discussion thread" on the forum to decide on which issues need a vote [http://forums3.armagetronad.net/viewtopic.php?f=60&t=19444&start=0 here] is an example.
 +
 
 +
===Stage 6 - Quarterly voting===
 +
 
 +
After the discussion is exhausted, and with enough time for a fair vote (at least a week before Ladle day), A "Ladle voting" thread is created. Only Team Captains or someone in charge of the team currently signed up on the Challenge Board may vote; Only  one vote per team. The vote ends when the Challenge Board is closed to sign-ups (see above). The results of the vote are then edited into the wiki and the ladle.cfg files.
 +
 
  
 
{{:Ladle/Blurb}}
 
{{:Ladle/Blurb}}
  
 
[[Category:Events]]
 
[[Category:Events]]

Revision as of 20:30, 24 January 2010

Ladle Info | About | Challenge Board | Tools | Operations | Results | Statistics | Voting | Bowl
The One hundred and fifty-seventh TRONIC Ladle will be played on Sunday, March 3rd, 2024!
  • Discussion for Ladle 157 is taking place [ here].
  • Server administrators please update your config files.
  • Teams please sign up on the Challenge Board.
  • Then get some practice in before the big day! :)

Stages

Stage 1 - Preparation

A Ladle Enthusiast will prepare the wiki for a new event keeping the following in mind: Per tradition, the Ladle will be played on the first Sunday of every month (except for January, which will take place on the Sunday following the first Tuesday of the month). The opening round of play will start at 18:45 GMT for a 16 team bracket, and 18:00 GMT for a 32-team bracket. The start times will change to follow Daylight Savings Time in the EU. Generally, 45 minutes is allowed to complete each round.


Stage 2 - Adding the teams

Only the Team-Captain is authorized to place your team on the Challenge Board. Team captains must also list their Global ID. Changes to the team roster can happen at any time, however, the cut off for the provisional placement of teams is 18:00 GMT on Thursday before the event. This will allow time for server admin's to update their servers. Teams will also be able to finalize their players based on the brackets. It will also will allow players and enthusiasts to post their predictions on the forums, if they want to.

The most important thing for players to do in this stage is to:

*Elect a Team-Captain who you can trust, who listens to everyone in the team, who is capable of communicating with other team-captains, and can follow the procedure to the letter on the night.
**A Team Captain should also be familiar with authentication. (You may also wish to elect a stand-in in-case the Team-Captain can't make it.)
**A team leader should have their team signed up before the deadline

Stage 3 - Setting the challenge board

Ladle Enthusiasts meet On IRC Armagetron sometime between 18 and 22 GMT the Thursday prior to the Ladle to determine the brackets.

Once here one Enthusiast will fill in the servers to play on,

  *Odd numbered ladles have Finals played in a US server.
  *Even numbered ladles have Finals played in a Euro server.
  *servers must flow smoothly.

Once servers are set and agreed on by players then someone will check to make sure they have .randomteam working (try to make sure you put testing Prior to this) this divides arguments by spaces so no names can contain spaces or else there will be errors. once confirmed one players does .r and another follows with the .randomteam command, the result of that .randomteam sets the challenge board up. once player adds them in accordingly and others confirm. If a .randomteam error was not caught in the initial testing than test and redo the .r and .randomteam commands.

Stage 4 - Playing the ladle

Teams meet at the designated servers on Ladle day and play the best of 3 matches.

Administration will record results on the brackets as they come in. The brackets should be followed, unless Team-Captains have legitimate reason to alter the course of progress. The only thing to be decided, if there is any question, is the server. If there is an issue with the primary server Team-Captains can discuss moving to the secondary server (examples: the majority of the players are from the US/EU and want to play on a "home" server, or the primary server becomes unstable).

Team management is available on all Ladle servers. Designated team captains should lock their teams so no random people can join, then invite their teammates as they arrive. More on that here.

The following guidelines for all players may prove useful:

  *During the event, do not listen to anyone external to your team; rely on your Team-captain for information as to who you are playing and where.
  *Regarding ping, make sure your team-captain is aware of your server preference.
  *Regarding imbalanced teams... anything less than a full of team of 6 is your problem... an obliging opponent may reduce their numbers if they wish...
  *If opponents don't turn up on time, they forfeit, unless again a team wishes to delay the start... though this causes problems for subsequent timing...
  *Regarding new players turning up: server admins can make their server private, lock it once all players are in, or kick new players immediately

Stage 5 - The outcome

Players use the forums to congratulate the winners, discuss issues, and eventually vote for changes where needed.

The majority of Ladles run smoothly, however, problems occasionally arise. So far, the most successful way of dealing with problems is quarterly voting (currently every 3 Ladles starting from L-21). A Ladle Enthusiast creates a "voting discussion thread" on the forum to decide on which issues need a vote here is an example.

Stage 6 - Quarterly voting

After the discussion is exhausted, and with enough time for a fair vote (at least a week before Ladle day), A "Ladle voting" thread is created. Only Team Captains or someone in charge of the team currently signed up on the Challenge Board may vote; Only one vote per team. The vote ends when the Challenge Board is closed to sign-ups (see above). The results of the vote are then edited into the wiki and the ladle.cfg files.


Ladle Info | About | Challenge Board | Tools | Operations | Results | Statistics | Voting | Bowl
The One hundred and fifty-seventh TRONIC Ladle will be played on Sunday, March 3rd, 2024!
  • Discussion for Ladle 157 is taking place [ here].
  • Server administrators please update your config files.
  • Teams please sign up on the Challenge Board.
  • Then get some practice in before the big day! :)