League Forums

I don't know if it is a bug or if I don't understand how the autoqueue is working; it is my first steps in the game.

After a pick of my team is made, the settings of the autoqueue are not updated (removing 1 in the goal count and decreasing the weight on the position of the drafted player) when I check it in the edit pane of the autoqueue.

On the other hand, when I ask to reset it automaticaly to my coach preferences, it seems to take those into account.

The goal count is actually reducing based on the number of players at that position you have selected - so you don't necessarily want to reduce it. Basically, the logic subtracts the number of players you have selected at that position from the goal count, and adjusts the weight accordingly (basically halving the weight for each player you have selected at that position). The idea is that you will select the number of players at each position you have a non-zero goal count unless you don't have enough picks.

Using your coach's preferences actually sees the players on your roster as not from the draft ... that actually probably is a bug that needs to be fixed.

Thank you for the prompt reply but I am not sure I understand you correctly.

Do you mean that if I am changing the setting during the draft, I should put the weighting and goal count according to the situation before the draft?
So, for example, I pick a QB in the first round and after that go to the setting of the autoqueue to put the goal count of the QB position at 1 because I want 1 more, the autoqueue will not put a QB on the board because the goal count is at 1 and I have already drafted a QB during the draft.

To rephrase it, when I am adjusting the setting in the middle of the draft, does the algorithm run through the player already selected by my team in order to rearrange the queue or does the weighting I select represent the weighting for the next pick?

I am sorry to bug you with that but living in Europe the schedule of the draft is not so convenient to me and I have to rely on the autoqueue for the draft round which take place in the evening in the US.

The "goal count" is the total number of players you want to draft at that position over the entire draft. The idea is that you can set it at the beginning of the draft and forget it, if you need to. If you have a goal count of 1 at RB and 0 at all the other positions, you will most likely take a RB in your first selection. Once you select that RB, if you leave the goal count at 1, the algorithm will see that you have drafted one running back, so it adjusts the next pick as if you had not drafted a RB but have the goal count at 0. If you reduce the goal count to zero, then it further reduces the chances of you selecting a RB.

Looking at it another way, the algorithm is set up to select a maximum of one player at each position (dependent on the weights and the ratings of available players). If all positions are at a goal count of zero, then each pick will be best player available according to the weights, with essentially a maximum of one player at each position. If you have positions that are non-zero, then the algorithm will prioritize those positions above the zero goal count positions and will try to select a player at those positions first, until the goal count number of those players have been reached, at which time you will select BPA based on your weights.

Thank you...

Now I better understand how it works.

Then, indeed, if you ask the coach to remake the automation of the weighting factors during the draft (at least in the inaugural draft), The coach look at the drafted players as part of the roster and set lower weight and count to the position that it should be expected given that it will be lowered once more by the post processing of the draft board selection (I am not sure if what I say does make sense so excuse my French; bottom line is that the auto option of the autoqueue is not working properly if you use it in the middle of the draft).

Yeah, I'll have to look at that because if that's happening then it definitely is a bug. Setting the recommended values should not change the goal count.