Specifications / Collection of Notes

[iMer 184]

So I'm currently looking through the source and finding things which arent immediately clear - mostly the network bit.

 

CPacketInfo

It's purpose is to do two things

1. Profile/Log incoming packets, how long processing them (the analyze call) took.

2. It stores information regarding to packets, f.e. if there are Sequence bytes at the end of that packet.

 

Packets

A packet always consists of:

1 byte Header

x byte Data

optional 1 byte Sequence

 

Db packets always consist of

1 byte Header

4 byte Handle

4 byte Size

x byte Data

 

Sequence Bytes

The sequence bytes/sequence table are a static array of a set size.

For each DESC (network connection basically) it stores the current position in the sequence table DESC::m_iCurrentSequence and the last 10 elements it recieved (those are for logging purposes only and can be safely removed) DESC::m_seq_vector

The sequence byte will always be at the end of a packet.

What packet has sequence bytes is set in CPacketInfo.

Sequence bytess are only used for packets from client to game.

 

 

I thought this would be neat for anyone who's interested in this kind of thing

I'll add more stuff as I find out about it or think of it.

 

[iMer 184]

Desc->BufferedPacket

..is completely useless in the new encryption. (34k+)

[iMer 184]

Fun fact: If your login starts with [ the password is treated as plain text.

Of course you wouldn't even get that far with a [ in the login, but whatever..

Edited August 15, 2022 by Metin2 Dev
Core X - External 2 Internal