We're gonna simplify this, since no one seems to understand...
EQ names before this patch were 30.. now they are 64, but to make this example not spam 5 pages we're going to say they were 6 now they are 15. The thing the old client would read for a name every 6 "bytes" or characters, and that is what our emu server sends.. as show below:
<none><none><none><none><none><none><none><none><none><none>
But the new client is expecting to recieve 15 but we're still sending them every 6, so it's going to inturpret (sp) them as this:
<none><none><none><none><none><none><none><none><none><none>
So basically what it does is this. EQ client checks the string.. see's if there is a "<none>", which means that it should display the create new character button. But when it doesn't read that at first, or there is more than 1 it'll either put it, or leave it blank for some reason (the red ones give <none> but then they give a <no at the end, so it doesn't know what to do and shows the name as blank. Now for the white ones it stats out with ne> so it says hey this is a name, but <none> is considered to be a new create button so it guesses it's there on accident and forgets about it and just shows the ne>. The thing is also it's going to keep reading into other places in the packets.. and it's going to mismatch positions and read gender/race/class/ect. as the wrong values. This messes things up and causes BAD things to happen when the client gets the wrong values =). Anyways I gotta go, hope that helps.
|