Demoting spring training invitees

[beorn]

I am glad to see that the game allows you to invite players who are not on the 40 man roster to spring training.

However, I am surprised to find out that such an invitee must pass through waivers to go back to the minors, if they have no options left.

This does not seem to make sense, since a player in the same situation with options remaining does not burn an option being sent to the minors.

Is this the way it is supposed to work?

Not sure if this is
a) a real life rule I am not aware of,
b) not realistic, but working as designed, or
c) a bug

[Le Grande Orange]

Originally Posted by beorn

I am glad to see that the game allows you to invite players who are not on the 40 man roster to spring training.

That shouldn't happen, at least not according to real-life rules, unless the player is on the 40-man roster and you are trying to remove him from it.

Originally Posted by beorn

This does not seem to make sense, since a player in the same situation with options remaining does not burn an option being sent to the minors.

That's not quite correct. A player on the 40-man roster but in the minors will use up an option if he's still in the minors when the regular season rolls around. (In real life the player would have to spend 20 days in the minors during the regular season to use up an option; in OOTP it's just one day.)

[beorn]

Originally Posted by Le Grande Orange

That's not quite correct. A player on the 40-man roster but in the minors will use up an option if he's still in the minors when the regular season rolls around. (In real life the player would have to spend 20 days in the minors during the regular season to use up an option; in OOTP it's just one day.)

But this player is NOT on the 40 man roster. He's a spring training invitee, not listed on the 40 man list, and having the # after his name on the transactions screen.

[Markus Heinsohn]

Yes, this issue was discovered today by the beta team as well, unfortunately too late to be fixed for patch #3. So, I'll have to fix it for patch #4.

There has to be some sort of workaround though...