petrel
07-12-2006, 07:35 PM
Someone in a thread somewhere pointed out a list of baseball transaction terminology and what these terms mean. The game doesn't have a 40-man roster or the Rule V Draft (yet), but I would like to suggest that "Veteran Players" be added for future editions.
"Veteran Players"
Any player who has been in the major leagues for five full seasons may not be assigned to a minor-league team without his written consent. This sometimes puts the team in a bad position, because a player with five years has every right to say, "I don't want to go to New Orleans. You can either release me and keep paying me, or keep me on the major league roster and keep paying. Your choice."
Also, a player with five years of service time who is traded in the middle of a multi-year contract may demand another trade prior to the start of the season following the one in which he was traded.
Any player with at least 10 years of Major League service, the last five of which have been with one Major League Club, may not be traded to another Major League Club without his written consent. This is commonly known as "the five-and-ten rule."
(From the website.)
The tough question is "how hard would this be to code?"
I don't see that the first and third paragraphs would be hard to do. The "Vitals" section already calcuates service time, and service time is a "sortable stat". It would be a simple "if-then program".
(Owner wants to move player to minor leagues)
If (player has less than five years service time)
THEN (allow move)
ELSE IF (player gives written permission)
THEN 1. allow move
2. show pop up "Player gives permission! Lucky you!"
ELSE 1. block move
2. show pop up "You must keep this player on the major league
roster or release him -- you don't have permission".
The third paragraph shouldn't be bad either. When proposing a trade, before the computer approves it, it looks at the service time of all players involved. If a player has service time > 10 years, it determines for each player if the other team is an "acceptable team". If it is, the trade goes forward, else
there is a popup-window.
("This trade was blocked by <name of player>. He has 10 years of service and he refuses the trade.")
The hard part is that the player also has to have five years of service time with the same club. Another sortable stat would have to be created, "time with current club". (I think fans would like that stat -- it would be interesting to know who leads the league in time with a club.)
The hard part would be paragraph two. How does a player "demand another trade"? How does that work out?
Even so, I think the game would be more interesting if the Veteran Players rules were implemented. No one could hide veterans in the minors, and it would make for more interesting roster management.
--Pet
"Veteran Players"
Any player who has been in the major leagues for five full seasons may not be assigned to a minor-league team without his written consent. This sometimes puts the team in a bad position, because a player with five years has every right to say, "I don't want to go to New Orleans. You can either release me and keep paying me, or keep me on the major league roster and keep paying. Your choice."
Also, a player with five years of service time who is traded in the middle of a multi-year contract may demand another trade prior to the start of the season following the one in which he was traded.
Any player with at least 10 years of Major League service, the last five of which have been with one Major League Club, may not be traded to another Major League Club without his written consent. This is commonly known as "the five-and-ten rule."
(From the website.)
The tough question is "how hard would this be to code?"
I don't see that the first and third paragraphs would be hard to do. The "Vitals" section already calcuates service time, and service time is a "sortable stat". It would be a simple "if-then program".
(Owner wants to move player to minor leagues)
If (player has less than five years service time)
THEN (allow move)
ELSE IF (player gives written permission)
THEN 1. allow move
2. show pop up "Player gives permission! Lucky you!"
ELSE 1. block move
2. show pop up "You must keep this player on the major league
roster or release him -- you don't have permission".
The third paragraph shouldn't be bad either. When proposing a trade, before the computer approves it, it looks at the service time of all players involved. If a player has service time > 10 years, it determines for each player if the other team is an "acceptable team". If it is, the trade goes forward, else
there is a popup-window.
("This trade was blocked by <name of player>. He has 10 years of service and he refuses the trade.")
The hard part is that the player also has to have five years of service time with the same club. Another sortable stat would have to be created, "time with current club". (I think fans would like that stat -- it would be interesting to know who leads the league in time with a club.)
The hard part would be paragraph two. How does a player "demand another trade"? How does that work out?
Even so, I think the game would be more interesting if the Veteran Players rules were implemented. No one could hide veterans in the minors, and it would make for more interesting roster management.
--Pet