![]() |
Re: [FF]: 2017 Season Long Fantasy FIRST
Got a couple of announcements and reminders.
1) No drafts tomorrow, folks. Enjoy the evening off. Tech Valley and Greater Pittsburgh are Wednesday night. If you see those drafts pop up, don't sweat it, you aren't late (until Wednesday). 2) For the draft runners, I just uploaded an updated version (3.2.3) of the program. The only change is to allow lists with "Random" to, well, pick random, automatically. Next up are a couple of changes to do the same for random rookies and possibly a couple of other minor tweaks (think "convenience"--like being able to just rotate the player list from the last time, or being able to tell at a glance which player(s) have lists). 3) We're still looking for someone to run Bayou, a week from tomorrow. That's the only hole left (other than a possible one in Colorado on 12/11). Oh, and I'm pretty sure this is the first time we've made it for 20 drafts from season start with perfect attendance, ever. Usually I've sent at least one boot warning by now... |
Re: [FF]: 2017 Season Long Fantasy FIRST
Quote:
|
Re: [FF]: 2017 Season Long Fantasy FIRST
Quote:
|
Re: [FF]: 2017 Season Long Fantasy FIRST
Eric,
Have you been able to determine if we were planning to use the old ranking points system (20 12 12 6 6 ...) or the district ranking points system for scoring? |
Re: [FF]: 2017 Season Long Fantasy FIRST
Quote:
Edit: On further review... No determination. Any chance TBC can check the scoring system from last year? At this point in time, I don't see a reason to change the system from last year's, other than to exempt Culture Change awards from district averaging, and possibly to adjust district scoring (some discussion of removing inter-district points from the count and/or normalizing scores to two events rather than averaging all events). |
Re: [FF]: 2017 Season Long Fantasy FIRST
Either I missed something or am misunderstanding.
In 2015 we switched over from giving the win loss points to the district ranking points because there was no win loss. I thought we kept the same in 2016 because our ranking wasn't based on win loss but on QP. Basically I thought we replaced the 2 points for a win 1 for a tie and 0 for a loss with the district ranking 2 years in a row (To also normalize the points between large and small events) but kept the ranking bonus points the same to reward the teams who understood how to rank well. So did we switch it between the two years or keep it the same I honestly don't remember. |
Re: [FF]: 2017 Season Long Fantasy FIRST
Quote:
|
Re: [FF]: 2017 Season Long Fantasy FIRST
We kept it the same as 2015.
|
Re: [FF]: 2017 Season Long Fantasy FIRST
Quote:
*Unless the GDC completely removes ranking points or an equivalent from determining rank. In which case, we'll discuss fallback options. Discussion if any to start no earlier than 1/7/17 :cool:. |
Re: [FF]: 2017 Season Long Fantasy FIRST
Quote:
*90 seconds later* "Steamworks like the industrial revolution does not have an anyone can succeed ranking system, instead the top teams are decided by who has the most blue banners historically, any ties will be broke by oldest blue banner. There will be no picking in the top 8 and no matches but instead exhibitions for the top teams to observe and decided who to hire for their alliance" Fantasy FIRST then becomes basically a stockmarket instead of a Fantasy sports league |
Re: [FF]: 2017 Season Long Fantasy FIRST
Quote:
|
Re: [FF]: 2017 Season Long Fantasy FIRST
QD and Falcon have completed the following trade:
Falcon receives: #4 and #15 at San Francisco #2 and #17 at Rocket City QD receives: #2 and #17 at San Francisco #9 and #10 at Rocket City |
Re: [FF]: 2017 Season Long Fantasy FIRST
So how are we doing requests for teams who join an event after the draft, but before season starts? Waiver or first come first serve?
|
Re: [FF]: 2017 Season Long Fantasy FIRST
Quote:
|
Re: [FF]: 2017 Season Long Fantasy FIRST
Quote:
|
| All times are GMT -5. The time now is 15:09. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi