Quote:
Originally Posted by Lukas Berger
This is not ideal, but it's also a result of a brutal Rule 5 crunch the Rays are going to be facing this year.
Real life and in-game, they're going to have to trade guys away at a discount or leave some good players exposed.
Unfortunately, not really much way around that or much of a good way for the AI to handle it.
The 2020 Rays are basically a textbook example of exactly why the Rule 5 draft was established in the first place 
Anyway, the problem at this point is not whether the AI in some circumstances leave guys exposed that it shouldn't, it's pretty clear that in some circumstances it does. What we need to find out is why it does it.
At this point, what we need to make any progress is the actual save game files from the day before or the day of the Rule 5 draft (but before the draft is started) where there's a clear case of a guy being exposed who in no way should be exposed (not Brujan or another Rays prospect in 2020, since that's just a no win situation, like I mentioned). |
Things I’ve have noticed is that
1. AI would rather have a low rated RP on its 40 rather than a better rated position player. (Maybe it have to do with Pitcher vs Batter?)
2. Potential OVR does not seem to outweigh or be equal to current OVR in this decision making.
A 40/40 player would get picked over a 25/50 player. That could be argued considering you would want MLB ready players ready to be called up from AAA but I also feel that potential should have way more weight for the sake of protecting some players.
These issues would be glaring if you take stats almost out of the equation of figuring out current OVR. Which is what is happening here IMO.
Sent from my iPhone using Tapatalk