SalaryCapCheck utility

3ric · 03-15-2006, 01:27 PM

This could be interesting for the league commissioners, a simple salary cap check utility: SalaryCapCheck.zip

When investigating the Packers team in the HFL, it was found that the previous owner had assembled the best roster in the league by always offering the minimal salaries possible, through the "commish cheat".

By doing a quick comparison on how big a percentage the salary took up of GBY's salary cap from the team page in the HTML output (http://www.shalkith.com/hfl/stats/10roster.html) you take the columns "Cap cost" and "Save Release", of which the sum of the latter tells you how much salary is paid on the roster. Divide that by the total cap cost, and you got a 17.6% salary percentage compared to the bonus. Most other rosters was in the range of 40-75% ratio of salaries, with no other team dropping below 35%.

My suggestion to combat this was to write an utility for commishes which can do this analysis automatically using the league HTML as input and calculate the salary/bonus ratio for every team, and should a team get their salaries down really low again, it should be easier to catch.

I should mention that these numbers are only relevant in relation to the amount of roster talent. The combination of low salaries and high level of talent should be what's suspicious, not just low salaries.

Anyway, the installation process should be straightforward, and the utility should by default point towards the "leaguehtml" directory in the FOF2k4 program folder. Should the league html output be somewhere else, you can edit the text box in the program. The default value can be changed by editing the SalaryCapCheck.config file and its FilePath key value. After clicking "Go" and receiving the output, it can be copied and pasted as usual.

Example output:
Ratio of salary/cap on rosters:
St. Louis Cardinals: 65.18 %
Green Bay Packers: 17.65 %
Baltimore Colts: 40.46 %
Jacksonville Jaguars: 76.14 %
Kansas City Chiefs: 58.37 %
Miami Dolphins: 57.04 %
Minnesota Vikings: 75.64 %
New England Patriots: 78.75 %
New Orleans Saints: 58.01 %
New York Giants: 70.98 %
New York Jets: 64.60 %
Atlanta Falcons: 63.09 %
Oakland Raiders: 71.96 %
Philadelphia Eagles: 64.86 %
Pittsburgh Steelers: 70.50 %
San Diego Chargers: 50.48 %
Seattle Seahawks: 64.69 %
San Francisco 49ers: 67.96 %
Los Angeles Rams: 46.91 %
Tampa Bay Buccaneers: 60.13 %
Baltimore Ravens: 52.71 %
Washington Redskins: 66.53 %
Houston Oilers: 73.88 %
Cleveland Browns: 54.12 %
Houston Texans: 78.01 %
Buffalo Bills: 51.63 %
Carolina Panthers: 51.05 %
Chicago Bears: 71.87 %
Cincinnati Bengals: 68.82 %
Dallas Cowboys: 36.36 %
Denver Broncos: 54.33 %
Detroit Lions: 55.78 %

stevew · 03-15-2006, 04:12 PM

Just a quick question. I think this may get messed up if a team happens to have more than 53 players on their roster.

The low man on the list is Washington.

Ratio of salary/cap on rosters:
Arizona Pioneers: 34.18 %
Sioux Falls (SD) Green Wave: 60.91 %
Indianapolis Stallions: 49.73 %
Jacksonville Cougars: 33.67 %
Kansas City Arrowheads: 64.21 %
Miami Bay Sharks: 46.25 %
Minnesota Norsemen: 39.05 %
New England Colonials: 57.04 %
New Orleans Delta Rays: 51.72 %
New York Gladiators: 60.89 %
New Jersey Meteorites: 45.12 %
Atlanta Raptors: 55.31 %
Oakland Bandits: 49.91 %
Philadelphia Condors: 62.21 %
Pittsburgh Ironmen: 43.74 %
San Diego Lightning: 31.56 %
Seattle Cyberhawks: 60.52 %
San Francisco Gold Rush: 67.70 %
St. Louis Stags: 51.26 %
Tampa Bay Pirates: 53.90 %
Tennessee Dreamsicles: 41.57 %
Washington Landslides: 29.23 %
Baltimore Nightwings: 39.78 %
Cleveland Maroons: 44.38 %
Houston Apollos: 53.67 %

But he also has one guy on IR, so some of his players are actually showing up as negative cap space gained by being cut. The other low teams seem to have 54 players(or more) as well.

But thats a great idea for a utility nonetheless. If I add in the minimum times 54 players, his percentage goes into the mid 40s. Which makes sense, and is right in line with my team. When you are either in cap hell, or are trying to make a run, i would think your percentage would be lower. Obviously not 17% low.

Alf · 03-16-2006, 03:32 AM

3ric, can you do that for IHOF ?

3ric · 03-16-2006, 10:24 AM

stevew, I guess I should use only the 53 players with the highest salaries (or cap figures) to get the right numbers for every team. Good point.

3ric · 03-17-2006, 10:20 AM

Updated the utility to account for negative cap space for some players.

gottimd · 03-17-2006, 11:22 AM

Great Tool, this should be put in the sticky thread. NAFL tested, and discussed, no worries.

gottimd · 03-17-2006, 11:30 AM

This basically shows you where to look, its not an identifier.

For instance, I could have just traded with team x for their star qb. On team x he had a 400 million salary and huge bonus. When he comes over to my team via the trade, obviously I don't incur the bonus expense, so it may through my % way out for having a huge base pay and no bonus, correct?

But it is still a good indicator of where there might be something fishy going on.

sovereignstar · 03-17-2006, 02:04 PM

Am I correct in noting that this program requires you to have an older version of the .NET framework? It keeps on saying I need 1.4(?) when, unfortunately, gstelmack's FOF Extractor requires 2.0+.

3ric · 03-17-2006, 02:07 PM

Yes, it's written with the previous version of .NET (2003), but I use gstelmack's Extractor as well and have no problem with either of them? Both frameworks should co-exist quite happily, I imagine.

sovereignstar · 03-17-2006, 02:26 PM

Hmmm.. not happening for me.

03-15-2006, 04:12 PM	#2
stevew Hall Of Famer Join Date: Dec 2003 Location: the yo'	Just a quick question. I think this may get messed up if a team happens to have more than 53 players on their roster. The low man on the list is Washington. Ratio of salary/cap on rosters: Arizona Pioneers: 34.18 % Sioux Falls (SD) Green Wave: 60.91 % Indianapolis Stallions: 49.73 % Jacksonville Cougars: 33.67 % Kansas City Arrowheads: 64.21 % Miami Bay Sharks: 46.25 % Minnesota Norsemen: 39.05 % New England Colonials: 57.04 % New Orleans Delta Rays: 51.72 % New York Gladiators: 60.89 % New Jersey Meteorites: 45.12 % Atlanta Raptors: 55.31 % Oakland Bandits: 49.91 % Philadelphia Condors: 62.21 % Pittsburgh Ironmen: 43.74 % San Diego Lightning: 31.56 % Seattle Cyberhawks: 60.52 % San Francisco Gold Rush: 67.70 % St. Louis Stags: 51.26 % Tampa Bay Pirates: 53.90 % Tennessee Dreamsicles: 41.57 % Washington Landslides: 29.23 % Baltimore Nightwings: 39.78 % Cleveland Maroons: 44.38 % Houston Apollos: 53.67 % But he also has one guy on IR, so some of his players are actually showing up as negative cap space gained by being cut. The other low teams seem to have 54 players(or more) as well. But thats a great idea for a utility nonetheless. If I add in the minimum times 54 players, his percentage goes into the mid 40s. Which makes sense, and is right in line with my team. When you are either in cap hell, or are trying to make a run, i would think your percentage would be lower. Obviously not 17% low. Last edited by stevew : 03-15-2006 at 04:20 PM.

03-16-2006, 03:32 AM	#3
Alf Pro Starter Join Date: Jan 2001 Location: Rennes, France	3ric, can you do that for IHOF ? __________________ FOFL - GML - IHOF - FranceStats

03-16-2006, 10:24 AM	#4
3ric College Starter Join Date: Dec 2000 Location: Sweden	stevew, I guess I should use only the 53 players with the highest salaries (or cap figures) to get the right numbers for every team. Good point. __________________ San Diego Chargers (HFL) - Lappland Reindeers (WOOF) - Gothenburg Giants (IHOF) Indiana: A TCY VC - year 2044 - the longest running dynasty ever on FOFC!

03-17-2006, 10:20 AM	#5
3ric College Starter Join Date: Dec 2000 Location: Sweden	Updated the utility to account for negative cap space for some players. __________________ San Diego Chargers (HFL) - Lappland Reindeers (WOOF) - Gothenburg Giants (IHOF) Indiana: A TCY VC - year 2044 - the longest running dynasty ever on FOFC!

03-17-2006, 11:22 AM	#6
gottimd Dearly Missed (9/25/77-12/23/08) Join Date: Nov 2003 Location: DC Suburbs	Great Tool, this should be put in the sticky thread. NAFL tested, and discussed, no worries. __________________ NAFL New Orleans Saints GM/Co-Commish MP Career Record: 114-85 NAFL Super Bowl XI Champs In memory of Gavin Anthony: 7/22/08-7/26/08

03-17-2006, 11:30 AM	#7
gottimd Dearly Missed (9/25/77-12/23/08) Join Date: Nov 2003 Location: DC Suburbs	This basically shows you where to look, its not an identifier. For instance, I could have just traded with team x for their star qb. On team x he had a 400 million salary and huge bonus. When he comes over to my team via the trade, obviously I don't incur the bonus expense, so it may through my % way out for having a huge base pay and no bonus, correct? But it is still a good indicator of where there might be something fishy going on. __________________ NAFL New Orleans Saints GM/Co-Commish MP Career Record: 114-85 NAFL Super Bowl XI Champs In memory of Gavin Anthony: 7/22/08-7/26/08

03-17-2006, 02:04 PM	#8
sovereignstar Pro Starter Join Date: Feb 2004	Am I correct in noting that this program requires you to have an older version of the .NET framework? It keeps on saying I need 1.4(?) when, unfortunately, gstelmack's FOF Extractor requires 2.0+.

03-17-2006, 02:07 PM	#9
3ric College Starter Join Date: Dec 2000 Location: Sweden	Yes, it's written with the previous version of .NET (2003), but I use gstelmack's Extractor as well and have no problem with either of them? Both frameworks should co-exist quite happily, I imagine. __________________ San Diego Chargers (HFL) - Lappland Reindeers (WOOF) - Gothenburg Giants (IHOF) Indiana: A TCY VC - year 2044 - the longest running dynasty ever on FOFC!

03-17-2006, 02:26 PM	#10
sovereignstar Pro Starter Join Date: Feb 2004	Hmmm.. not happening for me.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)