|
I would think that Rainouts & Rescheduling as optional and configurable would the way to go. Something like this:
1. Gamer could select Rainouts & Auto-Rescheduling as Yes or No option.
2. If Yes, gamer could select Stop Sim on No-Reschedule as Yes or No, in order to tell the game - during auto-sim - whether or not to stop auto-sim when it is unable to reschedule a rainout. More on that below...
3. Gamer could then select how the game would approach rescheduling rained out games, by use of percentages. For examples:
MODERN SETTINGS (as per LGO's stats from the 2011 season):
- Schedule as Day/Night Doubleheader: 48%
- Single game on Common Off Day: 30%
- Schedule as a Single Admission Doubleheader: 22%
- Do not reschedule: 0%
- Switch home team allowed*: No
EARLY 20th CENTURY SETTINGS (totally making these up; LGO could likely come up with realistic numbers):
- Schedule as Day/Night Doubleheader: 0%
- Single game on Common Off Day: 25%
- Schedule as a Single Admission Doubleheader: 55%
- Do not reschedule: 20%
- Switch home team allowed*: Yes
* Switch home team allowed would be to account for when, historically (minimal and less-than-thorough research appears to confirm) make-up games were sometimes held in the opposite city, presumably for travel/geographic/scheduling considerations/restrictions. For example, if LA is rained out in Cincy and there are no more games on the schedule between the two teams in Cincy, the game might be made up later when the teams meet in LA.
3. Then, once the internal game engine "rolls the weighted dice" (based on %'s above) to determine the type of make-up game (decides if D/N doubleheader, single admission doubleheader, off day makeup game, or no rescheduling), the game would follow logic - which wouldn't be too hard to develop, especially once LGO compiles the historical data ;-) - to analyze the remaining schedule and pick a date suitable for the makeup game. If the logic comes up empty (for example, no remaining dates between the teams, or off days, remain) and the game is unable to reschedule, then the gamer can consult the Rain Out Log to see which games were rained out and not rescheduled (and then the gamer can decide what, if anything, to do - manually - about those). The simple Rainout Log would also be useful to see which games were rained out, dates of rainout, date of reschedule game (if exists), and type of rescheduled game (off day, d/n dh, dh, not rescheduled). And if the Stop Sim option (#2 above) were set to Yes, the gamer would be able to check the log right then and there.
I think the merits of this approach are that it can be 1) comprehensively configured by the gamer to be fairly realistic, totally non-realistic, or anywhere in-between, 2) it can be used to where it is very non-intrusive, depending upon settings, and 3) for those users who couldn't care less about rainouts, it can be turned off.
|