| Split Players - The Ohtani Rule | |
|---|---|
| Tweet Topic Started: Jan 12 2018, 03:23 PM (89 Views) | |
| john.kolodziej | Jan 12 2018, 03:23 PM Post #1 |
|
The Situation With the addition of Shohei Ohtani to the Yahoo! Fantasy Baseball system as two separate entities (both a batter and a pitcher), the team of co-commissioners have discussed what would be the best way for our league to handle one single player listed in two separate places. This will be referred to as a "split player" moving forward. The Result To set aside the reading and explanations for those who want to just "get in and get out," a split player is going to be handled as two separate entities altogether. If/when a split player is drafted, just as with any drafted player, you will have to specify the position of the player you are choosing to draft so the allocation in the Yahoo! system can be done correctly. This will require no additional monitoring as this is all operating within the current league functionality parameters. If there is ever a time where our league becomes one that has a split player as a single entity, the following process will happen. 1) If the split player is owned by only 1 team, that team will be awarded with the player. 2) If the split player is owned by 2 teams, they will be given ample time to work out a trade. ^ 3) If the split player is owned by 2 teams and they are unable to work out a trade * then the player will be awarded to the team who owns the "most valuable" version of the split player. ** In this occurrence the team who loses their split player will be awarded a supplemental draft pick between the first and second rounds. *** ^This trade can involve draft picks, players, etc. This trading process will be overseen by the league co-commissioners. The base trade period will be 1-week to ensure this process gets handled in a timely manner and not dragged out. If it requires more time and the two parties are actively working together on a trade, the co-commissioners reserve the right to extend this trade-time as needed. *due to (a) one or both teams not making an effort or communicating through a trade, (b) openly deciding to not make a trade, or (c) reaching the allotted time frame with no trade agreement reached **In this instance "most valuable" will be determined by the co-commissioner team. The basis of this will be determined on the players value compared to the whole league player pool and not the player's value to his specific team ***If there are two or more split players that require this step the co-commissioner team will determine the supplemental draft pick order either based on "value" or randomly. The Process There were a few options that were discussed below. Option 1 - Whoever drafts/owns a split player will own both entities of the player. They must be drafted, added, dropped, traded, etc. together at all times. This would treat all entities of the player as a single player in all transacting/ownership functions. If our league is ever in a system that has split players as a single player it would free up a roster spot for the owning team. The split player will occupy 2 roster spots instead of only 1. If the split player goes on the DL then the team would functionally lose 2 players in one blow. If the split player is not valuable at one of the entities the owning team would be forced to keep this entity as long as they own the other entity. If the split player is not valuable at one of the entities this would alter the trade/ownership "value" of the other entity because they must be owned together. This would require minor monitoring to ensure that the two player entities are always owned/moved together. Option 2 - Each version of a split player is treated as its own entity. This changes nothing within the system and league functionalities. This requires no additional monitoring as each version of the player is treated as a single player. If a future league system provides a combined version of the player, guidelines will need to be established. **This has been established and outlined above** Option 3 - A split player is treated as a single ownable entity with only one owned at a time. This would require a transaction any time the owner wants to switch between each version of the split player, which would have a negative impact. Any ownership/transaction of the player would include both versions of the split player. This would require minor monitoring to ensure that only one version of the player is owned at a time. After conversation among the co-commissioner team, it has been decided that Option 2 was the best way to go for our league. This will allow the league to maintain the concept of operating entirely within the system rules with no additional monitoring. If the system should change at some point to allow for a split player to turn into a combined player we have determined a procedure so the handling of this situation is predetermined. |
![]() |
|
| 1 user reading this topic (1 Guest and 0 Anonymous) | |
| « Previous Topic · Rosters · Next Topic » |






4:33 AM Jul 11