I'm playing in a league that prevents cuts after game start, places all free agents on waivers after game start, and processes game-start waivers on Wednesday.
What time, if any, do players on bye lock?
Is this a change from previous years' leagues that had those same settings in place? If so, what was the rationale for the change?
Players on bye week do not lock. They can be added/cut at any time. This has always been our behavior. The rationale is that no one can gain a "true" competitive advantage by making a transaction to that player because their game isn't playing.
"Players on bye week do not lock. They can be added/cut at any time."
This conflicts with what fleaflounder said.
My league settings say that players go on waivers when they are dropped and when their game starts.
Players who were on a bye this past week are all on waivers right now, even though they were not cut and had no games. Is this how it is supposed to work?
For example all Bengals players were available to be added last night, and now they must be claimed. Why?
From your help site: "There are two ways a player can end up on waivers: a player is placed on waivers when that player is dropped from an owner's roster, becoming a free agent; a free agent player is placed on waivers when that player's real NFL game begins. Both of these are optional."
I have scores of players who meet neither condition yet are on waivers.
Because after scores finalize, they lock for the week with the entire player pool form finalization until waivers run in your league -- this has always been the behavior.
Bryan_BMon 10/17/11 7:07 PM
I'm playing in a league that prevents cuts after game start, places all free agents on waivers after game start, and processes game-start waivers on Wednesday.
What time, if any, do players on bye lock?
Is this a change from previous years' leagues that had those same settings in place? If so, what was the rationale for the change?
FleaMod AdminMon 10/17/11 8:03 PM
Players on bye week do not lock. They can be added/cut at any time. This has always been our behavior. The rationale is that no one can gain a "true" competitive advantage by making a transaction to that player because their game isn't playing.
rangerdaveMon 10/17/11 8:12 PM
It's actually helpful when you are faced with an unexpected inactive for a late game as it gives you more player options for release or IR.
McBainTue 10/25/11 10:32 AM
"Players on bye week do not lock. They can be added/cut at any time."
This conflicts with what fleaflounder said.
My league settings say that players go on waivers when they are dropped and when their game starts.
Players who were on a bye this past week are all on waivers right now, even though they were not cut and had no games. Is this how it is supposed to work?
For example all Bengals players were available to be added last night, and now they must be claimed. Why?
McBainTue 10/25/11 10:40 AM
From your help site: "There are two ways a player can end up on waivers: a player is placed on waivers when that player is dropped from an owner's roster, becoming a free agent; a free agent player is placed on waivers when that player's real NFL game begins. Both of these are optional."
I have scores of players who meet neither condition yet are on waivers.
FleaMod AdminTue 10/25/11 11:00 AM
We can change the wording for you in the future to include players from the pool following the finalization of games until waivers run.
FleaMod AdminTue 10/25/11 10:59 AM
Because after scores finalize, they lock for the week with the entire player pool form finalization until waivers run in your league -- this has always been the behavior.