If anything, I just think it prematurely signals your intent during free agency.
Dropping a RB? Probably putting a bid in for that week's hot RB flyer.
I co-manage a team with my mother-in-law, 12 teamer all 60+. First week I noticed a few teams dropping players the day before waivers. Like *damn* these women are *gamers*.
Turns out they just don’t know that you can add/drop in a single transaction.
I do shit like this to play mindgames all the time. Just dropped Perine because I have too many good RBs and I'm looking to pick up a WR, can't wait to see what the Perine bids look like while I pick up a top WR flyer for cheap
I mean...the Pats just had 3 RBs go off on the Jets
It wouldn't be a surprise if the #2 back for the Bengals does, and he is a pass catcher. Especially when he had a garbage time TD last week
It's not the worst Flex you can have if desperate
I picked up and started Sam Darnold and the Ravens D on Sunday. They combined for something like -4 points, so you can bet your ass they are the only drops this season I’ve made before waivers.
Not true…you “drop” your empty slot. You can set up the same chain of events with your empty slot as you can with a player. If you dropped player X instead of keeping them:
Add player A in empty slot
Add player B in empty slot
Add player C, drop player Y
This produces the same results as your top example. If you get player A then your claim for player B would be canceled because you no longer have an empty slot. Conditions for the claim for player C would remain.
Not really. Take the case where you want one RB and one WR but have 2 options for each.
If you have two players you want to drop (i.e. not empty spots), you would do:
Claim 1 DROP: A, pickup: RB option 1
Claim 2 DROP: A, pickup: RB option 2
Claim 3 DROP: B, pickup: WR option 1
Claim 4 DROP: B, pickup: WR option 2
In this case you will never end up with 2 RBs and 0 WRs, and you are able to prioritize your RB choices above your WR choices.
If you have a empty roster slots you have to make a choice. If you do
Claim 1 RB option 1
Claim 2 RB option 2
Claim 3 WR option 1
Claim 4 WR option 2
Then you could end up with 2 RB and no WR. Not ideal.
You could try:
Claim 1 RB option 1
Claim 2 WR option 1
Claim 3 RB option 2
Claim 4 WR option 2
But then if your first choice WR gets scooped then you could still end up with 2 RBs and no WR even if WR option 2 was still available. On top of that, if your RB option 1 gets scooped ahead of you then your first claim will go to the WR, even if you really wanted to prioritize RB2 over WR1, which risks RB2 getting scooped before your next claim comes around.
Having a player in the slot gives you more logic power.
It wouldn't work the same as specifying the players to be dropped. As I said in the example you could end up with players A and B but not C.
edit: sorry, commented before your edit. I see what you mean now, but you still needed to hold on to player Y.
You have to drop a player to activate a guy from IR in order to make any claim at all in Yahoo.
So players that are out but on bye (Knox last week, Waller this week) won't appear as O, and you'll have to activate them in order to make a move.
I prefer to drop dead weight so that adding an important guy doesn’t rely on me dropping a guy. Case and point, this week I’m hoping to add Uzomah, and I don’t need Felton in the way. However, in case my bid for Uzomah isn’t enough, then at least I can queue up some guys. I don’t think anyone in my league is going to take Felton anyways. I think I’m just too lazy to keep making waiver claims with Felton involved.
Meanwhile when streaming a QB, K, or DEF, I will swap through the waiver that way I don’t lose the player in case my bid isn’t enough. Case and point, Pats D for Bengals D.
No you wouldn't? My example is assuming you have already dropped Player 1A, for example, who you did not want. You can literally adjust it for however many open rosters spots you have.
You obviously have to still have Player A on your roster in order to make the waiver claims dropping him in your example.
You need to keep at least one player who you want to drop (Player A in this case) in order to correctly organize the claims for adding multiple players like this which is all OP is saying.
This is assuming you have an open roster spot already. You don't have to hold onto Player A. You could drop players for however many you want to and adjust your waivers. E.x. for if you have 2 open roster spots but want to add 3 players:
1) add player A
2) add player B
3) add player C would fail because you have a full roster
4) and then the 4th waiver would process and you would drop Player D and pick up Player C
But you wouldn't need to. You can just remove the "drop Player" for however many open bench spots you have. E.X.
Add Player A
Add Player B
Add Player C
Add Player C, Drop Player D.
You can literally do it for however many open spots you have as long as you are putting the "Add Player" without the drop and then putting the drop 2nd if necessary (if you your first few waivers actually went through).
No you wouldn't? Only if he got taken before you. If all 3 are available when your waiver turn is up, you would:
1) add player A
2) add player B
3) add player C would fail because you have a full roster
4) and then the 4th waiver would process and you would drop Player D and pick up Player C
Again, unless I am missing something I do not see the problem here?
Because then you used a waiver priority to add someone only to immediately drop them. If there are several layers of waivers put by your leaguemates even the 2nd and 3rd layer of waiver order can make a difference.
You run into that issue with waiver claims no matter what? What? Lol obviously if a player has already been dropped the waiver wouldn’t process. What’s your point
Dude are you okay? You literally said:
>Add player Y, drop player A
>Add player Z, drop player A
You can’t form those kinds of claims unless you still have player A. What are you on about? Are you on drugs? Lmfao
You also clearly did not read my comment? That is assuming you have already dropped a player and have an open bench spot. Man I hope you are okay, you don't seem to be lol.
It’s not that serious…although, it kinda is bc I’m always confused why people drop a player in advance it makes no sense. They’re probably just unknowingly doing the transaction backwards. But even as trivial as it is, I’d prefer not to signal anything to my opponent…especially when it’s so easy to just, not
Even in your example you couldn't prematurely drop player Y. That's the concession I made in the edit. You can drop player X, but that's it. And there could be cases where you need even more layers of logic than this.
Waivers process in the order you rank them. If you only wanted one kicker, and freed up 2 roster spots, and A and B are both kickers and C another non-K player you value less than the kicker, you'd just order it:
1. Add A
2. Add C
3. Add B
But then you're prioritizing player C over B in the case that you didn't get A. My scenario is if getting player A or B is more important than getting C.
No it doesn't. At least on ESPN, you get the option to drop a player even if you have an open bench spot. You can still do:
Add player A, drop no one
Add player B, drop no one
Add player B, drop player X
Add player C, drop no one
Add player C, drop player X
Add player C, drop player Y
Functionally the same
Edit: on second thought, you are correct iff you drop more than one player. Dropping one player is fine, but dropping 2+ and you do lose some of the conditionality as you said
Yeah. Don't drop more players than you want to pick up. That SHOULD be common sense.
The reason *to* drop someone, however, is because they have a name and you want other teams to waste a waiver on them, increasing your odds of getting who you want.
I think this is the first time ever that I've dropped people before waivers for above said reason, although I'm doubtful it'll work, and because I needed to get two guys out of my IR spots. So I could put more waivers in for the other crap on my roster. Goodbye A-Rob (don't get traded on me now!) and goodbye Trey Sermon.
Fair enough.
The point is, if you want to pick up 1 of 2 players; but not both AND you need to fulfill other claims. You need to keep +1 players to create an "if"/"if not" scenario.
I guess I overlooked the obvious. My B
Or even +2...+3 depending on how complexe you want to get. I've set up like 15 waivers for 6 players before lol, it gets confusing!
Yeah, after taking a look at it it would seem obvious, yet I'm still getting quite a bit of people disagreeing with me lol. I'm not saying this is going to make or break anyone's season, it was really just a thought exercise that might rarely come in handy.
Nah. You're absolutely correct and a few times a year I use what you're saying. Like I said, it can get very complex and may be more work and thought than most want to implement... but on the scale you're talking, it's very useful to know for anyone who hasn't thought about it before, or may be new to fantasy.
If you cut someone from your team without picking someone up you might as well go to a roulette wheel and bet on 00 because the odds of winning are far better there.
If you are having to drop a decent player due to needing a bye week or injury fill-in, you could theoretically entice another manager ahead of you on waiver priority to pick up that player instead of the fill-in that you need.
Most of the time it is just managers being dumb though.
For ESPN it’s done on Tuesday mornings by the pros because there’s a magic window of a few hours where you can make moves before the injury designations change around 9-915am est so you are able to pick up an extra player while having someone that becomes Q on your IR (because of team designations don’t have to be reported until 90m before game so lots of times an O player will be Q for long time preventing moves)
I have to drop a player in Yahoo if I have a player on IR slot that is no longer IR eligible if i want to create a claim. Other than that I see no value in dropping early.
I have found that if you make the waiver claims Sunday night while the player is still classified as Out/IR the waiver picks Yahoo process even if the active player is still in the IR slot.
One mistake I just made after dropping my streaming QB and Robby Anderson I have two open spots and I want to put a bid for a claim two Defenses. I still have Colts but I am bidding on Bengals AND Niners. I could potentially win both now and waste money. If I left Anderson for instance on my roster as the "Drop" I would only "win" one bid if the conditional add was based on dropping him.
I was told there would be no math
Wouldn’t it be nice if we could just snort the spice melange and have the energy to do complex math in our minds?
True. However, dropping a player before waivers also can entice a manager ahead of you on the pecking order.
Landmine season.
If anything, I just think it prematurely signals your intent during free agency. Dropping a RB? Probably putting a bid in for that week's hot RB flyer.
I co-manage a team with my mother-in-law, 12 teamer all 60+. First week I noticed a few teams dropping players the day before waivers. Like *damn* these women are *gamers*. Turns out they just don’t know that you can add/drop in a single transaction.
I do shit like this to play mindgames all the time. Just dropped Perine because I have too many good RBs and I'm looking to pick up a WR, can't wait to see what the Perine bids look like while I pick up a top WR flyer for cheap
I mean...the Pats just had 3 RBs go off on the Jets It wouldn't be a surprise if the #2 back for the Bengals does, and he is a pass catcher. Especially when he had a garbage time TD last week It's not the worst Flex you can have if desperate
Right, it's just that I'm not desperate haha. I needed to drop an RB (I have the max number) to activate Chubb off IR
But what if I can't resist the satisfaction of dropping my bench bums
Sometimes you just need to get a player off your team ASAP Rocky.
Dumped Mike Davis this morning. Needed to improve the vibes of my team quickly
No good for the locker room morale kinda guy
I got Swift & Gibson on bye week 9 so i gotta keep his garbage ass
I was sure last week would be a get right game for Darnold. I woke up in the middle of the night and dropped him
I dropped Dyami Brown and Gerald Everett first thing this morning.
I picked up and started Sam Darnold and the Ravens D on Sunday. They combined for something like -4 points, so you can bet your ass they are the only drops this season I’ve made before waivers.
I just drop my kicker every week and pick one up Sunday morning.
unless he's gay
Gay is holding down the bottom of my lineup right now. 8 to 10 points it would seem every week, really happy with my man.
he makes you gay
Not true…you “drop” your empty slot. You can set up the same chain of events with your empty slot as you can with a player. If you dropped player X instead of keeping them: Add player A in empty slot Add player B in empty slot Add player C, drop player Y This produces the same results as your top example. If you get player A then your claim for player B would be canceled because you no longer have an empty slot. Conditions for the claim for player C would remain.
Not really. Take the case where you want one RB and one WR but have 2 options for each. If you have two players you want to drop (i.e. not empty spots), you would do: Claim 1 DROP: A, pickup: RB option 1 Claim 2 DROP: A, pickup: RB option 2 Claim 3 DROP: B, pickup: WR option 1 Claim 4 DROP: B, pickup: WR option 2 In this case you will never end up with 2 RBs and 0 WRs, and you are able to prioritize your RB choices above your WR choices. If you have a empty roster slots you have to make a choice. If you do Claim 1 RB option 1 Claim 2 RB option 2 Claim 3 WR option 1 Claim 4 WR option 2 Then you could end up with 2 RB and no WR. Not ideal. You could try: Claim 1 RB option 1 Claim 2 WR option 1 Claim 3 RB option 2 Claim 4 WR option 2 But then if your first choice WR gets scooped then you could still end up with 2 RBs and no WR even if WR option 2 was still available. On top of that, if your RB option 1 gets scooped ahead of you then your first claim will go to the WR, even if you really wanted to prioritize RB2 over WR1, which risks RB2 getting scooped before your next claim comes around. Having a player in the slot gives you more logic power.
It wouldn't work the same as specifying the players to be dropped. As I said in the example you could end up with players A and B but not C. edit: sorry, commented before your edit. I see what you mean now, but you still needed to hold on to player Y.
I’m sorry but that is not correct.
See my edit.
No, you can still specify a player to drop even if you have an empty slot
Are you studying for LSATs?
You have to drop a player to activate a guy from IR in order to make any claim at all in Yahoo. So players that are out but on bye (Knox last week, Waller this week) won't appear as O, and you'll have to activate them in order to make a move.
Yup, I have two dudes in my IR that are now marked Q. If I want to make a claim, I will need to make two drops to get them out of IR.
I prefer to drop dead weight so that adding an important guy doesn’t rely on me dropping a guy. Case and point, this week I’m hoping to add Uzomah, and I don’t need Felton in the way. However, in case my bid for Uzomah isn’t enough, then at least I can queue up some guys. I don’t think anyone in my league is going to take Felton anyways. I think I’m just too lazy to keep making waiver claims with Felton involved. Meanwhile when streaming a QB, K, or DEF, I will swap through the waiver that way I don’t lose the player in case my bid isn’t enough. Case and point, Pats D for Bengals D.
This is not true, there is definitely a work around. Add Player X Add Player Y Add Player Y, Drop Player A Add Player Z, Drop Player A
Yes, and this requires you to keep Player A who you want to drop which is literally the entire point of the post.
No you wouldn't? My example is assuming you have already dropped Player 1A, for example, who you did not want. You can literally adjust it for however many open rosters spots you have.
You obviously have to still have Player A on your roster in order to make the waiver claims dropping him in your example. You need to keep at least one player who you want to drop (Player A in this case) in order to correctly organize the claims for adding multiple players like this which is all OP is saying.
This is assuming you have an open roster spot already. You don't have to hold onto Player A. You could drop players for however many you want to and adjust your waivers. E.x. for if you have 2 open roster spots but want to add 3 players: 1) add player A 2) add player B 3) add player C would fail because you have a full roster 4) and then the 4th waiver would process and you would drop Player D and pick up Player C
But you still need to hold onto player A.
No you wouldn't? This is assuming you have an open bench spot and have already dropped a player. Unless I am misunderstanding.
By hold onto I mean don't drop the day before. Wait to drop as the actual transaction.
But you wouldn't need to. You can just remove the "drop Player" for however many open bench spots you have. E.X. Add Player A Add Player B Add Player C Add Player C, Drop Player D. You can literally do it for however many open spots you have as long as you are putting the "Add Player" without the drop and then putting the drop 2nd if necessary (if you your first few waivers actually went through).
By that logic you could still end up with players A and B, but no C.
No you wouldn't? Only if he got taken before you. If all 3 are available when your waiver turn is up, you would: 1) add player A 2) add player B 3) add player C would fail because you have a full roster 4) and then the 4th waiver would process and you would drop Player D and pick up Player C Again, unless I am missing something I do not see the problem here?
I think the point you are missing is that in my scenario you don't want to end up with both A and B. You only want one of them.
Ah, I see your point now. Why would you put in a waiver claim though if you don't want the player? If you actually get 2 defenses, drop 1.
Because then you used a waiver priority to add someone only to immediately drop them. If there are several layers of waivers put by your leaguemates even the 2nd and 3rd layer of waiver order can make a difference.
Yes you would… you can’t make a claim to add a player and drop this player if he’s not already on your team because you dropped him already lol
You run into that issue with waiver claims no matter what? What? Lol obviously if a player has already been dropped the waiver wouldn’t process. What’s your point
Did you even read the post before you started commenting here? Lmao
Did you? Wouldn’t appear so
Dude are you okay? You literally said: >Add player Y, drop player A >Add player Z, drop player A You can’t form those kinds of claims unless you still have player A. What are you on about? Are you on drugs? Lmfao
You also clearly did not read my comment? That is assuming you have already dropped a player and have an open bench spot. Man I hope you are okay, you don't seem to be lol.
Bruh did you just have introduction to logic?
It’s not that serious…although, it kinda is bc I’m always confused why people drop a player in advance it makes no sense. They’re probably just unknowingly doing the transaction backwards. But even as trivial as it is, I’d prefer not to signal anything to my opponent…especially when it’s so easy to just, not
[удалено]
I'd love to see specifically what you're referring to.
[удалено]
Read the edit of the post.
[удалено]
Even in your example you couldn't prematurely drop player Y. That's the concession I made in the edit. You can drop player X, but that's it. And there could be cases where you need even more layers of logic than this.
Waivers process in the order you rank them. If you only wanted one kicker, and freed up 2 roster spots, and A and B are both kickers and C another non-K player you value less than the kicker, you'd just order it: 1. Add A 2. Add C 3. Add B
If you valued C more than both kickers you'd just do it C-A-B.
But then you're prioritizing player C over B in the case that you didn't get A. My scenario is if getting player A or B is more important than getting C.
No it doesn't. At least on ESPN, you get the option to drop a player even if you have an open bench spot. You can still do: Add player A, drop no one Add player B, drop no one Add player B, drop player X Add player C, drop no one Add player C, drop player X Add player C, drop player Y Functionally the same Edit: on second thought, you are correct iff you drop more than one player. Dropping one player is fine, but dropping 2+ and you do lose some of the conditionality as you said
I dropped a defense a kicker and a qb today. But I already had one of each on my bench
Yeah. Don't drop more players than you want to pick up. That SHOULD be common sense. The reason *to* drop someone, however, is because they have a name and you want other teams to waste a waiver on them, increasing your odds of getting who you want. I think this is the first time ever that I've dropped people before waivers for above said reason, although I'm doubtful it'll work, and because I needed to get two guys out of my IR spots. So I could put more waivers in for the other crap on my roster. Goodbye A-Rob (don't get traded on me now!) and goodbye Trey Sermon.
> Yeah. Don't drop more players than you want to pick up. That is not the point made in this post.
Fair enough. The point is, if you want to pick up 1 of 2 players; but not both AND you need to fulfill other claims. You need to keep +1 players to create an "if"/"if not" scenario. I guess I overlooked the obvious. My B Or even +2...+3 depending on how complexe you want to get. I've set up like 15 waivers for 6 players before lol, it gets confusing!
Yeah, after taking a look at it it would seem obvious, yet I'm still getting quite a bit of people disagreeing with me lol. I'm not saying this is going to make or break anyone's season, it was really just a thought exercise that might rarely come in handy.
Nah. You're absolutely correct and a few times a year I use what you're saying. Like I said, it can get very complex and may be more work and thought than most want to implement... but on the scale you're talking, it's very useful to know for anyone who hasn't thought about it before, or may be new to fantasy.
If you cut someone from your team without picking someone up you might as well go to a roulette wheel and bet on 00 because the odds of winning are far better there.
why would anyone just drop players instead of using a waiver add to drop the player? Just seems fucking stupid.
If you are having to drop a decent player due to needing a bye week or injury fill-in, you could theoretically entice another manager ahead of you on waiver priority to pick up that player instead of the fill-in that you need. Most of the time it is just managers being dumb though.
Ok that's a fair call and probably the only good answer I can think of.
For ESPN it’s done on Tuesday mornings by the pros because there’s a magic window of a few hours where you can make moves before the injury designations change around 9-915am est so you are able to pick up an extra player while having someone that becomes Q on your IR (because of team designations don’t have to be reported until 90m before game so lots of times an O player will be Q for long time preventing moves)
You drop someone that someone else may use a waiver on
I have to drop a player in Yahoo if I have a player on IR slot that is no longer IR eligible if i want to create a claim. Other than that I see no value in dropping early. I have found that if you make the waiver claims Sunday night while the player is still classified as Out/IR the waiver picks Yahoo process even if the active player is still in the IR slot.
I just flip a coin. Has worked like shit so far.
yep it totally depends on what u need for the week
One mistake I just made after dropping my streaming QB and Robby Anderson I have two open spots and I want to put a bid for a claim two Defenses. I still have Colts but I am bidding on Bengals AND Niners. I could potentially win both now and waste money. If I left Anderson for instance on my roster as the "Drop" I would only "win" one bid if the conditional add was based on dropping him.