The problem with patching "problems" based on user feedback

[tessl]

I use manage mode. People complained the batters were bunting too much so the "fixed" it in the patch. Now user controlled batters never bunt for a hit.

Too many bunts are not realistic but the batter never bunting is as unrealistic because IRL players bunt for a hit on their own.

It isn't a game breaker but an example of how "fixing" something has to be done carefully.

[Bobhead]

Re: The problem with patching "problems" based on user feedback

Uhh...
I think you meant CPU controlled batters. Why would user controlled batters bunt for a hit... without input from the controlling user? If you want to bunt, press the bunt button.

If you meant CPU controlled batters, I still see a very consistent number of attempts from the CPU.
I'm not too familiar with Manager mode but my understanding is that it runs almost identical to CPU vs CPU exhibition play. Thus one would expect the same number of bunts as in a CPU vs CPU game.

So if you aren't seeing the same number of bunts, it's most likely because of a difference in your strategy (more bunt shifts), or a difference in your sliders (slower baserunners or faster fielders).

[kehlis]

Re: The problem with patching "problems" based on user feedback

Uhh...
I think you meant CPU controlled batters. Why would user controlled batters bunt for a hit... without input from the controlling user? If you want to bunt, press the bunt button.

If you meant CPU controlled batters, I still see a very consistent number of attempts from the CPU.
I'm not too familiar with Manager mode but my understanding is that it runs almost identical to CPU vs CPU exhibition play. Thus one would expect the same number of bunts as in a CPU vs CPU game.

So if you aren't seeing the same number of bunts, it's most likely because of a difference in your strategy (more bunt shifts), or a difference in your sliders (slower baserunners or faster fielders).

I use manage mode.

He's saying players should have the green light to bunt on their own without his input which would be different than him calling for a sacrifice bunt.

I don't use manage only mode but based on the timing of this post I'm assuming they did so previously.

[Jgainsey]

Re: The problem with patching "problems" based on user feedback

The problems with bunting in this year's game were quite real. No quotation marks needed.

The thread title here implies that the developers haphazardly rushed into fixing a problem in an effort to alleviate complaints from an impatient majority.

What's your point? That SCEA shouldn't accidentally create a bug while fixing a legitimate issue with the game? Ok... I really hope the developers learned their lesson.

BAD SCEA!!

BE MORE CAREFUL NEXT TIME WHEN FIXING "PROBLEMS!!!"

[tessl]

Re: The problem with patching "problems" based on user feedback

Uhh...
I think you meant CPU controlled batters. Why would user controlled batters bunt for a hit... without input from the controlling user? If you want to bunt, press the bunt button.

If you meant CPU controlled batters, I still see a very consistent number of attempts from the CPU.
I'm not too familiar with Manager mode but my understanding is that it runs almost identical to CPU vs CPU exhibition play. Thus one would expect the same number of bunts as in a CPU vs CPU game.

So if you aren't seeing the same number of bunts, it's most likely because of a difference in your strategy (more bunt shifts), or a difference in your sliders (slower baserunners or faster fielders).

To replicate reality.

[Knight165]

Re: The problem with patching "problems" based on user feedback

I would say VERY FEW batters are bunting on their own nowadays.
If you are managing the game....and you want your guy to bunt...tell him to bunt.
It beats seeing guys bunt when
-A. They shouldn't be bunting
-B. They shouldn't be bunting.
or worst of all..
-C. They shouldn't be bunting.

M.K.
Knight165

[tessl]

Re: The problem with patching "problems" based on user feedback

I would say VERY FEW batters are bunting on their own nowadays.
If you are managing the game....and you want your guy to bunt...tell him to bunt.
It beats seeing guys bunt when
-A. They shouldn't be bunting
-B. They shouldn't be bunting.
or worst of all..
-C. They shouldn't be bunting.

M.K.
Knight165

LOL - batters bunting for a hit do it on their own. Sacrifice bunts are called from the dugout. It has been that way for 100 years.

[forme95]

Re: The problem with patching "problems" based on user feedback

I use MoM mode also. I hate that you have to guess which pitch to tell the player to bunt on. I would like it better if you told the player to Sac bunt, or bunt for hit that he goes to the plate and picks the pitch to try it on.

[Knight165]

Re: The problem with patching "problems" based on user feedback

LOL - batters bunting for a hit do it on their own. Sacrifice bunts are called from the dugout. It has been that way for 100 years.

Like I said...very few nowadays do ....and they are given the green light by the manager.
NO DOUBT.

But if you want to continue to look back on baseball from 1945...and apply it to today...be my guest.

M.K.
Knight165

[tessl]

Re: The problem with patching "problems" based on user feedback

Like I said...very few nowadays do ....and they are given the green light by the manager.
NO DOUBT.

But if you want to continue to look back on baseball from 1945...and apply it to today...be my guest.

M.K.
Knight165

When did this change occur and do you have a source?

This author seems to have some doubt...

What was Chris Heisey thinking with his two-out bunt attempt?

...as do I since I've seen batters walk to the plate without looking at a coach for a sign, with no sign being give by a coach, and attempt to bunt for a hit - in 2015.

[Knight165]

Re: The problem with patching "problems" based on user feedback

When did this change occur and do you have a source?

My source is common sense.....
http://www.baseball-reference.com/le...-batting.shtml

That is 0.26737 % of hits are bunts.
I'll give you that 50 % of attempts are successful and I'll also give you that some of those are sac bunt attempts that didn't result in an out as freebies.
So just over 1/2 of a percent of AB's are bunt attempts(for hits)
Sounds like all the rage among MLB hitters.

CPU hitters still attempt bunts.
You have to tell your batters to bunt 0.53474 % of the time.
That's an insane amount of effort.
You better get a nap in before your next game.

M.K.
Knight165

[cadillacsts05]

Re: The problem with patching "problems" based on user feedback

I just had the CPU try to bunt with Jose Abreu. They had first and second with no outs. And I threw down and in thankfully he missed it. Then missed the 2nd bunt. I still see a lot of bunts that shouldn't be happening

[tessl]

Re: The problem with patching "problems" based on user feedback

I just had the CPU try to bunt with Jose Abreu. They had first and second with no outs. And I threw down and in thankfully he missed it. Then missed the 2nd bunt. I still see a lot of bunts that shouldn't be happening

The CPU bunts, the user controlled team does not.

As I said in the first post of this thread, the danger of patching "problems" based on user feedback is you end up playing that user's version of what baseball should be which is often at variance with reality.

The correct patch would have been to reduce the frequency of user players bunting, not eliminate it completely.

[Jr.]

Re: The problem with patching "problems" based on user feedback

The CPU bunts, the user controlled team does not.

As I said in the first post of this thread, the danger of patching "problems" based on user feedback is you end up playing that user's version of what baseball should be which is often at variance with reality.

The correct patch would have been to reduce the frequency of user players bunting, not eliminate it completely.

Why would the developers patch the frequency of user players bunting when all of the issues stemmed from CPU teams bunting?

[tessl]

Re: The problem with patching "problems" based on user feedback

Why would the developers patch the frequency of user players bunting when all of the issues stemmed from CPU teams bunting?

I'm not a developer, you need to ask them.