I then asked about BTP's bidHi Brandon -
On the Setup > Salary Cap Setup > General Salary Cap Setup you choose to apply 50% of the players salary when dropped. This is not included until the player is actually dropped, which resulted in your exceeding of the salary cap.
- Julie
Basically they are saying that the system doesn't take into account the salary cap hit for dropping a player it assumes you are going to get 100% of your cap room back. But it doesn't actually give you your money back from dropping the player until all other bids are processed. I *think* the explanation makes sense to me but the logic MFL uses to process blind bids doesn't.Brandon -
The system processes the blind bidding, so a player will not be awarded if that would exceed the blind bidding balance. Once they are processed, at that time your dropped player penalty is applied, not before this time frame. Therefore an owners bids can be within the salary cap range and they are awarded. The penalty is not included in this process an adjustment, which in this case exceeded the cap.
For Yates the reason was:
Add Yates, T.J. HOU QB for $2025000.00 and drop Gray, Jonas FA* RB (Error - Transaction Would Create An Invalid Roster For Bring the PainHard League Salary Cap of $45000000.00 Exceeded ($45945263.50)
The site does not include any other dropped players during that waiver period as they are not yet dropped/processed.
It doesn't take into account the fact that we also have a Hard Salary cap and it states:
Salary Cap Type: Hard limit - only a commissioner-initiated transaction may exceed the salary cap.
Obviously we just proved that that explanation isn't 100% true but they didn't address that when I asked the about it.
The first transaction to process is always going to be the one with the highest bid. In this case it was Bring the Pains bid for Keenum where Manning is dropped. It then goes through each bid and check to see if there is enough cap room to add the player.
In the case of Wabbits it didn't add in the salary cap adjustments until after the players were dropped, despite the fact that we also have a hard cap.
Of course this isn't considered a bug by MFL but they did forward this to one of their dev's as a feature request. Given that we've had the same rules for the last 7+ years and they are saying that its always worked like this we'll have to let the bids stand and in the offseason we can see what, if anything, we want to do to account for this.
In the meantime if this happens again this offseason make sure to get your roster under the salary cap limit as soon as you can as our settings won't let you submit a lineup with an invalid roster/salary cap.
