Weird situation in a recent game for me.  I have two SS on my roster and because of fatigue I had one starting at SS and one filling in at 2B.  Of course the SS ends up getting hurt in the game and because I was resting other players my back up C had to come into the game.  That isn't the logic I have an issue with.  Why can't there be same way for the computer to think "hmmm....there is a player better suited to slide over to SS already in the game".  I would have been fine with the C ending up at 2nd base because it's my "fault" for giving guys a rest day.  But why wouldn't the computer just slide my other SS over from 2B.  That would make more sense, but it didn't happen.
7/15/2015 7:18 AM
i guess rest takes precedence in that situation no matter what
7/15/2015 8:22 AM
The sim isn't capable of doing that.   Not a programmer but maybe it's just impossible to code.   But, if your C isn't set up as a rest or defensive option for 2B, he's probably better suited, arm-wise, to play SS so that's where he was put.
7/15/2015 9:15 AM
That's a good point Mike.  As far as Sergei's comment.  I see guys get moved during games all the time from LF to 1st base or something like that when other defensive replacements come in late game. 

I didn't mean my guys that were on rest should play.  I mean the computer manager should have said "hmmm...the regular SS back up is playing 2nd.  We should probably slide him over to SS in this situation".  That has to be coded doesn't it?  I don't know.  Thanks for the thought Mike, appreciate it.

7/15/2015 3:39 PM
It's not coded.  If I'm not mistaken, you have to set it up manually in your defensive hierarchy, which means also accounting for who the second backup 2B should be.
7/15/2015 3:42 PM
The "problem" is we see the obvious.    Back up SS at 2B, SS goes down.  The obvious move is 2B to SS and then figure out the best option for 2B.   Which might be the LF.   So LF to 2B and figure out best option for LF.    Might be the back-up 1B sitting on the bench.   And that's exactly what we'd do if making the changes live.  But that's where the problem starts.   I'd move my RF to LF, LF to 2B, 2B to SS and stick my back-up C in RF.   You might say "WTF?  That dude has 4 range!!!!"

So SIMMY does what we set up and then, if forced to make a move that we haven't set up, looks at specific defensive ratings to figure out what would be "best".   C almost always end up at SS in that situation due to arm.   Which tells me that the SIM favors arm over glove/range at SS.   That might tell us something.
7/15/2015 4:29 PM
Its strange sometimes. I had my SS in the field and no one on the bench. My SS got injured and they brought a pitcher in to replace him. Strange. Oddly no errors or -
7/15/2015 4:48 PM
Posted by MikeT23 on 7/15/2015 4:29:00 PM (view original):
The "problem" is we see the obvious.    Back up SS at 2B, SS goes down.  The obvious move is 2B to SS and then figure out the best option for 2B.   Which might be the LF.   So LF to 2B and figure out best option for LF.    Might be the back-up 1B sitting on the bench.   And that's exactly what we'd do if making the changes live.  But that's where the problem starts.   I'd move my RF to LF, LF to 2B, 2B to SS and stick my back-up C in RF.   You might say "WTF?  That dude has 4 range!!!!"

So SIMMY does what we set up and then, if forced to make a move that we haven't set up, looks at specific defensive ratings to figure out what would be "best".   C almost always end up at SS in that situation due to arm.   Which tells me that the SIM favors arm over glove/range at SS.   That might tell us something.
That seems the most likely.  Might be interesting to ask in a dev. chat at some point....
7/18/2015 3:34 PM

Search Criteria

Terms of Use Customer Support Privacy Statement

© 1999-2026 WhatIfSports.com, Inc. All rights reserved. WhatIfSports is a trademark of WhatIfSports.com, Inc. SimLeague, SimMatchup and iSimNow are trademarks or registered trademarks of Electronic Arts, Inc. Used under license. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.