Rodney wrote:I might have missed a "as far as I can tell" there, but that would explain why everybody has a "0" as value for this stats key (according to the API).
Also according to the server files it is read-only:
Code: Select all
<field name="Name">level</field>
<field name="Description" />
<field name="DefaultValue">0</field>
<field name="ValueType">PersistentValueType_Set</field>
<field name="ClientFlags">PersistentValueProtection_ReadOnly</field>
<field name="ServerFlags">PersistentValueProtection_ReadOnly</field>
<field name="WritePolicy">PersistentValueWritePolicy_Disconnect</field>
<field name="Authorative">false</field>
While for example elo/elo0/elo1 are defined as read/write for the server.
Code: Select all
<field name="Name">elo</field>
<field name="Description" />
<field name="DefaultValue">1000.0</field>
<field name="ValueType">PersistentValueType_Set</field>
<field name="ClientFlags">PersistentValueProtection_ReadOnly</field>
<field name="ServerFlags">PersistentValueProtection_ReadAndWrite</field>
<field name="WritePolicy">PersistentValueWritePolicy_Checkpoint</field>
<field name="Authorative">false</field>
There are four fields that are tagged as 'ReadOnly', out of which only one is currently calculated by the backend, the second one is insignificant, the third one is unused, and the fourth one is 'level', which I had never seen before.
However, since there are no 'references' as to how it's calculated (as opposed to other fields like 'score'), I will have to somehow figure it out on my own based on official stat values (which is how I figured out 'score' initially, before looking at the files).
This might take some time, but I'll keep you guys posted.