Export client data with GetMainInfo
GetMainInfo converts its supported settings and tables into client data. The tool’s input is not the same as the GameServer gameplay configuration.
The outcome to aim for
GetMainInfo converts its supported settings and tables into client data. The tool’s input is not the same as the GameServer gameplay configuration.
Before you start
Read the complete procedure and its version notes. Record the affected server role and keep an untouched backup outside scanned data folders.
Files you need
One step at a time
- STEP 1
Use the owner’s primary GetMain folder, preserve its GetEngine.ini and inspect the relevant Data table before editing. Do not replace private settings with a guide example.
- STEP 2
Run GetMainInfo normally. The supplied standalone workflow exports PREMIUM/ServerData.bmd beside the tool and does not require a complete game client on the dedicated server.
- STEP 3
Copy the generated file to the actual client Data/Local/MOMU, then restart the client. If enabled executable/plugin checksums changed, refresh them using the owner’s settings.
- STEP 4
Custom wings, pets and item visuals can need client models/textures, registration tables and matching server behavior. Editing one table alone does not supply missing artwork.
- STEP 5
Test with the distributed client, not only the encoder machine. Verify connection, item name, model, effect, tooltip and server-side use.
Progress is saved only in this browser. Completion is your learning record, not proof of a live server change.
Apply the real change
Use the load method stated in the steps for this system. Startup-only settings require a planned restart. The reload finder below shows recorded groups; confirm whether the particular field is startup-only.
Find the file’s reload instructions →Verify the result in game
If the expected result is missing, restore the backed-up files and repeat the same reload/restart before adding another change.