Post by smatheny on Sept 24, 2011 18:16:32 GMT -5
Scheduling rules[/u]
We will advance every 4 days to begin with, this may change to 2/wk if we have no issues getting games played. (I'm in more than 1 league like the rest of you - lets all respect our opponents' time and the league in general by working hard to get our games in on time).
With the four day schedule, I expect every team to post in the schedule thread by the first day of the week (preferably as soon as the threads are open, should be the day before the advance). If a team has not posted by the second day of the current week, the opponent may request a sub game. YOU MUST request a sub first, then if no sub can be arranged by the final day of the week, a cpu game wil lbe allowed. NO CPU GAMES will be played unless the commish or other admin expressly notes it in the schedule thread. All correspondence - sub request, etc. will take place in the schedule thread.
Schedule Threads[/u]
USE the FORUM to SCHEDULE - I know we all use XBL msgs when they are quick and convenient, but they do not provide me with a record of what happened. If you come to me and say you have sent 101 XBL msgs and your opponent hasn't answered, I will a) think you are nuts, and b) not give any credence to your attempts to schedule. If it didn't happen in the SCHEDULE THREAD, it didn't happen. OK, that's clear.
Failure to show up without response will leave you subject to punishment. Repeated offenses in scheduling will lead to expulsion from the league.
Disconnects
If your game gets disconnected for whatever reason, please follow these guildlines.
My preference, and the way I will almost handle a DC, is to start over with whoever had the ball receiving the kick off, & playing the remaining amount of time. At which point you will stop playing, & add the current score to the original score. Then the winner can replay the cpu, or the loser can just quit and the game counted (the game has to be in the third qtr I think).
If both owners agree the game can be restarted and played from scratch.
IF you both agree to play it out, the original score is lost & forgotten, there will be no going back once you lose to try to add the score, & play cpu. (contact staff member to verify that you both are forfeiting the original score to "play it out".. If there is no staff member available make a post in the forums & both owners reply in the thread that you agree to "Play it out")
If the game is out of reach, up by 24 or more in 4th qtr, I would recommend just going the cpu option right away.
The owner who plays the CPU must play fairly & still be respectable. Do not run up the score or try to injure players. If a player on the OPPOSING TEAM is injured, I would allow you to restart your game if that injury is longer then 5 weeks in the interest of good sportmanship.
If a DC happens for whatever reason, you need to document the fact that you were disconnected. Also document what the agreed up on resolution was. Where do you think? In the SCHEDULE THREAD.
All disconnected games will be logged to help us determine a pattern of owners always being in a game the gets disconnected.
We will advance every 4 days to begin with, this may change to 2/wk if we have no issues getting games played. (I'm in more than 1 league like the rest of you - lets all respect our opponents' time and the league in general by working hard to get our games in on time).
With the four day schedule, I expect every team to post in the schedule thread by the first day of the week (preferably as soon as the threads are open, should be the day before the advance). If a team has not posted by the second day of the current week, the opponent may request a sub game. YOU MUST request a sub first, then if no sub can be arranged by the final day of the week, a cpu game wil lbe allowed. NO CPU GAMES will be played unless the commish or other admin expressly notes it in the schedule thread. All correspondence - sub request, etc. will take place in the schedule thread.
Schedule Threads[/u]
USE the FORUM to SCHEDULE - I know we all use XBL msgs when they are quick and convenient, but they do not provide me with a record of what happened. If you come to me and say you have sent 101 XBL msgs and your opponent hasn't answered, I will a) think you are nuts, and b) not give any credence to your attempts to schedule. If it didn't happen in the SCHEDULE THREAD, it didn't happen. OK, that's clear.
Failure to show up without response will leave you subject to punishment. Repeated offenses in scheduling will lead to expulsion from the league.
Disconnects
If your game gets disconnected for whatever reason, please follow these guildlines.
My preference, and the way I will almost handle a DC, is to start over with whoever had the ball receiving the kick off, & playing the remaining amount of time. At which point you will stop playing, & add the current score to the original score. Then the winner can replay the cpu, or the loser can just quit and the game counted (the game has to be in the third qtr I think).
If both owners agree the game can be restarted and played from scratch.
IF you both agree to play it out, the original score is lost & forgotten, there will be no going back once you lose to try to add the score, & play cpu. (contact staff member to verify that you both are forfeiting the original score to "play it out".. If there is no staff member available make a post in the forums & both owners reply in the thread that you agree to "Play it out")
If the game is out of reach, up by 24 or more in 4th qtr, I would recommend just going the cpu option right away.
The owner who plays the CPU must play fairly & still be respectable. Do not run up the score or try to injure players. If a player on the OPPOSING TEAM is injured, I would allow you to restart your game if that injury is longer then 5 weeks in the interest of good sportmanship.
If a DC happens for whatever reason, you need to document the fact that you were disconnected. Also document what the agreed up on resolution was. Where do you think? In the SCHEDULE THREAD.
All disconnected games will be logged to help us determine a pattern of owners always being in a game the gets disconnected.