i dont get it .. :wacko:
Printable View
True... and I don't think he would have bothered to open this topic if he really was cheating
I noticed another weird thing, only Israeli users get affected of this bug, but I didn't say anything :X
don't mind them, they missunderstood you :D
anyway this is a bug, and this is not new, it happened
to many users, and i have a feeling they r just using
it as an wxcuse to get rid of member they prefer not to
have... or in other word: SELECTION :whistling
and that, of course, sucks big time :dry:
One has 8,388,608.12 TB
The other has 8,388,608.06 TB
This number represents roughly what would happen if you subtract 1 from 0 on an unsigned 63 bit number, but here's the problem. Neither MySQL nor PHP offer support for an unsigned 63 bit number. The closest you get to 9223372036854775808 is a signed 64 bit number (bigint) which does not have a problem going below 0. Subtract 1 from 0 with a signed bigint, and you get -1.
If you completely fill a signed bigint, you get 8388607.9999999999990905052982271 TB. 8388608.12 requires an unsigned bigint to store the value, and the "bug" just isn't matching what is known.
The well known bug in tbdev is actually 16 million TB, which is what you get when subtracting 1 from 0 on an unsigned bigint.
So, either TL are using some off the wall coding that supports 63bit unsigned ints (which would be very strange), or somebodies client is screwy. The most screwed up clients are the badly written cheat ones. From TLs point of view, there is nothing to be done but assume you are cheating.
Edit: see squirr3ls post. 16,777,216TB, that's the bug. 8 million TB isn't.
hmmm how exactly does the bug work?