Quote:
Originally Posted by MathBandit
What I'm saying is that let's suppose I build a world where I take the 2023 MLB rosters/teams and relocate them all to local Little League diamonds where the field dimensions are 275 down the line and 300 to straightaway centre- instead of playing in major-league parks.
The way to achieve that (or one way to achieve it, I suppose) is to take all parks and change their HR park factors to 2.000. (Yes, it would also affect all the other factors, but for the sake of this lets assume HRs are either the only thing that changes or the only change we care about). If I moved them all to those tiny parks with HR 2.000 in all of them, I would not be happy with the simulation results if the game decided that since everyone is 2.000 then no one is 2.000 and that Judge and Ohtani are still only able to hit ~40-50 HRs/year even in those stadiums. My expectation would be (similar to the results) that power numbers go through the roof and the value of those HRs plummets accordingly (note that Judge has 95 HRs but less than 6 WAR).
|
If you change all the park factors to 2.0, then, yes, HR will inflate...and better players will hit more.
Unless, I think, as Syd says, the autocalc is run. I tend to forget about autocalc because I don't think I've ever used it. But its purpose is to force league-wide totals back toward the baseline stats output you list as "desired," so I can see that it would essentially rebaseline the "average" park factor.
Regardless, unless something changed in the last version and the OOTP manual just wasn't updated, dimensions are entered to make the cosmetics of play-by-play read well.