Use editors and optional tools deliberately
The Tool folder includes different applications. Their settings can point to separate databases or client directories; confirm the target before saving.
The outcome to aim for
The Tool folder includes different applications. Their settings can point to separate databases or client directories; confirm the target before saving.
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
For account/item editors, use a test account and a database backup. Check that the editor’s item format matches the running server before making permanent items.
- STEP 2
Terrain editors can change walkability and safe areas. Back up the map resource and keep client/server terrain synchronized. Test movement and teleport arrivals after a change.
- STEP 3
NarrationRelay is optional. Follow NARRATION_SETUP.txt; service credentials remain on the owner-hosted service and the client receives only the intended public HTTPS endpoint.
- STEP 4
Logs, database backups, caches, archives and runtime DLLs are not balance tables. Do not edit binary resources as plain text. Use the matching application or replace validated runtime files in maintenance.
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.