Re: TOP Players / Tier Requirements Thread - Updated 10/31/07
The current coding behind FFR scoring simply follows this semi-pseudocode:
//
variables p, g, a, m, b
variables combo, total
time windows : hit : increment corresponding variable
combo = greatest distance between m increments
total = variable*value + 1000*combo
//
The current tier calculator uses the total value, which is anywhere from 1 to 7 digits.
For a PA-based system, you would omit the totaling procedure and could instead have a storage string that represents the accuracy increments. Ex: 5G1A1M1B would indicate a score of 5 goods with an average miss. Of course, the tier calculator would need to support the interpretation of variable-length strings, which I assume can be accomplished through basic case statements.
The whole process would be a bit tedious, which is kinda what JX was getting at.
The current coding behind FFR scoring simply follows this semi-pseudocode:
//
variables p, g, a, m, b
variables combo, total
time windows : hit : increment corresponding variable
combo = greatest distance between m increments
total = variable*value + 1000*combo
//
The current tier calculator uses the total value, which is anywhere from 1 to 7 digits.
For a PA-based system, you would omit the totaling procedure and could instead have a storage string that represents the accuracy increments. Ex: 5G1A1M1B would indicate a score of 5 goods with an average miss. Of course, the tier calculator would need to support the interpretation of variable-length strings, which I assume can be accomplished through basic case statements.
The whole process would be a bit tedious, which is kinda what JX was getting at.






Comment