[QuantaCondor]

Originally Posted by Argonaut

There's that piece too, though on the aggregate hitters will pull to the opposite field moreso than otherwise.

I'm interested in the nuts-and-bolts behind park factors and batted balls. Like, the OOTP engine sees 1.10 LHB AVG and 0.90 RHB AVG and does a good job of reflecting this skew in long-term statistics and results. But say in one case you had a 60 rated LF and a 60 rated RF, and in the other case you had a 50 rated LF and a 70 rated RF.

Would the latter setup be better for this park? Would the engine "understand" that a better right-fielder helps to mitigate the 1.10 LHB AVG park? What do these factors even "mean" in terms of park dimensions, especially if you also have 1.10 LHB HR.. a wide right field area and a tiny fence?

My gut feeling is that the OOTP engine will get this right.. especially because it seems to reflect the advantages of bunting against the infield shift. But I don't know the nuts-and-bolts of how it gets it right.

Probably hitter BABIP is opposed by defender Range for the relevant batted ball location. So, if opposing hitters pull more, then those fielders would be more important. I don't think it's a stretch at all for this to be integrated, I think I'd even expect it.