You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there will be a 3-5 day period where I'll release draft order and owners will have to set their keepers, which I think I want to be blind to the rest of the league.
then at the deadline, keepers lock and they'll be visible. could be a hidden toggle like we do for CBB/CHK claims
once set, I was going to manually enter all of the keepers in the correct round, before the draft starts. that way (I think) those players won't be available. although that will cause an issue with the total draft time...
axel 8:02 PM
We should be able to automate a lot. It's not visible to others yet, but the draft position is saved with each roster position. If we load the pick into the draft, its going to mess up some assumptions I've made about who is next, but I can figure it out.
I think I can add a column on the draft pick table for "keeper?" then exclude it when necessary
The text was updated successfully, but these errors were encountered:
there will be a 3-5 day period where I'll release draft order and owners will have to set their keepers, which I think I want to be blind to the rest of the league.
then at the deadline, keepers lock and they'll be visible. could be a hidden toggle like we do for CBB/CHK claims
once set, I was going to manually enter all of the keepers in the correct round, before the draft starts. that way (I think) those players won't be available. although that will cause an issue with the total draft time...
axel 8:02 PM
We should be able to automate a lot. It's not visible to others yet, but the draft position is saved with each roster position. If we load the pick into the draft, its going to mess up some assumptions I've made about who is next, but I can figure it out.
I think I can add a column on the draft pick table for "keeper?" then exclude it when necessary
The text was updated successfully, but these errors were encountered: