Configure the Season 6 Episode 3 client

Prepare a clean client

Use the client and patch from the same server release. An unrelated main.exe or DLL can fail even with the correct IP.

• Keep the original archive and a separate test copy.
• Complete server connections and record the ConnectServer TCP port.
• Run the client on a Windows player PC with the required runtime components.

Match the package layout

Current Kantru source uses DataServer.ini and AllowedIPList.xml beside DataServer, ConnectServer.ini and ServerList.xml beside ConnectServer, and Data\Server\MapServerInfo.xml. Older Season 6 packages instead use IGCDS.ini, IGC_AllowedIPList.xml, IGCCS.ini, IGC_ServerList.xml, and IGCData\IGC_MapServerInfo.xml. Use the set shipped with your executable; renaming files does not upgrade a package. Numbered service folders in these examples refer to the corresponding folder in your installation.

1. Apply the release patch

1. Extract the full client to a new folder. Copy the matching Client Patch contents into its root, merging Data folders and replacing the intended files.
2. Confirm main.exe and supplied DLLs are in the client root, not inside an extra Client Patch folder.
3. Back up Data\Local\ServerInfo.bmd. Edit the accompanying ServerInfo.xml if supplied; otherwise open the BMD with the release’s dedicated ServerInfo editor.

2. Enter connection details

1. Set Connection IP to the address reachable from the player PC: LAN IPv4 for local-network testing or public IPv4 for Internet testing.
2. Set Connection Port to TCP_PORT in 2. ConnectServer\ConnectServer.ini, normally 44405. Do not use GameServer’s 56900 here.
3. Match Version and Serial to the server release. In the XML layout, these are in the ServerInfo entry of MapServerInfo.xml. Preserve the n.nn.nn version format and exact serial characters.
4. Keep the release’s other launcher and compatibility settings unchanged for the first test. Enable optional launchers only when they are part of your installation.

3. Save the runtime file

1. For XML-based configuration, encode the XML to BMD. Editing XML alone does not update the client.
2. Copy the generated ServerInfo.bmd to Data\Local. With a dedicated BMD editor, use Save to write that file instead.
3. Close the client, then launch the patched copy from its own folder. Test with a game account created by the package’s compatible account tool. A Kantru website account is separate.

4. Verify the login path

• Server list appears: the client reaches ConnectServer.
• Channel selection succeeds: the advertised GameServer address and TCP port are reachable.
• Account login succeeds: the account exists in DataServer’s configured account database and uses its expected password format.
• Character enters the world and reconnects: client files and stored character data are compatible.
• Failure before the list: inspect client destination and ConnectServer listener. Failure after channel selection: inspect the GameServer address/port. Version error: compare the release pair and regenerate the BMD.

Continue

Next: Configure firewall access.

Reference: IGCN — Client configuration. These instructions use the Season 6 file layout; keep configuration files and tools from the same release.