Packet 1006 [Unknown]

[FuriousFang]

Hey everyone,

This is research from my folder that I just added. It's very odd. Packet ID 1006. Here's what it does...

1. Undresses, unmeshes, resets hp to 0, removes avatar, and removes item bp.
2. Sets this general data (for my character at least):

3. Freezes the client.


EDIT:
Offset 16 is a time stamp and offset 2 is the uid (which i tested doesn't have to be there). The entire thing is basically 0. This might be a way that the client sends general data within itself.

Interesting right? I wonder what it could be.

Sincerely,
Fang

[Its Arco]

Why the **** are you setting a timestamp in the characterinfo packet?

[FuriousFang]

Originally Posted by stigs

Why the **** are you setting a timestamp in the characterinfo packet?

I'm not. The client does. That's why it's so unknown and weird.
And look at the length. It's only 37!

[Korvacs]

What? Explain whats happening here, wheres the packet from and going to etc.

[FuriousFang]

Originally Posted by Korvacs

What? Explain whats happening here, wheres the packet from and going to etc.

I made a command that makes a new packet of a packet id. In this case it took packet id 1006. Then, it made an empty buffer of the length that the client is meant to read and recognize. It then sends it to the server to let me know if there is a packet at that packet id and what the length is. In this case, we all know 1006 is the character info packet, then it sent a general data packet as shown in the picture above. After that, the client froze.

This is one of a few possible things that it might be:
1. Most likely it's the character info packet buffer telling the client to proceed onto general data (on login). This doesn't explain it's length tho since it's never been that short.
2. This might be a way that the client sends data (like general data) to the client within itself.

What are your guesses Korvacs?

[Korvacs]

Im guessing that your sending the server an invalid packet, so its sending you an invalid response. The client never sends the 1006 packet, that packet is used once and once only and thats during the login process, beyond that it is never used, as a result im not supprised you got a bad response when you tried to send it to the server.

Its definately neither of your options, the client responds to 1006 with the general data proceed with login request, not the server.

[FuriousFang]

Originally Posted by Korvacs

Im guessing that your sending the server an invalid packet, so its sending you an invalid response. The client never sends the 1006 packet, that packet is used once and once only and thats during the login process, beyond that it is never used, as a result im not supprised you got a bad response when you tried to send it to the server.

Its definately neither of your options, the client responds to 1006 with the general data proceed with login request, not the server.

I sent it with a length at 80 bytes and it is supposed to return the real length that the client is comfortable with. It was correct about all of the other packets so I don't see why it would be incorrect with this one. For all we know, this could be a specialized packet like the 1009 packet that spawns items in 5200+. Weird thing is.. it returns general data.

Edit: I figured it out. The test I was doing are two tests. One sends it to the server and one sends the buffer to the client. When it sent it to the client, I got this result. This means that the client reacts to the received packet with a general data packet.

"Most likely it's the character info packet buffer telling the client to proceed onto general data (on login). This doesn't explain it's length tho since it's never been that short." << me first guess what correct. Interesting tho isn't it?

[Korvacs]

Of course the client reacts to the 1006 packet, thats how it is in the login process. And of course it responds with a general data packet, again thats how it is in the login process. Your first guess was correct, although i wish you had explained your tests like i asked, its hard to make an assessment of whats going on with such general information >_>".

As for the length of the general data packet, you are sending a login packet to the client after you have logged in, again its no real surprise that your getting weird packets.

[FuriousFang]

Originally Posted by Korvacs

Of course the client reacts to the 1006 packet, thats how it is in the login process. And of course it responds with a general data packet, again thats how it is in the login process. Your first guess was correct, although i wish you had explained your tests like i asked, its hard to make an assessment of whats going on with such general information >_>".

As for the length of the general data packet, you are sending a login packet to the client after you have logged in, again its no real surprise that your getting weird packets.

Yah. Well I have always kept an eye on the packethandler on login but I overlooked the Character Info, so I guess it's just interesting to me =]