The Fleaflicker waiver system is a mystery. I wish someone in support would explain it because stuff like this happens all the time. I just had it happen this week. Some idiot cut Cam Akers so I made claim to get him 1 other team did and that team is undefeated and according to waiver order on standings page he was 10th and I was 6th but they gave him Akers instead of me. He hasn't made a waiver claim all season while I have including this week so just because he hasn't made a move yet and I have they gave him to the other team.
But that would be going by the "Rolling Order" version where each time you make a move you get moved to the bottom of the list and every other team gets a chance at a move before you do again. While the other option is revert to standings each week lowest ranked team 1st. The setting for that league are to go by standings not the rolling order so he shouldn't have gotten him just because he hasn't made a waiver move yet otherwise why have the options to pick which version you want to use when it seems like Fleaflicker is going by the rolling order thing anyway giving the team that has went longer without picking a player instead of the lower ranked team?
I figured out how it works now. if you have settings for waiver order to be decided by standings each week, it resets it on Tuesday after week is over to worst to first based on standings. THEN for the entire week until next Tuesday each time a team makes a waiver claim it does the rolling order moving them to the bottom. So each time a new claim is made the order gets changed.
When I did everything by hand in the old days it was the 1st claim by however many teams made one is "round 1" then it starts over then as round 2 and each claim is made again with the worst ranked team of the group going first not the team that has went yet. after the entire list of claims is done for the week then it resets again. So if a player gets cut and multiple teams claim him the one with worst record gets him not the one who hasn't made a claim yet.
Thats the way it should be when you have it set to NOT use the rolling order. Then every time there is a new set (or round) of claims the worst ranked team gets 1st pick when there are multiple claims for the same player. It should reset for each round of waivers not just at the beginning of the week. Doing it with FAAB method would be better so you know no matter how many teams claim a guy if you paid the highest price you get him Since it doesn't guarantee if you have the worst record you will get a guy in Fleaflickers waiver system.
I don't have an explanation of how the example Shook 20 showed happened where a team in FAAB method that paid the higher price didnt get a guy. The only way I've seen that happen before is what HelaodsVerde mentioned where they have an illegal roster such as a player on IR or Taxi that didn't meet the requirements. If that isn't the reason wny then I have no idea why.
ShookSat 10/1/22 12:23 PM
We had a waiver processed today both played have full rosters, bother were trying to replace an active player on the roster with Josh Palmer.
Bids
Player A - $0
Player B - $2
Both have over $80 in budget
Player A won the waiver.
How is this possible?
JRHroxThu 10/20/22 2:19 PM
The Fleaflicker waiver system is a mystery. I wish someone in support would explain it because stuff like this happens all the time. I just had it happen this week. Some idiot cut Cam Akers so I made claim to get him 1 other team did and that team is undefeated and according to waiver order on standings page he was 10th and I was 6th but they gave him Akers instead of me. He hasn't made a waiver claim all season while I have including this week so just because he hasn't made a move yet and I have they gave him to the other team.
But that would be going by the "Rolling Order" version where each time you make a move you get moved to the bottom of the list and every other team gets a chance at a move before you do again. While the other option is revert to standings each week lowest ranked team 1st. The setting for that league are to go by standings not the rolling order so he shouldn't have gotten him just because he hasn't made a waiver move yet otherwise why have the options to pick which version you want to use when it seems like Fleaflicker is going by the rolling order thing anyway giving the team that has went longer without picking a player instead of the lower ranked team?
JRHroxFri 10/21/22 4:11 PM
I figured out how it works now. if you have settings for waiver order to be decided by standings each week, it resets it on Tuesday after week is over to worst to first based on standings. THEN for the entire week until next Tuesday each time a team makes a waiver claim it does the rolling order moving them to the bottom. So each time a new claim is made the order gets changed.
When I did everything by hand in the old days it was the 1st claim by however many teams made one is "round 1" then it starts over then as round 2 and each claim is made again with the worst ranked team of the group going first not the team that has went yet. after the entire list of claims is done for the week then it resets again. So if a player gets cut and multiple teams claim him the one with worst record gets him not the one who hasn't made a claim yet.
Thats the way it should be when you have it set to NOT use the rolling order. Then every time there is a new set (or round) of claims the worst ranked team gets 1st pick when there are multiple claims for the same player. It should reset for each round of waivers not just at the beginning of the week. Doing it with FAAB method would be better so you know no matter how many teams claim a guy if you paid the highest price you get him Since it doesn't guarantee if you have the worst record you will get a guy in Fleaflickers waiver system.
I don't have an explanation of how the example Shook 20 showed happened where a team in FAAB method that paid the higher price didnt get a guy. The only way I've seen that happen before is what HelaodsVerde mentioned where they have an illegal roster such as a player on IR or Taxi that didn't meet the requirements. If that isn't the reason wny then I have no idea why.