If you're familiar with Morrighan, you will feel right at home here.

Download

Remember to regularly update PaleTree and Zemyna whenever one is available, as they need to be up-to-date to work with the latest client.

How to use

For Zemyna to be able to read packets, it needs control over the starting process, as it temporarily adjusts your client, to tunnel its connection. It does so by making a backup of your client.xml, that contains information about where to connect to, and creates a new one. This change is reverted once Zemyna closes, this way you don't have to fiddle with any files yourself.

To tell Zemyna where to connect the client to, you use command line parameters. For example, let's say you wanted to log packets on the international server Laima, you would simply start it like this from the command line, after moving Zemyna to your game folder:

Zemyna.exe host:54.88.25.242 port:2000

The IP and port are of the login server for Laima. For easier reusability, you should create a link or bat file. Zemyna will then take the necessary steps to be able to read packets from the network, and start the client. A small window in the upper left corner will show you that Zemyna is running, it closes automatically when the client gets closed. You can also double click it to quickly close Zemyna and the client.

Since you can only have one server in the server list this way, the one you specify in the parameters, you could create multiple links/bats, one for each server.

If you want to use Zemyna on a server that doesn't use the Steam auto-login, but a login interface, you have to tell it, with another parameter. For example, connecting to a local server:

Zemyna.exe host:127.0.0.1 port:2000 nosteam

How to connect to Zemyna

Zemyna uses the same API as the tool it was inspired by, "Alissa". It uses WM_COPY messages to communicate between Zemyna's and the subscriber's window. To subscribe to Zemyna, to receive packets, you send the "op" (dwData) 100 to Zemyna's window (window name: "mod_Tossa"), to unsubscribe, you send 101. While you're subscribed, you receive all incoming (op 0x10101012) and outgoing (op 0x10101011) packets via the same method.

For an actual example on how this works, I suggest looking at the corresponding functions in Pale. Alternatively you can also create a plug-in for Pale, which will be easier.

Restrictions

• Zemyna currently only supports the Login and Channel servers.
• Due to ToS's protocol, Zemyna needs to be updated regularly, or there's a high chance for it not to function correctly. Check for updates after each game patch and report potential issues.

Korean TOS

If you click on Download, you will find multiple versions, one of them being for kTOS (notice the "k" prefix). Choose that one if you want to log packets on the Korean server.

Due to kTOS using a web login, we had to do things a little differently for the Korean version of Zemyna. You need an additional argument, "kr", which activates certain KR only options. Example:

Zemyna.exe host:54.88.25.242 port:2000 kr

After you started Zemyna like that, the client won't start automatically, but it will still modify the client files, so when you finally start the client via the web login, the connection will still go through Zemyna, allowing you to log packets using PaleTree.

Just like its cousin MabiPale, PaleTree allows you to log packets, and save, load, and modify the logs. However, unlike MabiPale, you won't see clear, separated variables here, as ToS's protocol doesn't communicate this information. Instead, PaleTree features a hex editor on the right side, and it has a plugin to show which values might hide behind a bunch of random bytes, starting at the selected index. For deeper analysis, a tool like 010 Binary Editor is recommended.

Another difference to MabiPale, is that due to the availability of op codes, there are no unknown ops, and in case of changes, the ops are saved inside the logs, so you never have to worry about incorrect op names. But you should update PaleTree regularly, since any change in an op could result in confusing data.

Download

Remember to regularly update PaleTree and Zemyna whenever one is available, as they need to be up-to-date to work with the latest client.

Features

• Logging packets
• Saving logs
• Log management (deleting, filtering)
• Plugin system
• Official plugins:
  • Variable Preview: Displays what values could be read from a packet, starting at the selected byte.

How to use

• Put Zemyna.exe into your ToS folder
• Create a link to Zemyna.exe, using parameters for the appropriate server. For example to connect to the international server Laima, you would use Laima's login server IP and port:

  Zemyna.exe host:54.88.25.242 port:2000

  And to connect to a local server, without Steam auto-login, but with a login form, you would use this:

  Zemyna.exe host:127.0.0.1 port:2000 nosteam

• Start the client with that link whenever you want to log packets.
• Click connect in Pale to subscribe to Zemyna's packet broadcast and to start logging packets.

Packet data

The packet data in the hex editor is always the raw data received/sent by the client, incl. packet header. This means the actual values don't start at the first byte.

Packets from the client to the server have a 10 byte header:

short op;
int sequence;
int checksum;

Packets from the server to the client are the same, just without the checksum, so it's 6 bytes in total. Additionally, packets that don't have a fixed size have another short (2 byte) before the actual data, the length of the entire packet. Packets that have a fixed length will say something like "Size: 50 (Table: 50, Garbage: 0)" in the packet information on the right side, after the op, while dynamic packets don't say this (dynamic packets are ones that include lists or variable sized strings, where you can't define a fixed size).

The last thing of note is the potential "garbage" at the end of packets from the client to the server. Because of how the packet encryption works, the length of packets from the client to the server is always a multiple of 8. Packets that have a fixed size will be able to determine that X byte are "garbage", because they don't belong to the actual data, but are a left-overs from the encryption process.

The garbage bytes can generally be ignored, the only reason we don't truncate them is that we could potentially lose data if the ops are outdated.

I spent a .bat file with the commands to open the client -SERVICE

and it is working perfectly, both in the game folder, as a shortcut

Program Bat to Exe Converter

http://www.f2ko.de/downloads/Bat_To_Exe_Converter.zip

Code:

start Client_tos.exe -SERVICE

save the .bat extension,  then just use the program.

If not want to use the program I provide my file \/

extract and place within the folder  Steam\steamapps\common\Tree Of Savior\release

Tree of Savior.rar

Download
Source

Features

• Reads any IPF files, be it iCBT1, 2, or current kTOS/iTOS ones.
• (Fast) extraction of single files, all files in one IPF, or an entire client's data.
• Optional preview for all text, image, and font files.

Limits

• No IPF editing.
• No 3D preview (yet).

http://www.tosbase.com/downloads/IPF_Suite.zip.html

Update: I'm now using my own tool to browse and extract IPFs, IPF Browser.