Specialist secondary role and player usage

Twax · 04-28-2019, 09:55 PM

Hello,

I am about 40 games into my season, and I've noticed that there seems to be a little problem with a relieve usage when his secondary role is set at "specialist". As you can see in the picture below, K. Crockett is player usage is set a "use more often" while his secondary role is "specialist". What happens during game is the AI recognise his secondary role and use him against lefties, but they always take him out after that single batter. It looks to me like once he gets put in the game as a specialist, it the AI forgets that he's also my best middle relieve and that he should be used more often. Most of the time they switch him out for G. Moya, who's another LHP.

The results is that Crockett who should be used more often has only pitched 7 innings while Moya has pitched 20 :

I don't know if this is considered a bug or if it's just a flaw in the AI but it would be cool if it could be fixed.

Thank you.

endgame · 04-28-2019, 10:09 PM

I'm not offering anything but passing opinion. I don't think I see enough data to form an opinion on this one so I'll keep the one I have for now: there are so many factors that contribute to the use of this particular pitcher. One missing element, unless I've missed it, is the number of games in which they've made appearances. Crockett, for instance, 7IP and double that in appearances?

diamond3017 · 04-28-2019, 10:36 PM

Your hook reliever settings might be coming into play as well. I think hook settings are based on runs allowed, not pitch count, so that high ERA might indicate that he is getting pulled quickly due to allowing runs (if you do indeed have a quick RP hook in your strategy settings).

Matt Arnold · 04-29-2019, 10:58 AM

Yes, currently if a player is "selected" as a LOOGY, then as soon as an opposite-handed hitter comes up they will pretty much always be replaced. We'll look into what can be done - I noticed this too recently on a team I was running.

NoOne · 04-29-2019, 12:11 PM

would be a great improvement to consider the primary role when brought in for any secondary role. not just this context.

Twax · 04-29-2019, 12:40 PM

Quote:

Originally Posted by Matt Arnold

Yes, currently if a player is "selected" as a LOOGY, then as soon as an opposite-handed hitter comes up they will pretty much always be replaced. We'll look into what can be done - I noticed this too recently on a team I was running.

Good to hear thank you !!

Dyzalot · 04-29-2019, 04:33 PM

Wish there was a way for the strategy to designate certain relievers as "avoid using vs righties in high leverage spots" without designating them as a lefty specialist or vice versa. Then maybe someone like that can be used as a standard middle reliever in standard spots or blowouts but would only be preferred by the AI against lefties or righties in high leverage situations.

polydamas · 07-15-2019, 05:57 AM

Has this been addressed in a patch yet?

04-28-2019, 09:55 PM	#1
Twax Minors (Rookie Ball) Join Date: May 2018 Posts: 45	Specialist secondary role and player usage Hello, I am about 40 games into my season, and I've noticed that there seems to be a little problem with a relieve usage when his secondary role is set at "specialist". As you can see in the picture below, K. Crockett is player usage is set a "use more often" while his secondary role is "specialist". What happens during game is the AI recognise his secondary role and use him against lefties, but they always take him out after that single batter. It looks to me like once he gets put in the game as a specialist, it the AI forgets that he's also my best middle relieve and that he should be used more often. Most of the time they switch him out for G. Moya, who's another LHP. The results is that Crockett who should be used more often has only pitched 7 innings while Moya has pitched 20 : I don't know if this is considered a bug or if it's just a flaw in the AI but it would be cool if it could be fixed. Thank you.

04-28-2019, 10:09 PM	#2
endgame Hall Of Famer Join Date: Aug 2002 Posts: 16,843	I'm not offering anything but passing opinion. I don't think I see enough data to form an opinion on this one so I'll keep the one I have for now: there are so many factors that contribute to the use of this particular pitcher. One missing element, unless I've missed it, is the number of games in which they've made appearances. Crockett, for instance, 7IP and double that in appearances? __________________ "Try again. Fail again. Fail better." -- Samuel Beckett _____________________________________________

04-28-2019, 10:36 PM	#3
diamond3017 Minors (Single A) Join Date: Sep 2017 Posts: 88	Your hook reliever settings might be coming into play as well. I think hook settings are based on runs allowed, not pitch count, so that high ERA might indicate that he is getting pulled quickly due to allowing runs (if you do indeed have a quick RP hook in your strategy settings). Last edited by diamond3017; 04-28-2019 at 10:37 PM.

04-29-2019, 10:58 AM	#4
Matt Arnold OOTP Developer Join Date: Jun 2009 Location: Here and there Posts: 14,149	Yes, currently if a player is "selected" as a LOOGY, then as soon as an opposite-handed hitter comes up they will pretty much always be replaced. We'll look into what can be done - I noticed this too recently on a team I was running.

04-29-2019, 12:11 PM	#5
NoOne Hall Of Famer Join Date: Apr 2015 Posts: 7,167	would be a great improvement to consider the primary role when brought in for any secondary role. not just this context.

04-29-2019, 04:33 PM	#7
Dyzalot All Star Starter Join Date: May 2008 Posts: 1,735	Wish there was a way for the strategy to designate certain relievers as "avoid using vs righties in high leverage spots" without designating them as a lefty specialist or vice versa. Then maybe someone like that can be used as a standard middle reliever in standard spots or blowouts but would only be preferred by the AI against lefties or righties in high leverage situations.

07-15-2019, 05:57 AM	#8
polydamas All Star Reserve Join Date: Jul 2011 Posts: 598	Has this been addressed in a patch yet?