[darkcloud4579]

LGO is dead on to what I was saying/asking. I spent years on beta and I lead a huge programming team (in my day job and have for over a decade) so I understand the constraints of technical projects. I wasn't going off on a rant, really. And i'm notorious for shooting down ideas I think are insane in here, so...I was initially taking a dose of my own medicine.

Except now.

The origin of this post is, if you know anything about cricket...you know that there are different forms all based on time. The most popular at the moment is Twenty20 cricket which is a limited amount of overs and outs.

I have a theory that baseball would regain popularity and would be better if games were shorter. Since if every game in a year were rained out, 5 inning games would count, I think baseball games should all be 5 (or 6) innings because it'd change the entire complexity of the game.

I'd be super curious to simulate that over a period of time and see what it'd do, etc. etc. and test it out. I could do it in OOTP now if I wanted to, if I played both teams out and essentially did something like manage them both or whatever. But...I don't really want to do that. Though now that I type that i'm considering it.

Even if the game allowed for inducing a rain delay or making it so you could end a game after 5 or 6 or 7 or 8 innings due to rain, it'd serve my purpose the same way.

I don't want the code base to be changed to reflect this idea AT ALL. ONLY the functionality to shorten games because IN THE REAL WORLD baseball games DO NOT ALWAYS go nine innings and in OOTP they ALWAYS do because rain delays exist, but no games end with rain.

So I just went from asking for a thing that's "unrealistic" to actually asking for a thing that more accurately reflects baseball in the real world.

ACTUAL rain shortened games.

There.

Thanks for the debate and helping me flesh this out, gang.