Connectivity Guide

From OpenKore Wiki
Revision as of 13:49, 18 August 2010 by Manticora (Talk | contribs) (Syntax)

Jump to: navigation, search

Getting Server Information

OpenKore comes with a list of official servers information only, because of the high amount of private servers, it is impossible to have and keep them updated, so private servers players should follow this guide to get and update their server information.

Before continuing, read the list of unsupported servers. Your server might have anti-bot protection resulting in not being supported by Openkore.

OpenKore needs the following information about the Ragnarok Online server before it can login:

  • The server name
  • The server's host (IP address or hostname) and port
  • The server's master version number
  • The server's server version number (not the same as the master version number)
  • The server's character encoding
  • The server's type version.

There are two ways to collect server information, which is using WPE or Wireshark. Other network sniffers can be used, too.

WPE (Winsock Packet Editor)

1. Download WPE and extract it.

  • Before downloading, make a sure to disable your anti-virus as it can mark WPE as a virus and delete it. Download at your risk, we will not be resposabilized if your computer crashes.
  • You will need some programs to extract it, the common ones are WinRAR and 7zip.

2. Open your ragnarok but don't login yet! Leave it on the login screen and open WPE.

3. At WPE's window, click on Target Programs button.

Targetyc.png

4. A window will open, search for the server's executable and double-click it.

Clickrag.png
Note. Some servers "hide" their executables by renaming it (like from xxxRO.exe to xxxx.dll or xxxxx.bin), so don't worry if the executable isn't a .exe one.

5. In the WPE's window, click on Play button.

Play.png

6. Switch to your Ragnarok's window, put and try to login.

Note. Valid login information are not needed.

7. Back to WPE's window, click on Stop button

Stopjw.png

8. A window will open with some recorded packets. The server's version and master_version, IP and port can be found there. The packets will be different on each server, but most of the time it will start with 64 00. These are the packets that contains the version and master_version. Write them down because they are going to be used later.

Inforb.png
Legend:
  1. version (displayed as 4-byte unsigned number in little-endian, in hex)
  2. IP (as is)
  3. port (as is)
  4. master version (displayed as 1-byte unsigned number, in hex)

9. See Converting Hexadecimal to Decimal numbers to convert the master_version and version before configuring Kore.

Wireshark

1. Download and install Wireshark.

2. Open your ragnarok but don't login yet! Leave it on the login screen and open Wireshark.

3. At Wireshark's window, go to Capture > Options on the upper menu or press Ctrl + K.

Capiture.png

4. In the top right box, select the interface that will be used to capture on. If there isn't any specific interface to use, select the one whose IP address is equal to the your ip address or is not unknown. Alternatively you can try all of them and use the one that records the packets. Set the others settings like the images bellow:

Interface.PNG

5. Click on Start button and go back to the Ragnarok window and login.

Note. Valid information are not needed.

6. Back to Wireshark and click on Stop button.

Stop.png

7. In Wireshark main window, you can see the TCP segments that were captured. Fill in the packet filter, but what to fill in depends on the username you used to login.

Enter this in the "Filter" text box:
eth contains "xxxxxx" or eth contains xxxxxx
Replace xxxxxx with the username that was used to login and press enter. In the example bellow, username was Mushroom.
Filter.png

8. There will be only one entry now, click on it to show some information about it. This is where the IP and port is stored.

Ip.png
Write down the IP and port.

9. On the entry again, right-click on it and go to Follow TCP Stream.

Tcp.png

10. A new window will open, in the bottom left, select Hex Dump.

Hex.png

11. These are the login packets. Take a look at it and write down the packets that contains the version and master version numbers. They are marked on the image bellow.

Packets.png

12. See Converting Hexadecimal to Decimal numbers to convert the master_version and version before configuring Kore.

Converting Hexadecimal to Decimal numbers

Master_version and server version collected from the login packets are in hexadecimal number (base-16) and Kore expects a decimal number (base-10), so converting those numbers are needed before Kore can read them.

Converting can be made using Windows' calculator or any other site that has a hex to dec calculator.

1. Open Windows calculator Start > Accessories > Calculator.

Calc.PNG

2. Go to View on the upper menu and click on Scientific.

Sci.PNG

3. Check the circle beside Hex.

Hexa.PNG

4. On the calculator, type the number that you got for master_version and version. In the example, master_version hexadecimal number is 10.

Type.PNG

5. Check the circle beside Dec.

Dec.PNG

6. After checking, the number shown should automatically be converted from hexadecimal to decimal.

Done.PNG
You must convert master_version and version.

Configuring Openkore

OpenKore reads server information from a file named servers.txt. The file is on tables folder.

If your server is not listed in the file, then add a new entry. If your server is already listed, then modify the existing entry.

Syntax

[<server name>]
ip <number/host>
port <number>
version <number>
master_version <number> 
serverType <serverType name>
serverEncoding <enconding>
charBlockSize <number>

#Following configs are optional
addTableFolders <folder path>
captcha <boolean flag>
chatLangCode <boolean flag>
field_<location> <filename>
clientHash <hex string>
gameGuard <number>
private <boolean flag> 
paddedPackets <boolean flag>
paddedPackets_attackID <packet switches>
paddedPackets_skillUseID <packet switches>
secureLogin <boolean flag>
secureLogin_type <type>
secureLogin_requestCode <hex string>
secureLogin_account <boolean flag>
storageEncryptKey <encrypt key>
recvpackets <file name>

Main configs

[<server name>]
The name of the server that you want to bot. The name must be between [ ].
ip <number/host>
Server's login IP.
port <number>
Server's login port number.
version <number>
Server's version (converted from hex to decimal).
master_version <number>
Server's master_version (converted from hex to decimal).
serverType
Development.pngThe following documentation describes a feature that was greatly changed in SVN trunk (latest development version) since the last release.
It may work differently or not be available if you're using 2.0.7 or any older version.
Server's type. Each official server has its own serverType, private servers must use kRO serverTypes according to executables dates.
serverEncoding
Characters encoding type. The character encoding cannot be automatically detected, but here's a list of possible character encodings that you can use:
Encoding Language used
Western Language which uses a Roman-based alphabet. Example: English, German, French, Portuguese, Indonesian, etc.
Simplified Chinese Simplified Chinese.
Traditional Chinese Traditional Chinese.
Korean Korean
Russian Russian, or a Cyrillic-based language.
Japanese Japanese
Thai Thai
charBlockSize <value>
Configures character block size. Currently known values are 106, 108 or 112, 128 (renewal servers). Set this option if Openkore is having problems showing character name, job and level when selecting the character.


Following configs are optional

addTableFolders <folder path>
Configures Kore to load tables file from the specified path.
The same effect as with --tables argument. kRO serverType uses korean tables by default; for english ones, you can use
addTableFolders tables/translated/kRO_english
or
addTableFolders tables/iRO
captcha <boolean flag>
Configure Kore to use the captcha 'protocol'.
chatLangCode <boolean flag>
Removes language code on messages.
gameGuard <number>
Used for GameGuard and HackShield. See also: Poseidon.
private <boolean flag>
Set this option if Openkore connects to a wrong map-server IP. Usually for private servers.
recvpackets <file name.txt>
Configures file's name for recvpackets. See also: Packet Length Extractor.

Example

[MushroomRO]
ip 127.0.0.1
port 6900
master_version 16
version 20
serverType kRO_RagexeRE_0
charBlockSize 108
serverEncoding Western
recvpackets mush-recvpackets.txt