|
|
Starting Date |
Ending Date |
Trading
Deadline |
CM Due Date |
Results Due
Date |
|
Block 1 |
4/4/2016 |
4/14/2016 |
3/26/2016 |
4/1/2016 |
4/14/2016 |
|
Block 2 |
4/15/2016 |
4/30/2016 |
4/15/2016 |
4/18/2016 |
4/30/2016 |
|
Block 3 |
5/1/2016 |
5/15/2016 |
4/30/2016 |
5/3/2016 |
5/15/2016 |
|
Block 4 |
5/16/2016 |
5/31/2016 |
5/15/2016 |
5/18/2016 |
5/31/2016 |
|
Block 5 |
6/1/2016 |
6/15/2016 |
5/31/2016 |
6/3/2016 |
6/15/2016 |
|
Block 6 |
6/16/2016 |
6/30/2016 |
6/15/2016 |
6/18/2016 |
6/30/2016 |
|
Block 7 |
7/1/2016 |
7/15/2016 |
6/30/2016 |
7/3/2016 |
7/15/2016 |
|
Block 8 |
7/16/2016 |
7/31/2016 |
7/15/2016 |
7/18/2016 |
7/31/2016 |
|
Block 9 |
8/1/2016 |
8/15/2016 |
7/31/2016 |
8/3/2016 |
8/15/2016 |
|
Block 10 |
8/16/2016 |
8/31/2016 |
|
8/18/2016 |
8/31/2016 |
|
Block 11 |
9/1/2016 |
9/15/2016 |
|
9/3/2016 |
9/15/2016 |
|
Block 12 |
9/16/2016 |
9/28/2016 |
|
9/18/2016 |
9/28/2016 |
|
|
|
|
|
|
|
|
All due dates/deadlines are 10:00 pm
Eastern on the date shown. |
|
|
|
|
|
|
|
|
|
The SPIBL process: |
|
|
|
|
|
1) At the beginning of the season a league
file will be sent out. This file is used ONLY to create CMs. |
|
2) At the CM Due Date, all CMs received will
be imported to create a PLAYBALL file to be sent out. |
|
3) If any CMs are missing, a
computer-generated CM will be created by the league statistician. |
|
4) Each team owner will import the PLAYBALL
file and play his home games for the block. Netplay permitted. |
|
5) At the Results Due Date, the league
statistician will import all game results received and autoplay any
missing games. |
|
6) When all games for the block have been
played, the league statistician will incorporate any roster changes |
|
for the upcoming block of games and send out
a new league file. Teams will update their CMs as needed |
|
from this file. |
|
|
|
|
|
7) The process above repeats for each block
of the season. |
|
