Re: mooClick Large User Ids
I don't see any logical explanation for why MMF2 would be programmed to change the initial ID.
I think its a bug too.
Re: mooClick Large User Ids
It isn't programmed to change the initial ID, but I think that the code for setting the initial ID to 1 has been accidentally removed. When you declare an int in C++, it takes the value of the last int which was at that memory address unless you set it to something else.
Re: mooClick Large User Ids
Its not bug, in MMF 1.5 it sometimes happenned too. Its MooClick problem.
Re: mooClick Large User Ids
It wont effect the amount of data sent, all IDs are sent as 4 bytes unsigned values no matter if its 0 or 1768709275.
Re: mooClick Large User Ids
Numbers like that are sent binary form, not in text form.
I believe that the user ID is sent as a "long" value:
A long value is only 4 bytes big (4 characters) which isn't exactly much.
A long value goes from about 0-4294967295 if it is an unsigned number.
*edit* aw Andrew you were faster ;)