|
While the financial aspect is not something that interests me, the idea of having a ballpark creator where you input things like fence heights and distance from fair territory for the stands and the program then calculates the amount of foul territory and the program uses this information (in conjunction with altitude) to give you ball park effects.
From a user standpoint, it is a little backwards to ask for the desired park factors from the user and have the fence distances meaningless. A user putting in a 400 ft CF at sea level means nothing. The "400" might as well be "Fred" for all that it means to the game play.
To have a coded standard that can be accessed would be wonderful.
Do I want a 1.132 HR factor? I don't freaking know. But I want a Three River Stadium with 10' fences 5 feet closer than they were in 1979. A computer program of this nature should be able to give me a HR factor (among the others) that may be something like 1.132, or a whole lot different. It doesn't matter what the number actually is. What matters is that there is a mechanism for providing a contextual figure within the software.
I, as the user, shouldn't have to guess what number OOTP needs to make this reality configure to the context of the other parks in my environment. A tool should provide a number. Then I should have the option of modifying that number further, if I desire.
Before getting into the infinitely more nebulous labor of making the financials of a ballpark "realistic". How about a tool that gives us a proper output when, for instance, we move in the power alley fences for our newly signed Dave Winfield?
Such a feature would have broad appeal, I believe.
There might also be a niche group of people interested in adjustable gravity factors, as well.....but, that is, literally, asking for the moon.
|