[Request] Some AfterLogin packets.

Hallo :)

After clicking character select, there are some packets sent by the client I'd like to understand:
Then,
0xDF PlayerUpdate. What is this ?
Packet Log

Code:

---

DF 00 // nothing else

---

0xCF TEMP SKILL. What is this too ?!
Packet Log

Code:

---

CF 00 // nothing else

---

edit2: They are both sent when changing map aswell.

edit:
0x23, no idea what this does, it's not even in moopledev.. :/ but its at login ...

When using Combo (Crusader) I get 0x6C, Again ,another unknown header... what could it be... ?

Thanks, nico


And if you wanna be kind, does any of you coded these packets?

Code:

---

    OPEN_ITEMUI(0xEB),
    CLOSE_ITEMUI(0xEC),
    USE_ITEMUI(0xED),

---

Not exactly sure what they do, but it looks like the data is empty. The CF 00 and DF 00 is the header obviously (00xCF -> 0xCF and 0xDF)

If those are recv headers then you can just print the slea.toString() to your bat file whenever they get called

I know its just header 00
But the question is, what do they do ?

Quote:

---

Originally Posted by nicomuffin

I know its just header 00
But the question is, what do they do ?

---

Not exactly sure what an item's ui is or does, sorry.. However, you'll notice a lot of headers don't have structures or handlers.

I do wonder how you get all those recv headers, though.. I didn't think you were able to get those from IDA and I never knew things like MATCH_TABLE existed outside of PLAYER_INTERACTION

Quote:

---

Originally Posted by nicomuffin

I know its just header 00
But the question is, what do they do ?

---

Check their recv-handlers and see.

I'm asking this because it's not coded at all .....
Else it would be really stupid from me to ask this.

Quote:

---

Originally Posted by chunkarama

Not exactly sure what they do, but it looks like the data is empty. The CF 00 and DF 00 is the header obviously (00xCF -> 0xCF and 0xDF)

If those are recv headers then you can just print the slea.toString() to your bat file whenever they get called

---

"00x" is incorrect

it's 0x00CF, 0x00DF

"0x" is a form recognized by the computer to symbolize hexadecimal. That's why 00x would be wrong since the computer would not know what to do with it and mark it as an error. You can also append a 0 in front of a number for octal. So 0123 would be recognized as octal.

Oh come on ... that's just a typo =/
You guys are just being hextypo nazis, the real problems are
What is 0xdf, 0xcf and 0x23 supposed to do ? (recv opcodes)

What are you expecting anyone to do?

Since they're only opcodes the client sends, and there's no server response for them (to my knowledge, at least), the only person who would know exactly what they do is Nexon.

Without even any data in the packets, there's nothing to go by. At most, you could pick apart the client in IDA and see if you could figure it out from there. Not an easy thing to do, though.

One day i'll find out ! haha ^^

Quote:

---

Originally Posted by AngelSpirit

What are you expecting anyone to do?

Since they're only opcodes the client sends, and there's no server response for them (to my knowledge, at least), the only person who would know exactly what they do is Nexon.

Without even any data in the packets, there's nothing to go by. At most, you could pick apart the client in IDA and see if you could figure it out from there. Not an easy thing to do, though.

---

Is it possible to find receive structure or any data related to it in IDA at all (even if it's not an easy thing to do like you said)? Just curious, still new to it.

Quote:

---

Originally Posted by chunkarama

Is it possible to find receive structure or any data related to it in IDA at all (even if it's not an easy thing to do like you said)? Just curious, still new to it.

---

Structures, yes. You can find those in the client just fine. With a bit more effort and some guesswork you can even use IDA to update recvops from version to version, not just sendops.

This is what a client-send (server recv) packet looks like in IDA:
http://i.imgur.com/4XpvUEP.png
(you'll note that i named my encoders differently because i am a huge faggot)

COutPacket_COutPacket_0 declares the recv header @chunkarama and you can xref it for all the other handlers (excluding the ones from COutPacket_COutPacket and COutPacket_COutPacket_ 1)

Just go to CWvsContext::OnPacket, xref it for CClientSocket::ProcessPacket and find ping (alivereq) and inside it has COutPacket_COutPacket_0 with pong's recv and ez way to find other handlers

@AngelSpirit pls Encode1 4 lyfe