Having problems with catchers in minor leagues

markprior22 · 05-09-2013, 09:55 AM

I haven't noticed this problem in my particular league in the past but I'm seeing issues with minor league teams not having a backup catcher in the depth chart. They have catchers on the roster but they keep starting them at other positions (almost always 1B) and leaving the backup catcher slot empty. I've tried clicking the "force start/play at" box to catcher and it still doesn't work. Originally I had lineups/depth charts set to AI mgr. I had to sign a FA catcher that played no other position and then he was put in as backup. My AAA team has 3 catchers, one is a 5 at C and a 2 at LF. The AI keeps playing him at LF even when I checked "play as catcher." I'm pretty sure something is up with this part of the game as I didn't see it before in the same league. It causes problems because your number one catcher will catch every day no matter how tired he is. No matter how crappy my other position players are, if I tell the AI to use this guy as a catcher, it should be doing that.

BIG17EASY · 05-09-2013, 10:22 AM

I noticed that in 13 and what I did was use the "force start/play" function, but not for the catchers. I used it to force the AI to play the correct player at whatever position it wanted to use the catcher at.

markprior22 · 05-09-2013, 11:38 AM

Quote:

Originally Posted by BIG17EASY

I noticed that in 13 and what I did was use the "force start/play" function, but not for the catchers. I used it to force the AI to play the correct player at whatever position it wanted to use the catcher at.

Yes, forgot to mention that was one of the steps I eventually had to incorporate to get the AI to get a catcher in the depth chart. It worked but it was a lot of setting this, setting that, etc to get the desired result it seems I should get from just setting the force player position to catcher.
I'm just wondering if something might be off in this area.

Quinton_Upchurch · 05-09-2013, 11:43 AM

Just had a browse through all the teams in my fictional league and I can see similar issues. Is probably one in 15/20 teams, including ML teams, affected.

What seems to cause the problem is if the team has a position player who can also play catcher. This causes the AI to only carry one 'true' catcher on the 25 man roster. The problem is compounded where the position player/catcher is good enough to be starting at another position. In this case the depth chart won't list him as the back-up catcher. The starting catcher will then play every game.

I'll post a screenshot...

Quinton_Upchurch · 05-09-2013, 11:52 AM

Here Chesapeake has Omar Rosado who can play catcher but is also their best second baseman. The AI manager starts him at second and therefore has no back-up for Dioletis.

BIG17EASY · 05-09-2013, 11:54 AM

Quote:

Originally Posted by markprior22

Yes, forgot to mention that was one of the steps I eventually had to incorporate to get the AI to get a catcher in the depth chart. It worked but it was a lot of setting this, setting that, etc to get the desired result it seems I should get from just setting the force player position to catcher.
I'm just wondering if something might be off in this area.

I agree. I only did it for my organization, and I control all minor league transactions, so it wasn't too much extra work to keep an eye on this since the AI wasn't shuffling rosters on me. When I first noticed this happening, I looked through my world and found a lot of minor league catchers who were good hitters for their levels, but poor defensively, so I figured the AI saw a way to get a good bat in the lineup at a different position. But obviously teams would never put both of their catchers in the lineup together, even if there's a position guy who can be an emergency catcher.

I definitely think this is something that should be looked at, though.

Bluenoser · 05-09-2013, 12:13 PM

Be sure when using the "force start" option, you also select "override team strategy". Otherwise your AI manager can make a decision that doesn't agree with yours.

markprior22 · 05-09-2013, 12:50 PM

Quote:

Originally Posted by Bluenoser

Be sure when using the "force start" option, you also select "override team strategy". Otherwise your AI manager can make a decision that doesn't agree with yours.

Didn't think about that...I'll check tonight. Still seems kind of counter-intuitive though. If I go in and set the force start or lock at this minor league level, it seems to me that I'm telling the AI that, in these areas, I want to override AI strategy because if I'm controlling the team manually, I wouldn't need to select those options to begin with. I'll give it a try though.

The Game · 05-09-2013, 02:05 PM

Quote:

Originally Posted by Bluenoser

Be sure when using the "force start" option, you also select "override team strategy". Otherwise your AI manager can make a decision that doesn't agree with yours.

Didn;t think about that either. I always thought Override team strategy had to do more with stealing and pitching vs Player A playing 3B vs SS.

Has anyone tried to use force start for 2 or more C's? Wondering what would happen.

markprior22 · 05-10-2013, 11:04 AM

Also noticed last night that a young pitcher I have in AAA threw 118 pitches when I had set his limit to 100 (did have override settings selected also). I know that pitch counts can't be exact but 18 over seems like a lot. These are the type of red flags that make me think this whole area (force start, pitch limits, etc) should be looked at by Markus to make sure there aren't any obvious issues.

BIG17EASY · 05-10-2013, 12:13 PM

Quote:

Originally Posted by markprior22

Also noticed last night that a young pitcher I have in AAA threw 118 pitches when I had set his limit to 100 (did have override settings selected also). I know that pitch counts can't be exact but 18 over seems like a lot. These are the type of red flags that make me think this whole area (force start, pitch limits, etc) should be looked at by Markus to make sure there aren't any obvious issues.

How rested were your relievers? I've seen the AI push some starters 10-20 pitches beyond the limit when the bullpens are worn out.

RchW · 05-10-2013, 01:31 PM

Quote:

Originally Posted by markprior22

Also noticed last night that a young pitcher I have in AAA threw 118 pitches when I had set his limit to 100 (did have override settings selected also). I know that pitch counts can't be exact but 18 over seems like a lot. These are the type of red flags that make me think this whole area (force start, pitch limits, etc) should be looked at by Markus to make sure there aren't any obvious issues.

The internal rule AFAIK is for the pitcher to finish the inning. If you have game logs on check to see if he had a tough inning.

RchW · 05-10-2013, 01:33 PM

Quote:

Originally Posted by Bluenoser

Be sure when using the "force start" option, you also select "override team strategy". Otherwise your AI manager can make a decision that doesn't agree with yours.

I've not seen that before I often force start in the minors but never override strategy.

BIG17EASY · 05-10-2013, 01:38 PM

Quote:

Originally Posted by RchW

I've not seen that before I often force start in the minors but never override strategy.

Right, I'm pretty sure the override setting only refers to the strategy settings right below it (steal frequency, etc.). I use the "Bench Player for X Days" function constantly without using the override strategy and it works just fine.

05-09-2013, 09:55 AM	#1
markprior22 All Star Starter Join Date: Apr 2002 Location: springfield, illinois Posts: 1,235	Having problems with catchers in minor leagues I haven't noticed this problem in my particular league in the past but I'm seeing issues with minor league teams not having a backup catcher in the depth chart. They have catchers on the roster but they keep starting them at other positions (almost always 1B) and leaving the backup catcher slot empty. I've tried clicking the "force start/play at" box to catcher and it still doesn't work. Originally I had lineups/depth charts set to AI mgr. I had to sign a FA catcher that played no other position and then he was put in as backup. My AAA team has 3 catchers, one is a 5 at C and a 2 at LF. The AI keeps playing him at LF even when I checked "play as catcher." I'm pretty sure something is up with this part of the game as I didn't see it before in the same league. It causes problems because your number one catcher will catch every day no matter how tired he is. No matter how crappy my other position players are, if I tell the AI to use this guy as a catcher, it should be doing that.

05-09-2013, 11:52 AM	#5
Quinton_Upchurch All Star Reserve Join Date: Mar 2013 Posts: 789	Here Chesapeake has Omar Rosado who can play catcher but is also their best second baseman. The AI manager starts him at second and therefore has no back-up for Dioletis. Last edited by Quinton_Upchurch; 05-09-2013 at 11:58 AM.

05-09-2013, 10:22 AM	#2
BIG17EASY Hall Of Famer Join Date: Jun 2006 Posts: 3,291	I noticed that in 13 and what I did was use the "force start/play" function, but not for the catchers. I used it to force the AI to play the correct player at whatever position it wanted to use the catcher at.

05-09-2013, 11:43 AM	#4
Quinton_Upchurch All Star Reserve Join Date: Mar 2013 Posts: 789	Just had a browse through all the teams in my fictional league and I can see similar issues. Is probably one in 15/20 teams, including ML teams, affected. What seems to cause the problem is if the team has a position player who can also play catcher. This causes the AI to only carry one 'true' catcher on the 25 man roster. The problem is compounded where the position player/catcher is good enough to be starting at another position. In this case the depth chart won't list him as the back-up catcher. The starting catcher will then play every game. I'll post a screenshot...

05-09-2013, 12:13 PM	#7
Bluenoser Hall Of Famer Join Date: Mar 2002 Location: In The Moment Posts: 14,224	Be sure when using the "force start" option, you also select "override team strategy". Otherwise your AI manager can make a decision that doesn't agree with yours.

05-10-2013, 11:04 AM	#10
markprior22 All Star Starter Join Date: Apr 2002 Location: springfield, illinois Posts: 1,235	Also noticed last night that a young pitcher I have in AAA threw 118 pitches when I had set his limit to 100 (did have override settings selected also). I know that pitch counts can't be exact but 18 over seems like a lot. These are the type of red flags that make me think this whole area (force start, pitch limits, etc) should be looked at by Markus to make sure there aren't any obvious issues.