Wrong sequence when sending packets to world server

10/08/2022 12:03 Skyyrize#1
Hello, I am writing this topic today to ask you for help in understanding how sending packets on the world server works.

In my research to find out what was the procedure for sending packets to the world server, I understood that it was necessary to generate a number and to increment it with each new packet to send.
cf: [Only registered and activated users can see links. Click Here To Register...]

To verify this functional, I created a man in the middle between the client and the server to intercept the packets sent

But, as you can see from the code below, the number sequences don't follow each other for the first 3 packets.

Code:
session 38511
[WORLD CLIENT] b'54039 38511'
[WORLD CLIENT] b'54040 FR_ACCOUNTNAME GF 2'
[WORLD CLIENT] b'54042 c_close 0'
[WORLD CLIENT] b'54045 0'
[WORLD CLIENT] b'54046 0'
[WORLD CLIENT] b'54047 0'
We jump from 54040 to 54042 to continue with 54045, so there is a problem.

My question is therefore, why this behavior of skipping a sequence and what is the reason for this

Another question, what is this packet 0 which is sent every 10 seconds?

Thank you for your answers
10/08/2022 14:30 Hatz~#2
Quote:
Originally Posted by Skyyrize View Post
Hello, I am writing this topic today to ask you for help in understanding how sending packets on the world server works.

In my research to find out what was the procedure for sending packets to the world server, I understood that it was necessary to generate a number and to increment it with each new packet to send.
cf: [Only registered and activated users can see links. Click Here To Register...]

To verify this functional, I created a man in the middle between the client and the server to intercept the packets sent

But, as you can see from the code below, the number sequences don't follow each other for the first 3 packets.

Code:
session 38511
[WORLD CLIENT] b'54039 38511'
[WORLD CLIENT] b'54040 FR_ACCOUNTNAME GF 2'
[WORLD CLIENT] b'54042 c_close 0'
[WORLD CLIENT] b'54045 0'
[WORLD CLIENT] b'54046 0'
[WORLD CLIENT] b'54047 0'
We jump from 54040 to 54042 to continue with 54045, so there is a problem.

My question is therefore, why this behavior of skipping a sequence and what is the reason for this

Another question, what is this packet 0 which is sent every 10 seconds?

Thank you for your answers
When you receive data from the socket you can get multiple packets in the same call so you must handle that and split them, that's why you see the numbers are not incrementing as you expected. The 0 packet is probably there to make sure the connection is alive.
10/09/2022 15:28 ZroIsHere#3
Quote:
Originally Posted by Skyyrize View Post
Hello, I am writing this topic today to ask you for help in understanding how sending packets on the world server works.

In my research to find out what was the procedure for sending packets to the world server, I understood that it was necessary to generate a number and to increment it with each new packet to send.
cf: [Only registered and activated users can see links. Click Here To Register...]

To verify this functional, I created a man in the middle between the client and the server to intercept the packets sent

But, as you can see from the code below, the number sequences don't follow each other for the first 3 packets.

Code:
session 38511
[WORLD CLIENT] b'54039 38511'
[WORLD CLIENT] b'54040 FR_ACCOUNTNAME GF 2'
[WORLD CLIENT] b'54042 c_close 0'
[WORLD CLIENT] b'54045 0'
[WORLD CLIENT] b'54046 0'
[WORLD CLIENT] b'54047 0'
We jump from 54040 to 54042 to continue with 54045, so there is a problem.

My question is therefore, why this behavior of skipping a sequence and what is the reason for this

Another question, what is this packet 0 which is sent every 10 seconds?

Thank you for your answers
U received 2 or more packets in the same call, need do a split after all the unencrypt system with (char)0xFF that return an string array and handler the array

Probably the code take error and for this dont display it
10/09/2022 19:27 Skyyrize#4
Thank you for your answers, I would never have guessed that.