Encode and decode client configuration

Choose the correct converter

This covers XML configuration such as ServerInfo.xml. Models and binary tables also use .bmd; they do not all use this converter.

• Back up the original XML and BMD outside the client folder.
• Use the ToolKit or ServerInfo editor supplied for the same release. For a dedicated BMD editor, use its Open/Save workflow.
• Keep the release’s conversion password. It is a file-format key, not a game or SQL account password.

1. Edit the XML

1. Open a working copy in Notepad++. Change only intended attributes; preserve the root and closing tags.
2. Retain the supplied Password attribute for the first conversion. The generic IGC XML converter uses its own eight-character key; a dedicated ServerInfo format may differ. Do not pad or replace a key merely to suppress an error.
3. Escape XML-sensitive characters, including & as & in attribute values. Save without changing the expected encoding.
4. For connection changes, compare IP, Port, Version, and Serial with Client setup.

2. Encode and install

1. In the matching ToolKit, choose IGC File Enc/Dec (XML) for generic encrypted XML, or BMD Files → [IGC] ServerInfo (XML) for the dedicated ServerInfo format.
2. If the selected tool has a Password field, enter the file-format key. Drop the edited XML onto Encode or use the offered file picker.
3. Wait for success and locate the generated BMD. Confirm its timestamp changed. Renaming .xml to .bmd does not encode it.
4. Copy the output to the loaded path, normally Data\Local\ServerInfo.bmd. Keep the source XML and converter version outside the distributed patch.

3. Verify the round trip

1. Decode a copy of the generated BMD with the same converter and key into a separate folder. Do not overwrite your working XML.
2. Compare the decoded values with your intended edits. If decoding fails, check converter type, release preset, and key.
3. Restart the client and test the changed behavior, such as connection destination.
4. Distribute the tested BMD and required patch assets together. Exclude internal server configuration and private working files.

If the change is ignored

• Check the BMD is inside the client folder you actually launched.
• Check the output timestamp; failed conversion may leave an older file in place.
• If an updater replaces the BMD, update its patch source too.
• If the tool cannot decode the original file, obtain the release-compatible converter through Support, providing filename and release version.

Continue

Next: Test the client.

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