Packet Length Extractor: Difference between revisions

From OpenKore Wiki
Jump to navigation Jump to search
(→‎Packet Extractor: oops, turns out v1 is the older version :P)
(→‎Packet Extractor v3: replacing sketchy download link with github)
Line 33: Line 33:
== Packet Extractor v3 ==
== Packet Extractor v3 ==


* [http://dfiles.ru/files/pspbhe6cb Packet Extractor v3]
* [https://github.com/OpenKore/packet-extractor Packet Extractor v3]
* Also in [http://sourceforge.net/p/openkore/code/HEAD/tree/packet-extracter/trunk/ OpenKore SVN]. (See [http://forums.openkore.com/viewtopic.php?f=36&t=13305 kLab's forum post on Open Packet Extractor for more details.])
* Mirror: [http://sourceforge.net/p/openkore/code/HEAD/tree/packet-extracter/trunk/ OpenKore SVN]. (See [http://forums.openkore.com/viewtopic.php?f=36&t=13305 kLab's forum post on Open Packet Extractor for more details.])


Packet extractor branch to work with new insert server list here clients.
Packet extractor branch to work with new insert server list here clients.

Revision as of 13:01, 3 March 2016

If you're having server problems, such as:

  • Packet Tokenizer: Unknown switch: xxxx
  • Getting disconnected after a few seconds
  • NPCs, players and monsters are not recognized by Kore (shown as Unknown)

Then generating a new recvpackets.txt might solve the problem. It's advisable to always extract the recvpackets before running Openkore. The file must be on tables folder.

The network data that the server sends to Kore, is a byte stream. Kore must be able to recognize messages inside that byte stream to be able to do something with it. But the size of the messages can vary from to server to server. Recvpackets.txt contains information about the size of each message, so Kore can correctly split the byte stream into messages.

RO Tools

It's better to use JCV's RO Tools as it is more up to date and have some fixes for newer clients. Also it's much easier to maintain, but it has undesirable and outdated options in addition to the Openkore packet extractor.

Usage

  1. Open RO Tools.
  2. Click in the button with ... beside the box. Search for your's server executable (not server patcher and not launcher !!!) and open it.
    File:button.PNG
  3. On Extractor Type, check Full Disarm box.
    File:full.PNG
  4. Click on Start button and wait it to finish.
    File:start.PNG
  5. After it finishes, it will ask for you to save the file. Save it on tables folder, inside your Openkore's root folder. Override current file if needed.

Packet Extractor

Usage

  1. Run openkore-packet-length-extractor.exe
  2. Click in the button with ... beside the box. Search for your's server executable (not server patcher) and open it.
  3. Click on Extract button and wait it to finish.

Packet Extractor v3

Packet extractor branch to work with new insert server list here clients.

Usage

Variant 1 (for noobs):

  1. Download start.exe from http://misc.openkore.com and unpack to the same folder where packet_extract.pl is placed.
  2. Copy target .exe file to the same folder where packet_extract.pl is placed.
  3. Run packet_extract.bat to save extracted packets to text file.

Variant 2 (for profi):

  1. Download start.exe from http://misc.openkore.com and unpack to the same folder where packet_extract.pl is placed (optional).
  2. Copy target .exe file to the same folder where packet_extract.pl is placed.
  3. Run start.exe ! packet_extract.pl your_exe_name.exe or perl packet_extract.pl your_exe_name.exe to generate "extractor.exe".
  4. Run extractor.exe > recvpackets.txt to save extracted packets to text file.

Notes

  • Recvpackets file can be renamed as long as recvpackets option on servers.txt is set accordingly. (See Connectivity Guide)
  • There may be problems extracting the recvpackets if your server's client has some kind of protection. You should deal with it (like unpack if binary is packed) before using packet extractor, if it fails to find anything.