Quote:
Originally Posted by Syd Thrift
Even though the game presents you with a Contact rating, that rating is not used directly by the game. Basically, so far as I know, the game flow looks like:
- determine if a player struck out
- if not, determine if they walked
- if not, determine if they hit a HR
- if not, determine if their ball in play was a hit or not
No matter what the ceiling of any of those are, you’re not going to have a stack overflow when you “combine” them because you’ll never combine those ratings. There’s some sort of “stuff vs avoid Ks” kind of mojo that occurs but IME you don’t see stack overflow issues there either, and there are a variety of ways to avoid that, and I don’t know exactly how the game makes those “rolls” I noted above in the first place, so I’m not even going to speculate on how.
Just, as the big takeaway, Contact is not directly used by the game, only its component parts.
|
I think you are close, I see the game flow more like:
- determine if a batter is HBP (hidden ratings for both P and hitter IIRC)
- determine if a batter walked (Eye vs Control, maybe +/- some C Ability too)
- determine if a batter K'ed (AvK vs Stuff, maybe +/- some C Ability too)
- contact made: determine if it went for a HR (Power vs MOV, +/- park factors)
- determine if the ball in the field of play is a hit (BABIP +/- fielding, +/- park factors)
- (somewhere fielding errors come into play here too)
- determine if a hit is a XBH (GAP, +/- park factors + baserunning, possibly fielding/arm)