How I can study the packets?

Triedge

New member
Messages
199
Points
0
I want to use the 2015 Client.
But I have seen that there are certain errors.

I have been to modify clif.c to fix some minor problems.

But there are bugs that remain and need to be able to read the packets that are sent and received by the emulator.

Try using Peek, but there is an error that I can not use it.

I wonder if there any programs or tools that allow me to know how the work packets.

 
actually you need to know how to code in order to be able to make 2015 client work "100%", take a look at the implementation of the roulette system, lots of code where added in order to fully support it, the packet part is just "a bit" of the whole work that need to be done
default_tongue.png


 
actually you need to know how to code in order to be able to make 2015 client work "100%", take a look at the implementation of the roulette system, lots of code where added in order to fully support it, the packet part is just "a bit" of the whole work that need to be done
default_tongue.png
CRASH with multi-quest list in login.

CRASH with Feed a Pet and have 2 o more Foot for Pets.

Several Bugs in Vending of the Merchants....

 
actually you need to know how to code in order to be able to make 2015 client work "100%", take a look at the implementation of the roulette system, lots of code where added in order to fully support it, the packet part is just "a bit" of the whole work that need to be done
default_tongue.png
CRASH with multi-quest list in login.CRASH with Feed a Pet and have 2 o more Foot for Pets.

Several Bugs in Vending of the Merchants....
All items bug are related to a single thing, quest bug , is a minor change in packet.I don't know what's causing pet feed to crash...

 
All items bug are related to a single thing, quest bug , is a minor change in packet.I don't know what's causing pet feed to crash...
in msgstringtable.txt

search:

Feeding the pet. %d '%s' remaining#

change for:

Feeding the pet.#

Bug "Fix".

 
PLEASE, my server carries Vending weeks without being able to use this bug.

I can not go back to the old client, there is another unknown bug that causes crash when trying to use old customers in the server.

I just need to tell me what tools should I use to fix the problem on my own, that's all.

Please....

 
All items bug are related to a single thing, quest bug , is a minor change in packet.I don't know what's causing pet feed to crash...
in msgstringtable.txt

search:

Feeding the pet. %d '%s' remaining#

change for:

Feeding the pet.#

Bug "Fix".
Not really. Not to mention, you could of just changed it to:

Feeding the pet %d - %s remaining#

 
Last edited by a moderator:
All items bug are related to a single thing, quest bug , is a minor change in packet.I don't know what's causing pet feed to crash...
in msgstringtable.txt

search:

Feeding the pet. %d '%s' remaining#

change for:

Feeding the pet.#

Bug "Fix".
Not really. Not to mention, you could of just changed it to:

Feeding the pet %d - %s remaining#
PLEASE, my server carries Vending weeks without being able to use this bug.

I can not go back to the old client, there is another unknown bug that causes crash when trying to use old customers in the server.

I just need to tell me what tools should I use to fix the problem on my own, that's all.

Please....

 
Use PEEK or any to get info from kRO,

however you can only study server->client packets.

You can only study client->server packet only if you know how to decrypt them, since they are encrypted.

But whichever tool you use , you need to modify it according to client.

Or simply you can make your basic packet thing, by changing ws32_2.dll and hooking its send/receive functions and let it output to file/console.

And then later check what packets were send and study them.

Although , you really made a risky decision for changing to 2015 client at production server.

 
Last edited by a moderator:
Use PEEK or any to get info from kRO,

however you can only study server->client packets.

You can only study client->server packet only if you know how to decrypt them, since they are encrypted.

But whichever tool you use , you need to modify it according to client.

Or simply you can make your basic packet thing, by changing ws32_2.dll and hooking its send/receive functions and let it output to file/console.

And then later check what packets were send and study them.

Although , you really made a risky decision for changing to 2015 client at production server.
Peek error: http://herc.ws/board/topic/4912-peek-successor-to-yommys-packet-analyzer/?p=60392

 
Back
Top