Packets related to packets

[Morpheus]

Rules are:

03 Packet only:
02 03 .....

04 Packet only:
02 04 01 [current counter] [how many RPC in this block] [RPC] [RPC]...

04 with several subpackets:
02 04 0N [counter1] [how many RPC inside this block1] [RPC1][RPC1] .... [counter2][how many RPC inside this block2] [RPC2][RPC2] ... till N

Mixed 03 + 04:
02 03 ......... 00 00 04 0N [counter1] [how many RPC inside this block1] [RPC1][RPC1] .... [counter2][how many RPC inside this block2] [RPC2][RPC2] ... till N

TImed packets (Adjusting client<->server timer):
82 XX XX XX XX 03
82 XX XX XX XX 04
82 XX XX XX XX 03 .... 04

Ignore the first 5 values (timer indicator + time) and replace with a "02", which gives you the same rules as above.


Related example posted above is:

02 04 01 00 1d 01 2f 47 00 00 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1a 00 06 00 00 00 01 00 00 00 00 01 01 00 00 00 00 00 80 00 00 00 00 00 00 00 00

which turns into:

Packet structure:

02 04 -> 04 packet / RPC packet
01 -> 1 block inside
00 1d -> till now, "00 1d" blocks sent (aka MsgBlock Counter)
01 -> 1 RPC inside this block only
2f -> block length (2Fh in hex)

Packet Data:
Header: 47h . Should be 80xx BUT only for values above 80h itself (if i'm not wrong), so this, 47h is under 80h, hence, only 1 byte.
Rest: RPC data & values.

As we sent 1 RPC, the next counter we put in the packets OR the next counter we will find will be "00 1d" + 01 ==> "00 1e".