Thread: Bunting for hit
View Single Post
Old 05-08-2012, 06:30 PM   #7
Charlie Hough
Hall Of Famer
 
Charlie Hough's Avatar
 
Join Date: May 2006
Posts: 3,644
Quote:
Originally Posted by SteveP View Post
I studied this at some length a couple of years ago and found that bunt for hit success in OOTP was about half of what it should be according to actual stats (which don't exist for the entire MLB history, so one has to assume this is fairly constant). So I set the config file for this to 200.

I also set the overall bunting success rate to 170, to compensate for the fact that too many sac bunts end up with double plays or outs on the lead runner, again in comparison to actual stats.

FWIW
This is a beautiful example of what I'm talking about. Large scale testing will often show the complete opposite of what people intuitively believe is happening in the game. As your testing indicated, the success rates for bunting may actually be too low in the game rather than too high.

As for Bledsoe, I'm sure your intentions are constructive, but hunches are NOT a productive way to report a potential bug. However, this isn't a personal criticism. This is just an epidemic that has been sweeping the forums for years, and your post finally moved me to express the frustration that it brings about.

Human beings are highly prone to bias, bad reasoning, and unreliability. So, in any form of software development, a problem has to be repeatable, duplicated on multiple installations, and statistically significant to warrant reviewing it.

If the developer goes off on a wild goose chase to examine every claim based on anecdotal evidence and minimal sample sizes, then we're never going to see new versions released or new features developed. All the developer's time will be spent on dispelling unfounded claims.

That's why some of the others in the community try to step in and ask people to do more research, be more sure that there is a problem, and satisfy some basic criteria before we draw any conclusions. If we have multiple users reporting the same issue and able to repeat it and confirm it with large-scale testing, then we'll be the first ones to support reporting it as a bug. And this will help get it addressed much faster and more efficiently.

There is simply no way that any developer has the time or resources to investigate every claim that is posted without sufficient evidence. So if you want your concerns addressed, there are better ways to do it.

So, apologies for you being the unwitting victim of a rant, but we're seeing similar postings constantly, and we need to figure out a way to steer things in a more sensible direction. This is perhaps something that warrants a stickied thread on all the forums to remind people about the criteria we need to satisfy to help us quickly determine if there is a real problem and how to fix it.

Last edited by Charlie Hough; 05-08-2012 at 06:32 PM.
Charlie Hough is offline   Reply With Quote