Rain-outs & double-headers
I'd like to see rain-outs in OOTP 15 where the game(s) would need to be replayed as part of a double-header. Example: Opening Day between the Cardinals and Cubs gets rained out. The computer could then ask you "Make up as double-header tomorrow?" and you could select "Yes" or "No" and the game would be made up.
|
That sounds like a great idea!
|
I really like that idea, especially if in the middle of a game and then it gets ppd due to rain so those stats don't count, adds another level of realism to the game. Although would be very frustrating if your good stats are wiped out lol
|
Quote:
|
As stated in many of the threads for this request, the OOTP scheduling function is not strong enough to be able to allow for those. This is a thread that appears many times and it is the same. Scheduling rain outs is most likely never going to be a part because OOTP just cant do it yet.
Someone should try to come up with a better schedule producer but until then, it is a nice idea, just wont happen. |
Quote:
1. If the game is already long enough to be an official game, call it. 2. If in a series, schedule a double-header the next day. 3. If this series is already full but the teams play another series later in the season, schedule a double-header then. 4. If no double-header is possible, but the teams have a common day off, schedule a game there (possibly add an exception for, say, the all-star game). 5. If none of the above is possible, the game magically continues just like it does now. |
Quote:
|
Quote:
|
Quote:
Something else to note is that the majors and minors handle rescheduling very differently. In the minors, postponed games are almost always made up as regular single admission doubleheaders, either during that series, during the next series between the teams, or in the other club's park if the two teams are finished for the season in the original park. If the teams do not play again, then the game is not made up. The majors, in contrast, will do everything possible to reschedule a game, even if the two clubs are finished for the season. Indeed, if the postponed game has a bearing on the pennant race, it can even be replayed after the end of the regular season if necessary. The minors, however, never do this. Another wrinkle to consider is that the rate of postponements has varied over the years. In earlier days, a postponement rate of 10% or more was not uncommon in MLB; these days it's typically around 1%-1.5%. The minors typically are postponed more often; it varies between leagues but these days overall it's about 4%-5%. So there's another distinction that OOTP would need to understand and recreate. Let's add to that the Scores & Schedule and other screens which would need to be updated to include postponed and rescheduled game info. The MLB.com Scoreboard is a good example of how it notes the information so that it's clear when a game is postponed and when a game is a make up game. Then there's the rule added last season which allowed clubs a 26-man active roster for a doubleheader if it was scheduled at least 48 hours in advance. OOTP does not recreate this rule as yet. Put this all together and there's lots to consider. It's doable but will take a lot of good planning to do well. |
I do like this idea but some limitations come to mind.
Where does the weather logic come from? I'm not sure the game does anything other than take a random snapshot of possible weather conditions for the month in question and applies that to game day. I don't think that weather conditions other than rain-on rain-off change in-game. Where would the game find/create conditions that would trigger a game to be suspended with such a limited weather function. What about tied games and not-official games? Having said that this is one of the "realism proposals" that piques my interest. I could see some very interesting Septembers happening with a couple of doubleheaders and/or some suspended games scheduled. |
Quote:
Quote:
|
Quote:
I'd stay away from tie games, as that can get dicey. A tie game relies on the particular rules of when a game can be called, and those have changed over the years. Plus tie games, unlike postponed games, count in terms of player statistics and attendance even though there'll be a game played to make up for the tie. So overall I'd say they'd be more trouble than they're worth. I'd also stay away from suspended games as well. It causes potential record-keeping issues since the game is started one day but completed on another day (and may not even be completed in the same park). Plus there are different rules on when a game can be suspended. In the minors almost any game stopped by rain, even one just a half-inning old, becomes a suspended game. In the majors, the rules are more strict (in addition to having changed over the years). Just getting games postponed and rescheduled would be good enough in my opinion. It adds sufficient realism and flavour without getting bogged down in all the nitty gritty facets of reality like tie and suspended games. |
Le Grande Orange, I don't really see why distinguishing between "standard" and day-night doubleheaders should be such a big deal. If the game just treated every double header as two seperate games on the same day, that would be more than good enough for me.
Anyway, to sum it up: perfect is the enemy of good. Please don't sweep rain-outs under the carpet entirely just because you can't do them perfectly. |
The main issue with coding rain outs as far as Markus has said in the past is scheduling the make up game.
|
Quote:
|
Quote:
The minors don`t have much choice since the schedules and travel arrangements there are already tight. Quote:
Quote:
Quote:
I'm thinking one way OOTP could open up its scheduling is by having two schedule files. One is the 'original' schedule file, this is the base one that the game uses to set up the slate of matchups for the upcoming season, and would operate just as it does now. OOTP then creates a copy of that schedule file for specific use in the current season; let's call that the 'dynamic' schedule file. The first thing OOTP does with that dynamic file is individually adjust the starting times for each home team; that is, each home team can have its own unique typical starting time. These can be set in the team options section, and add more variety and flavour, especially for those using the RTS feature. No longer would you be restricted to whatever start times were entered into the schedule file itself. It's in the dynamic schedule file that OOTP keeps track of postponements and slots in the dates for make up games. At the end of the season, OOTP then deletes that dynamic schedule file since it's no longer needed. It takes the original schedule file, swaps around the opponents to create new matchups just like it does now, then creates a copy of that in the form of a new dynamic schedule file for the next season. Rinse and repeat for every season. I think a system like this could work out really well, adding a lot of new potential features to the schedule side of things. Quote:
Quote:
|
Incidentally, here are the real-life postponement rates for the majors and minors thus far in the 2013 season, through games of Sunday, June 16th. These figures include make up games, whether played or postponed. These rates will continue to drop as the season progresses into the generally better weather of July and August.
MLB: 31 out of 1059 (2.9%) International League: 38 out of 525 (7.2%) Pacific Coast League: 25 out of 584 (4.3%) Eastern League: 27 out of 433 (6.2%) Southern League: 25 out of 364 (6.9%) Texas League: 15 out of 289 (5.2%) California League: 2 out of 352 (0.6%) Carolina League: 22 out of 301 (7.3%) Florida State League: 37 out of 423 (8.7%) Midwest League: 68 out of 614* (11.1%) South Atlantic League: 49 out of 528 (9.3%) * One game ended in a tie. |
Quote:
Quote:
From what you wrote further on in your post it seems we are actually largely in agreement. |
Quote:
|
Quote:
There are also those who run independent minor leagues alongside their major leagues. Those would have financials. Quote:
Implement it properly now. That will come in very handy later on. (And it's not as if anything I've suggested need be terribly complicated to do. Nothing about it seems particularly difficult. A few little changes to the file structure of the schedule files, which can easily still be backwards compatible, and we're good to go. I've already thought some of the specifics through.) Quote:
Quote:
Sooner or later I'm going to sit down and write out my ideas into a more formal proposal for Markus & Co. :) |
All times are GMT -4. The time now is 09:55 AM. |
Powered by vBulletin® Version 3.8.10
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
Copyright © 2020 Out of the Park Developments