Re: [FF]: 2017 Season Long Fantasy FIRST
 

Flyswatter update #1: SPLAT! Found a bug (at least one) in the team removal. Helps to double-check variable names... Might explain why it's been buggy for so long.

And I haven't yet replicated the crashing. (Of course I'm trying here...) But so far, it's handled every non-at-event or previously-picked or otherwise off-nominal team I've tossed its way by flashing up a color like it's supposed to. If anybody experiencing a crash can pass along a crash report, that'd be pretty helpful.

Time to go introduce more bugs... by implementing random rookie functionality! (Don't worry, I'm not releasing YET.)

Edit #1: Huh. That was too easy... If anybody wants to beta test said functionality before I run a draft on Wednesday, use email and I'll send the beta over. Otherwise, I'll probably try to find what's been causing crashes and/or release the debugged sheet before then.

Re: [FF]: 2017 Season Long Fantasy FIRST
 

FYI, we have a need for a draft runner for Bayou tomorrow--something came up with the scheduled runner, and we seem to be low on the usual crew. I might be able to run it, but it's a very long shot. James can't, Joseph is already running one. Anybody want to step up?

Re: [FF]: 2017 Season Long Fantasy FIRST
 

I might be willing to, with only one issue; I don't have Excel. I just have a mac, do the macros and the other assorted things work on Google Sheets, or should I try and install an excel demo on my VM?

Re: [FF]: 2017 Season Long Fantasy FIRST
 

The only functionality that really transfers from Excel to Google Sheets is the data/formatting, and vice-versa. You might be able to get the demo to run with WINE.

Re: [FF]: 2017 Season Long Fantasy FIRST
 

I can.

Re: [FF]: 2017 Season Long Fantasy FIRST
 

Deleted post since theres no way I can run two drafts tonight(Doing other work while running 1 is hard enough).

Re: [FF]: 2017 Season Long Fantasy FIRST
 

Thank you, Joseph and Brennan for keeping Fantasy FIRST going tonight! I would have volunteered if I didn't have a final tomorrow :(

Re: [FF]: 2017 Season Long Fantasy FIRST
 

Apparently, I don't have to do that work anyways, so if Brennan doesn't post thread by 6:40, i got it

Re: [FF]: 2017 Season Long Fantasy FIRST
 

My conputer has been uhh, temporarily handicapped. Apologies and thanks joe for picking up the slack.

Re: [FF]: 2017 Season Long Fantasy FIRST
 

So I posted why in the thread, but Smoky Mountain needs a redraft.

Re: [FF]: 2017 Season Long Fantasy FIRST
 

May need a redraft, depends on how Eric wants to rule it. You were in fact assigned the proper team, its just that after you were assigned that pick, TBC changed their pick, which means a higher priority team was available on your list.

Now thats all find and dandy, but it did technically happen before your pick time, but you did also send a list in which means your picks happen as soon as your slot opens.

Not sure how Eric wants to call this one, but if it does cause a redraft, I won't be assigning list picks until their exact pick time to avoid any redrafts in the future.

Re: [FF]: 2017 Season Long Fantasy FIRST
 

I mean, to be fair, it's not like the 744-48 swap was announced, even in the edit. I don't have a problem making that swap, or the execution after, but it really should be slightly better indicated.

Re: [FF]: 2017 Season Long Fantasy FIRST
 

Questionable Decisionmakers and Untitled Team have agreed to the following trade, posted and waiting for approval at 2:57pm CD Time:

Untitled Receives:
QD 1st Round - Montreal - #5
QD 2nd Round - Montreal - #14
QD 2nd Round - Wisconsin - #16

QD Receives:
UT 1st Round - Montreal - #3
UT 2nd Round - Montreal - #16
UT 2nd Round - Wisconsin - #18

Re: [FF]: 2017 Season Long Fantasy FIRST
 

I agree, I really wasn't thinking when I just made the edit, definitely should of put the trade in there somewhere for clarity.

Re: [FF]: 2017 Season Long Fantasy FIRST
 

FYI, I had to drop next Wednesday's Lone Star Central, but I have tentatively picked up Midwest for Monday. I may also be able to do Idaho on Saturday but that's less likely. However, I might not be able to do that one either, because we'll be skiing in Vermont and wi-fi could be iffy.