But I ran into a problem. The SalaryAverage field is sometimes (actually quite often) wrong.
Here's an example from my data (a player with a 2-year, $900,000 contract... but the average is listed $894,000):
Code: Select all
<Contract>2</Contract>
<Rookie>false</Rookie>
<PProtected>false</PProtected>
<NoApplyRerate>false</NoApplyRerate>
<AvailableforTrade>false</AvailableforTrade>
<NoTrade>false</NoTrade>
<CanPlayPro>true</CanPlayPro>
<CanPlayFarm>true</CanPlayFarm>
<ForceWaiver>false</ForceWaiver>
<StarPower>0</StarPower>
<Salary>
<unsignedInt>0</unsignedInt>
<unsignedInt>900000</unsignedInt>
<unsignedInt>900000</unsignedInt>
<unsignedInt>0</unsignedInt>
<unsignedInt>0</unsignedInt>
<unsignedInt>0</unsignedInt>
<unsignedInt>0</unsignedInt>
<unsignedInt>0</unsignedInt>
<unsignedInt>0</unsignedInt>
<unsignedInt>0</unsignedInt>
<unsignedInt>0</unsignedInt>
</Salary>
<SalaryAverage>894000</SalaryAverage>
This bug does not affect all players, but it was a significant number of them.
I have since changed my code to read the second item in the Salary array, as that appears to be the first year of the contract. So I am fine, but I thought I should bring this bug to your attention.