Service time limits should be based on years only, not days.

[bigd51]

For example:

Currently, when I set a service time limit for the DSL league to 22 years max, a player can stay eligible for the roster for 22 years and 364 days. In other words, a player can technically stay eligible on the roster until the exact day they turn 23-years-old.

22 years max should be 22 years, 0 days. Not 22 years, 364 days.

[Dutch Alexander]

When you set a maximum age this is the players "Baseball Age". Player Baseball Age is their age on June 1st in the game. (In real life July 1st is used, not sure why the game uses June 1st.)
In your example max age of 22 means that players in their age 22 season are eligible. So players who turn 22 on or before June 1st are not eligible and players who turn 22 after June 1st are eligible. So some players will actually be 23 part of the season. So by the end of the season an eligible player could be as old as 23 years and 3 month.

================================================== ======
Baseball Age (Seasonal Age)
Definition
A player's baseball age indicates how old he is as of July 1 in a given season.

The purpose of baseball age is to establish one age per season for each player, even if a player has a birthday during the season and spends parts of the campaign at two different ages. A given season will often be referred to as a player's "age-x season," with "x" being the player's baseball age.

Note: Baseball age is not an official metric, but it is widely used in baseball literature and media..
================================================== ======

[bigd51]

Originally Posted by Dutch Alexander

In your example max age of 22 means that players in their age 22 season are eligible. So players who turn 22 on or before June 1st are not eligible and players who turn 22 after June 1st are eligible.

I don't think this is how it works in-game.

I have 24 years max set for all Single-A leagues. Right now, I have at least two players on my Single-A team who turned 24 on April 13th and the other on April 18th.

If what you're saying is correct -- and forgive me if I'm mistaken about your explanation -- then they should technically be ineligible for my Single-A team b/c they both turned 24 before June/July? Because it's now October, both played the whole season in Single-A, and both are still eligible for the roster.

Originally Posted by Dutch Alexander

So some players will actually be 23 part of the season. So by the end of the season an eligible player could be as old as 23 years and 3 month.

In every scenario I've encountered, this doesn't appear to be the case either.

With my Single-A leagues set to 24 years max, as soon as a player turns 25 (25 years, 0 days), he becomes ineligible. Whether he turns 25 before June/July or after isn't taken into consideration.

This is the same issue I have w/ service time limits b/c they operate in the same manner. If I have a service time limit set to 4 years max, a player can remain eligible for the roster until their service time reaches 5 years, 0 days.

----------------------------

Thinking about it more, though, I guess it's not so much the years/days I have issues w/ but the wording of the option and the implementation.

If the game implemented the June/July "Baseball Age" rule properly, it would make minor league roster management exponentially easier. But b/c it doesn't, a player can become ineligible for a roster mid-season and the game won't let me simulate past that date until I either promote him or release him. That changes roster management strategy tenfold -- especially when it comes to signing/drafting players to use for depth/fillers for minor league teams -- for human managers and CPU-controlled teams alike.

Now, if the option read "Active Roster Player Age Maximum, on or before June/July 1st" and it were implemented properly, I could live w/ that.