DarthVegito wrote: Tue Feb 06, 2018 4:56 pm
WigNosy wrote: Tue Feb 06, 2018 3:25 pm
WigNosy wrote: Tue Feb 06, 2018 1:17 pm
Also please note all the nodes are currently offline; I am doing maintenance on the physical host and will let you know when they are back up.
Nodes are back up. League file zip is NOT updated (will be updated following the draft lotto).
Yes, an MLE explanation please. Currently there is over 8 mil(the amount of the MLE) sitting in everyone's guaranteed salaries on their team page. This isn't exactly what the MLE that we always used was. It's optional and only used if you're over the tax so why is it being subtracted from the available cap space?
Down, boy.
The league file right now (and the index reflects this) is "before the draft." As explained in the first post of the original suggestion thread (
viewtopic.php?f=37&t=5906) FBB doesn't check a team's cap status to determine its eligibility for MLE use until "the draft is completed."
FACT: When the draft is completed, FBB checks to see if a team has more cap space than the total value of the MLE. If the team has less cap space than the value of the MLE (includes no remaining cap space), the team is given access to the MLE and gets a "cap hold" assessed for the value of the MLE so it can't use both its remaining cap space AND the MLE. This is all done by FBB, there is no action needed on our part. If the team has MORE remaining cap space than the value of the MLE, the team does not get access to the MLE (and gets no cap hold).
Once the draft is complete, FBB checks your cap and if you would be over the cap with the MLE cap hold included, you keep the cap hold. If you would be under the cap, the MLE available to you (and its cap hold) drops to 0. So that cap hold you're all up in arms about will fall off when the draft is over.
Note that if the draft is over and you have access to the MLE but then your team salary drops for some reason (e.g., trade between draft end and Free Agency Phase 1, roster cut, or via contract edit), FBB checks your salary status again. If you've dropped far enough under the cap (i.e., with the inclusion of the salary hold your team salary would go under the cap), the MLE (and its cap hold) drops to 0. ADDING salary at this point does NOT trigger a check and will NOT grant you access to the MLE.
This is a mechanism to keep teams from getting to use BOTH cap space AND the MLE. For instance, a team that had 8 million of cap space and had access to the MLE can't then cut a second-round pick to up that cap space to 8.5 million and use BOTH the 8.5 million in cap space AND the MLE - as soon as the cut is made and the cap space opens, the MLE disappears.
What this means for us is the following:
1. If your team salary (including MLE cap hold) is over the cap at the conclusion of the draft you will have access to the MLE. Our RFA cap holds do not apply to this total.
2. For the sake of simplicity, teams may not use the MLE during RFA. RFA is already a pain to implement manually and mixing the MLE with it can cause too many other cascading headaches - the complexity isn't worth it until we are more used to the MLE.
3. A lot of teams will probably be over the cap after RFA that weren't over the cap prior to RFA. Since it's your salary at the end of the
draft, not at the end of
RFA, that determines whether you have access to an MLE, this means if RFA pushes you over the cap you don't
also get the MLE. Sorry.
Side note: Some who are familiar with FBB might suggest that we could apply RFA cap holds by means of either a dummy player or simply editing the "Cut Salary" field in FBB. I tried a lot of ways to implement and none of them worked well. The main problem is that if a player re-signs in RFA the cap hold doesn't go away and "double counts" against a team's cap. And remember when we take the "Cut Salary" out, it lowers team salary - so FBB checks again to see if a team is MLE eligible. Basically, the way FBB works does not play well at all with the way we presently implement RFA. Since they're basically oil and water, I'm not going to try to force them to mix. We would have to completely re-do RFA in a much more clever way that I can't conceive of right now or scrap it entirely in order to get them to work together.