[FF]: Season Long Waiver Discussion

[EricH]

It's time for some planning ahead...

For those competing in the Season Long Fantasy FIRST league, there has been a discussion of modifying the procedure for picking up a newly added team from first-come-first-serve to a waiver system. With clearance from Ed to try it out, there are still a few questions to answer. I'll give my answer; anybody who has another answer, speak up.

(For an explanation of how this works, see this post.)

1) Which teams are subject to the waiver process?
--My thought is, if the team is in the pool of available teams at the end of a draft (or, more likely, an hour after the draft), they should not be included in the waiver process unless they are picked and dropped. All teams added to the pool, even by being dropped, after the draft ends would be subject to waivers.

2) How long should a new team be on waivers?
--I think I speak for both Kevin (Vikesrock) and myself when I say that we're thinking no more than a day or two from the point where the team's presence is known.

3) What about the waiver priority list? What criteria should be used to order that?
--The higher you are on the priority list, the quicker you can pick up a team. What we're thinking is use the most current scoring (AKA last year's until we get scores), in reverse order, with people who don't have a score in random order at the top of the list. I'm personally thinking that number of missing teams should also factor in, moving people who are missing teams higher on the list.

4) How to manage the list/claims?
--I'm thinking a separate thread to maintain the list and for claims to be posted.

5) Should players post teams that they will drop?


As this is a new idea for the league, input is welcomed. If you have a different question, bring it up and let the discussion begin.

[Chris is me]

1. Any team that is dropped or added to the event after the draft immediately goes to the Waiver list. (This is concise and accounts for trades and drops from the Free list too)

2. What's going to happen more often than not I think is a team will be on waivers, the person up next won't pick them up because they aren't active or whatever, and then they'll fall to the free list. All that would accomplish is pushing the "speed rush" for good teams back a day. I think they should stay on waivers until the entire list has said "pass" or someone has picked them up.

3. Only problem with "lowest first" is that it will be "barely active people first".

[Vikesrock]

Chris,

The way a waiver wire usually works is that anyone that wants to post a claim for a team during the time they are on waivers may do so. So if, for example, 1114 adds to Midwest and goes on waivers, anyone can post a claim in the 24 hours after their add is announced in the waiver thread.

The person that is highest on the priority list (or in this example, the person highest on the priority list in each tier) that puts in a claim would be awarded the team. Additions of very good teams to an event may result in a cascade of claims moving up the priority list as less active (or less ridiculous ) players check in.

[Chris is me]

Oh, that's a lot more reasonable then. Thanks for the clarification.

[Barry Bonzack]

I like the idea, but I would prefer the waiver period be by the end of Sunday, that way everyone has at least the weekend to get on and look. I don't think FF should be a daily maintenance game after drafting ends.

My proposition time frame to claim a team: all teams that go on the waiver list will be decided by 11:59PM Sunday, but no less than 48 hours.

For example: Team 67 joins the St. Louis Regional on a Wednesday, players can make claims up to 11:59 PM Sunday.

Example 2: Team 1625 is added to the Hawaii regional on a Saturday, Claims can be made all the way until the following Sunday (8 days).

[EricH]

I like that for during the drafting and build season. Cut it down to 48 hours or the lock of that event's drafts, whichever comes first, during competition season as there will be far fewer adds/drops during that time.

Oh, and I'd say that the waiver period starts on discovery that the team has added (i.e., 330 registers for San Diego on Monday, and they are discovered as attending on Saturday as somebody goes on a check, they'll be on waivers until the following Sunday). Does that seem reasonable?

[Vikesrock]

Originally Posted by EricH

Oh, and I'd say that the waiver period starts on discovery that the team has added (i.e., 330 registers for San Diego on Monday, and they are discovered as attending on Saturday as somebody goes on a check, they'll be on waivers until the following Sunday). Does that seem reasonable?

I agree, we have no way of knowing when a team actually registered, the waiver period should start when they are posted as available in the waiver thread.

I think that Barry's proposal will make it easier on both players and me by having a fixed time that waivers are processed.

[EricH]

Still to discuss:

1) When should the waiver start for dropped teams? I'm thinking that there are two ways to do this:
a) As soon as the draft ends, any team dropped goes on waivers.
b) After midnight (or some other specified time) after the draft, any team dropped goes on waivers; before then, all teams are free agents.


2) Should teams that will be dropped be posted, as an indication of which teams may/may not be available the next week? (Note that those teams would be "pending" or "probable" drops, not finalized.) I'd go with, for the sake of convenience, requiring the potential drop to be posted-- during the waiver process time on Sunday nights, it'll be relatively easy to go into the threads to do the swap, instead of tracking down the player and getting the team they're dropping.

3) During competition season, teams often show up missing from an event. I was thinking that players with missing teams should move up the list (say, one spot up per missing team in a given event), and not have to drop a team to get a team from waivers for an event they're missing a team in. What do you guys think about that?

[Vikesrock]

1) I like option B for the first question. Teams that are dropped the night of the draft are usually randoms that people are switching out and would really crowd the waiver process with teams that are unlikely to be picked up.

2) The proposed drop should definitely be included in the waiver claim post. If the team being dropped is no longer attending they should still be posted with a note that they are not attending to make things easier to process.

3)I'd be fine with moving someone up a spot or two per missing team during competition season.

[ATannahill]

On item number 2, i feel that a pm to whoever is running the waivers would be acceptable so that no other player can get an advantage by seeing what will be up the following week.

[EricH]

Originally Posted by rtfgnow

On item number 2, i feel that a pm to whoever is running the waivers would be acceptable so that no other player can get an advantage by seeing what will be up the following week.

I was thinking that a PM would be an acceptable method of making a claim, if you wanted to. Open post, PM, or any combination of the two, as long as you note a) the team you want, b) the tier/event combination, and c) the team you're dropping if your claim is the highest priority.

[EricH]

Due to more drops, the following teams are now on waivers (no particular order):

Granite State Tier 1: 134, 1721, 151
Granite State Tier 2: 3074, 58, 241
Finger Lakes Tier 1: 73, 211, 250
Finger Lakes Tier 2: 578, 145, 156
New Jersey: 2600, 2199, 1881, 102, 2729, 2191
Kettering Tier 1: 49, 894, 314
Kettering Tier 2: 2604, 703, 3536
Traverse City Tier 1: 2611, 2767, 3458
Traverse City Tier 2: 3357, 3639, 2000

[Chris is me]

Requesting 102 over 2495 - 8

[dodar]

I'll take 3357 over 857 - 3

[EricH]

And with kenavt dropping out, the following teams enter waiver (to come off not tomorrow, but the Sunday after, due to timing):

Alamo 1: 3529, 3366, 2745
Granite State 1: 836, 58, 1307
Finger Lakes 1: 145, 639, 1405
New Jersey: 2180, 623, 1647
Kettering 1: 703, 3450, 468
Traverse City 1: 3639, 1896, 3688
Kansas City: 2001, 1847, 2357
Superior 2: 2846, 3754, 2175
San Diego: 2090, 2839, 3480
WPI 2: 121, 1884, 3780