QUOTE(Tenboro @ Aug 31 2014, 16:44)

For 14113, it's not because it's not "old enough" but because the cache was reset at some point.
Those clients are a bit of an outlier case since it's unusual to have that high traffic without having more static ranges. I'm going to take a look at the Asian clients in particular to see if the changes skewed them unfairly.
Edit: Isolated to Asia-based clients, there was indeed an unintended drop in hath due to the relatively higher rate of traffic compared to the number of static ranges. A 25% bonus to Asia-based clients was added to adjust for this.
Hmm, I reset the cache and static ranges of 14113 because I faced a trust problem at mid-August.
Users kept request some files which
not exist in the cache, it made the trust red usually.
I tried several methods to fix it, one of them is resetting the cache, so it became a fresh new client. (IMG:[
invalid]
style_emoticons/default/tongue.gif)
I kept some logs at the time to trace the problem, I will post or pm if you want.
Now return to the hath wage.
In my vision, now the wage start point has down to 1 from 3, but
the cap limited by hit rate or speed is also reduced about 2~3, the reduced hath are now static range bonus.
So 14113 does higher output that could touch cap before patch, but now gets same hath as 14262 which does less output and has high static range. (14262 gets same hath as previous)
My opinion are make the
cap limited by hit rate and speed higher as previous patch, and change the hath/day increase rate by hit rate more linear.
If the clients do not have the high hit rate to reach the cap, they can get the static range bonus to reach it.
Or you want to make static range just as additional bonus.
Because high output + high static range clients should get more wage than the one has only a single stat. (IMG:[
invalid]
style_emoticons/default/tongue.gif)
Maybe the ideal will be like these
CODE
Situation Wage (compare with before)
no output 1
low output lesser
mid output a bit lesser
high output same (near to the hit rate/speed cap)
low output+high static range same or more
high output+high static range more