-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Passwords are insecure, and I don't want it to be my fault that your password is exposed if my provider (Google) is compromised.
With password-less sign in, all you have to remember is your email.
So-called "Social login" or "3rd party login" is a quick an easy way to reduce the number of passwords that users need to remember.
Using 3rd party login does not give 110 yards access to post on your behalf.
3rd party login providers share the following information with 110yards:
- Your full name
- Your email address
Players are locked at the beginning of their team's game for the week. Players whose team is on bye will be locked once the last game of the week has started
All players remain locked until the last game of the week has completed, at which point, they become eligible for a waiver bid. After waivers are processed, all players are unlocked until games start again.
Each day at 8AM central time a task is run called "end of day". The end of day job checks to see if any of the weekly tasks need to be run and triggers them if necessary.
The week ends once 24 hours have passed since the beginning of the last game of the week (the 24 hour window is to ensure that any late stat corrections are captured for the last game). In practice, this generally means around 36 hours after the last game of the week, assuming it's an evening game.
At the end of the week, results are calculated, players are unlocked and waivers are enabled.
Waivers are run the next day when the 8AM job runs again (24 hours later).
Example week where the last game of the week is Sunday at 4PM
- Tuesday @ 8AM Central - Results calculated, players unlocked, results calculated
- Wednesday @ 8AM Central - Waivers calculated, players freely available
Waivers are used on this site as the method for adding players shortly after all games for the week have ended. Rather than making it a race to get the player who had the big week, while waivers are active, teams must place bids on available players.
Bids are hidden from other teams, and bids of $0 are allowed (so you can always bid, even if you use up your entire waiver budget)
At the end of waivers, the site will assign sort all of the bids from highest to lowest, then assign that player to the winning bidder's roster. In the case of a tie, the team with the highest waiver priority will win.
Bids can fail for several reasons:
- You get out bid by another manager
- You bid the same as another manager, but that manager has a worse record than you and wins on priority
- You bid the same as another manager, have higher priority to start than that manager, but have already won another bid, so your priority is lower now
- You don't select a drop player, and you have no room on your roster (maybe because you won another bid)
- You do select a drop player, but that player is no longer on your roster (maybe because you had two bids with him as the drop player)
It's ok to make multiple bids which can't possibly work together, as a sort of back up plan. For example, you bid $5 on Player A, dropping Player C. Then you bid $4 on Player B, also dropping Player C. If you win the bid on Player A, your bid on player B will fail because C is no longer on your roster. If you lose the bid on Player A, you might still win the bid on Player B.
Your pending waiver bids and the results from your past waiver bids can be seen on your roster page.
League rankings at the end of the week are used to assign waiver priority. The team with the worst record (in the case of a tie, tie breakers will be used) gets the highest waiver priority, and so on down the list.
Each time a team wins a waiver bid, they are moved to the bottom of the waiver priority list.
E.g. Bob and Joe both bid $5 on the same two players. Bob has the worst record in his league, so his $5 for player 1 is accepted. Next, when the system looks at their bids on player 2, they are tied again, but now Joe has higher waiver priority, so his bid for player 2 is accepted.
Rankings are calculated using the same "points" method as the CFL users. 2 points for a win, 1 point for a tie.
Tie breakers are used to calculate rankings in the league if win-loss alone isn't enough.
The following tie breakers are used, in this order:
- Total wins
- Player points for
- Player points differential (points for - points against)
- Random selection
In the unlikely event of a tie during a playoff matchup, the team with the better rank during the regular season will advance (eg: the #1 team would win any tied playoff matchup, the #2 seed would win against all but the #1 seed, etc).
If you enable and configure Discord notifications, 110 yards will send messages to your Discord server when certain events occur.
The following events are available:
- Draft events: send a message when a player is drafted, or the commissioner undoes a pick.
- Transactions: send a message when a player is added or dropped
- Waivers: send a message when waivers are complete, reporting which players were claimed
- End of week: send a weekly recap message after the results have been calculated
Follow the Discord instructions here to obtain a web hook URL: https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks
Paste the web hook URL into the text box in your league settings, enable the notifications your league wants to receive, and save your league options.
You can use the "Send a test notification" button at any time to ensure the integration is working.
If your league was active in a past season, then it will be available for the commissioner to re-activate for the upcoming season. See this article for more information: https://github.com/mdryden/110yards/wiki/Renewing-a-league
Commissioners can do this from the matchup page after the week has completed - click here to see detailed instructions.