Xkore 2 / Proxy Guide

What is XKore 2 / Proxy?

Step 1: Configuring the XKore 2 Server in Openkore

In config.txt, there are several options that you need to configure in order to make Openkore start an XKore 2 server.

XKore <flag>

Set this option to 2 or proxy to tell Kore that you want to use XKore 2 or XKore Proxy. Check the config.txt section of the manual for further details on the option XKore.

XKore_ID <server name>

Set this option to the name of your game server (e.g. Chaos, Loki, or Sarah). This name will appear on the RO Client when you connect to XKore 2 and you are prompted to choose a server.

Xkore_listenIp <IP address>

If this option is not set, the XKore 2 server will listen to connection requests from any of the installed network devices on your system by default (recommended).

If you have multiple network devices installed on your system and you want to bind the XKore 2 server to a specific network device, set this option to the IP address of the corresponding network device (for advanced users only).

XKore_listenPort <port number>

The value for this option will be the port number that the RO Client will use to connect to the XKore 2 server.

If this option is not set, the Xkore 2 server will listen to connection requests from the port 6900 by default.

If you want to bind the XKore 2 server to a port other than the default (6900), set this option to the chosen port number.

XKore_publicIp <IP address>

The value for this option will be the IP address that the RO Client will use to connect to the XKore 2 server.

If this option is not set, XKore 2 uses the localhost IP address 127.0.0.1 as the default value. You can, therefore, only use an RO Client that will be run on the same computer where Openkore runs to connect to the XKore 2 server using the localhost IP (127.0.0.1).

If you are connected to a network (or the internet) and you want to allow an RO Client that runs on another computer across the network (or the internet) to connect to the XKore 2 server, you must set this option to your computer's IP address.

adminPassword <password>

The value for this option will be used as the login password when the RO Client connects to the XKore 2 server.

Step 2: Configuring the RO Client to connect to XKore 2

• You have to get a copy of your RO Client's account info file (e.g. clientinfo.xml for commercial servers, or sclientinfo.xml for Sakray). It is usually found inside the resource file data.grf (or an equivalent file depending on your Client) and you have to use a GRF extracting utility (like GRF Tool) to extract this file. In other versions of the RO Client, this file can be easily found in a folder named "data" inside the Ragnarok Online installation folder.

• Create a folder named "data" inside the Ragnarok Online folder, if it does not yet exist. Place the account info file in this folder and rename it to xkore2.xml.

• Open the file xkore2.xml using a text editor (e.g. Notepad).

A sample clientinfo.xml file would look like this:

<?xml version="1.0" encoding="euc-kr" ?>
<clientinfo>

	<servicetype>america</servicetype>
	<servertype>primary</servertype>
	<hideaccountlist></hideaccountlist>
	<extendedslot></extendedslot>

	<connection>
		<display>iRO Server</display>
		<desc>None</desc>
		<address>38.144.194.2</address>
		<port>6900</port>
		<version>18</version>
		<langtype>1</langtype>
		<registrationweb>http://enweb.gravity.co.kr/e_regist.htm</registrationweb>
		<aid>
			<admin>1650290</admin><admin>1650292</admin><admin>1650297</admin>
			<admin>1650302</admin><admin>1650306</admin><admin>1650310</admin><admin>1650313</admin>
			<admin>1650315</admin><admin>1650319</admin><admin>1650330</admin><admin>1650296</admin>
			<admin>1650298</admin><admin>1650300</admin><admin>1650303</admin>
			<admin>1650304</admin><admin>1650309</admin><admin>1650312</admin><admin>1650314</admin>
			<admin>1650317</admin><admin>1650320</admin><admin>527214</admin><admin>527215</admin>
		</aid>
		<yellow>
			<admin>1650290</admin><admin>1650292</admin><admin>1650297</admin>
			<admin>1650302</admin><admin>1650306</admin><admin>1650310</admin><admin>1650313</admin>
			<admin>1650315</admin><admin>1650319</admin><admin>1650330</admin><admin>1650296</admin>
			<admin>1650298</admin><admin>1650300</admin><admin>1650303</admin>
			<admin>1650304</admin><admin>1650309</admin><admin>1650312</admin><admin>1650314</admin>
			<admin>1650317</admin><admin>1650320</admin><admin>527214</admin><admin>527215</admin>
		</yellow>
	</connection>
</clientinfo>

• Delete the element passwordencrypt if it exists in this file.

• In the case when there are several connection elements, delete all other connection elements except that which contains a display element describing your server. In the sample clientinfo.xml file above, if your server is "Chaos", delete the first and second connection elements.

• If you will be running Openkore and the RO Client on the same computer, change the content of the address element to the localhost IP address 127.0.0.1 (regardless of the value set in the option XKore_publicIp in Openkore's config.txt).

• Otherwise, if you will be running the RO Client on a different computer, change the content of the address element to the IP address specified in the option XKore_publicIp.

• If the config.txt option XKore_listenPort in Openkore is set, change the content of the port element to the specified value. Otherwise, set it to 6900.

• Save xkore2.xml.

Using the sample clientinfo.xml file above, assuming your server is Chaos and you will be running Openkore and the RO Client on the same computer, the contents of the new xkore2.xml file would look like this:

<?xml version="1.0" encoding="euc-kr" ?>
<clientinfo>

	<servicetype>america</servicetype>
	<servertype>primary</servertype>
	<hideaccountlist></hideaccountlist>
	<extendedslot></extendedslot>

	<connection>
		<display>iRO Server</display>
		<desc>None</desc>
		<address>127.0.0.1</address>
		<port>6900</port>
		<version>18</version>
		<langtype>1</langtype>
		<registrationweb>http://enweb.gravity.co.kr/e_regist.htm</registrationweb>
		<aid>
			<admin>1650290</admin><admin>1650292</admin><admin>1650297</admin>
			<admin>1650302</admin><admin>1650306</admin><admin>1650310</admin><admin>1650313</admin>
			<admin>1650315</admin><admin>1650319</admin><admin>1650330</admin><admin>1650296</admin>
			<admin>1650298</admin><admin>1650300</admin><admin>1650303</admin>
			<admin>1650304</admin><admin>1650309</admin><admin>1650312</admin><admin>1650314</admin>
			<admin>1650317</admin><admin>1650320</admin><admin>527214</admin><admin>527215</admin>
		</aid>
		<yellow>
			<admin>1650290</admin><admin>1650292</admin><admin>1650297</admin>
			<admin>1650302</admin><admin>1650306</admin><admin>1650310</admin><admin>1650313</admin>
			<admin>1650315</admin><admin>1650319</admin><admin>1650330</admin><admin>1650296</admin>
			<admin>1650298</admin><admin>1650300</admin><admin>1650303</admin>
			<admin>1650304</admin><admin>1650309</admin><admin>1650312</admin><admin>1650314</admin>
			<admin>1650317</admin><admin>1650320</admin><admin>527214</admin><admin>527215</admin>
		</yellow>
	</connection>
</clientinfo>

Step 3: Start Openkore

Wait until Openkore fully connects to the map server and into the game.

Step 4: Start the RO Client

Now you have to make the RO Client connect to the XKore server instead of the real RO server. But first, there are several things that you have to check first:

Make sure that:

• The client that you will be using to connect to the XKore 2 server is the same client that you use to connect to the real RO server.
• Game Guard is disabled on the RO Client or it will detect Openkore. Search the forum or google on how to hex your client to disable Game Guard.

To make the RO Client connect to the XKore 2 server, you have to run the RO Client (Ragexe.exe, Pkexe.exe, or Sakexe.exe) with additional command-line arguments. You can achieve this by either creating a shortcut, or a batch file. For simplicity of this guide, batch files will not be discussed here.

• Create a shortcut to Ragexe.exe (or Pkexe.exe/Sakexe.exe).

• Right-click the newly created short-cut and click Properties. In the "Target" field, add the following command-line arguments at the end.

If you are using an executable other than Ragexe.exe or Pkexe.exe, the following is a list of other command-line arguments that you can use in place of 1rag1:

For example, use 1gld1 for gldexe.exe, and 1sak1 for Sakexe.exe.

/account:xkore2.xml

The /account:xkore2.xml command-line argument overrides the filename of the account info file that the RO Client will use. It tells the RO Client to use the file "xkore2.xml" instead of the default "clientinfo.xml".

For example, assuming you're using Ragexe.exe, the Target field in the shortcut properties should read:

Shortcut Target:

"C:\Program Files\Gravity\RagnarokOnline\Ragexe.exe" 1rag1 /account:xkore2.xml

• Run the RO Client using this shortcut.

• Choose your master server.

• Using any username, login with the adminPassword specified in Openkore's config.txt.

• Choose your server.

• Choose your character from the Character Selection Screen.

• Enjoy!