Players released after signing for millions of $

[1991Cubs]

Not happening to star players but middle of the road relief pitchers are signing then immediately placed on irrevocable waivers. If no team claims them, they are released after 7 days. Why pay a guy millions of dollars if he is just going to be released?

[Mike D]

Don't worry, he will be signed by another team in the Fall for a 7 million dollar deal, thus being paid twice.

[turtle4499]

Originally Posted by 1991Cubs

Not happening to star players but middle of the road relief pitchers are signing then immediately placed on irrevocable waivers. If no team claims them, they are released after 7 days. Why pay a guy millions of dollars if he is just going to be released?

Disable the minor league in season option limit. It is never used well by the computer.

[1991Cubs]

I discovered these seem to be veteran relieve pitchers that sign contracts but are not good enough to make the 40-man-roster. They end up refusing their minor league assignment, so their new teams release them if they clear waivers. Dylan Floro's contract was what I posted in the attachment. I always thought that guy was a clown in real life. The game confirms that for me. Next Nationals game I am at I am going to heckle that clown for refusing his minor league assignment in my baseball universe.

[monkeyman576]

Inflation! $1M is not much in 2025.

[jcard]

It really is a little late in the day for the game to still have such prominent flaws. I saw a post where the user held an expansion draft and the reigning MVP was left unprotected (good intangibles, popularity, etc., as well). Examples like the one being discussed here or the sign / release transaction cyclotron point to a primitive roster management AI, resulting in these edge cases where individual transactions might be defensible in isolation but when considered longitudinally.

[ayaghmour2]

Originally Posted by jcard

It really is a little late in the day for the game to still have such prominent flaws. I saw a post where the user held an expansion draft and the reigning MVP was left unprotected (good intangibles, popularity, etc., as well). Examples like the one being discussed here or the sign / release transaction cyclotron point to a primitive roster management AI, resulting in these edge cases where individual transactions might be defensible in isolation but when considered longitudinally.

I have to ask, and please don't take this the wrong way, do you use a thesaurus when making your posts? Seems like there are always a lot of big words, but something feels missing.

Cyclotron? That's a particle accelerator. Do you mean the sign and release transaction cycle?

And the last sentence. "but when considered longitudinally." Shouldn't there be more words after? What should we consider in the long-term? Should it be that the edge cases make sense (there's always someone that needs to be cut) but when looking at the big picture, teams should not be cycling between the same few players. It's quite unclear exactly what you're getting to

It's just interesting seeing all these uncommon phrases in a few sentences: prominent, cyclotron, primitive, defensible, isolation, longitudinal. Happens on a few other comments too. For what it's worth, this may cause confusion with others as it seems to take away from some of the good points you make

[bailey]

Longitudinally speaking, there is no $ in AI.