An example is in order to aleviate any fears of exposure.
Let's assume the following -
Code:
UniqueHandle WUs or points NickName
xyzzyxyzzy 100,100,100 IronBits
When Howard runs stats, he does it with the UniqueHandle, which is always static, never changes.
Code:
xyzzyxyzzy 100,100,101 xyzzy <-- sneaky IB horsing around. ;)
When using the 'nickname' which is not static, a slight change in the NickName will create chaos and confuse any 3rd party stats tracking attempts.
Now, let's do the same thing, this time with an additional uniqueID, which is static just like Howard's UniqueHandle.
Code:
UniqueID UniqueHandle WUs or points NickName
0000001 xyzzyxyzzy 100,100,100 IronBits
Now we have two static Unique fields, one for Howard, one for 3rd party stats engines.
Now folks like Dyyryath, can use the UniqueID, just like Howard uses his UniqueHandle.
Now if there is a change in the NickName, it will have no effect on either the UniqueID or UniqueHandle.
The only person that knows which UniqueHandle goes to what UniqueID or NickName, would be Howard, period. There is no way for anyone to figure out the UniqueHandle.
Code:
UniqueID WUs or points NickName
0000001 100,100,100 IronBits
0000001 100,100,100 xyzzy <-- sneaky IB horsing around. ;)
This is all that is shown. The above example could not fool the 3rd party stats engines anymore.
It's a win win for everyone.