Thursday, October 9, 2014

Controversy is a Brewing....

This past Monday night, Noo Shoo alerted us to some interesting dealings by our dear commish. While fully within the league settings and "legal", I still feel the need to alert the masses. Noo Shoo noticed a loophole that allows you to drop bench players at any time even after their games have been played. Ever looking for a competetive advantage, Rod noticed this and used it to his full benefit (no results, but could have) this past weekend. 

Here's a recap:






Basically, he picked up Darrin Reaves for the Sun AM game. Then after Reaves' game in which he played poorly (and got injured), he was dropped for a Sunday night player - James White. After the Sun night game, with there being no Patriot RB injuries or a breakout game from White, he was then dropped for Turbin who played in the Monday night game.

Personally, I didn't think you could drop a player once they had played in their game. However, as we have learned, you can drop them at anytime - even if their game is over - as long as they were on your bench. This can lead to "Handcuff hoarding" or "Handcuff Roulette". Basically, a scenario where people will drop a dropable player in hopes to land a stud by revolving backups into their bench. The idea being that you are hoping you can grab a backup player in case he blows up or becomes the starter for the next week. In theory, you could rotate 4 players into your one bench spot each week via this method. I repeat, with your 1 bench spot, you could add/drop 4 different guys Thurs-Mon.

First and foremost, I wanted everyone to know that this can happen and it's well within the league rules. So what does this mean? Well, it's up to us to decide. I thought the idea of waivers was to avoid the "wild wild west" of free agent pickups. However, some have stated that they like having a little craziness in their lives.

I propose a league vote:
1. Do nothing. It's within the league settings and I'm ok with it.
or
2. make a gentleman's agreement to not add players by dropping players that have already played.


Personally, I was a little peeved that this happened. Mostly, because I wasn't smart enough to notice it or figure it out.  But also because Noo Shoo and Rod knew about it, but didn't tell anyone else. It felt a little too colusiony for my tastes.

Now that everyone knows about it, I'm Ok going either way. It does add a little roster excitement, but also penalizes those that don't sit by the computer all day looking at the roster alerts.





1 comment:

  1. I was actually going to suggest we change the settings to continuous waivers next year, which would mean you have until Saturday night to make your last roster move before the Sunday games (Sunday night before a Monday night game etc.). Continuous waivers also gives everyone a fair shot at picking up a dude when an injury or arrest update comes in late Friday rather than giving the advantage to the first guy who sees the breaking news.

    That said, continuous waivers can be looked at for next year. With this info from Ned, I feel like I'm at a competitive disadvantage because I spend little time watching football and checking matchups on Sundays. I prefer option #2, but understand if we keep things the way they are since the season is in progress. I think dropping bench guys who have already played goes against part of the reason why we have the waiver rule in place.

    ReplyDelete