Make a change, apply it and roll it back
Use this procedure for every edit. It separates a text edit from a successful gameplay change and gives you a reliable way back.
The outcome to aim for
Use this procedure for every edit. It separates a text edit from a successful gameplay change and gives you a reliable way back.
Success check: A successful file load and a visible in-game result are both required. For currencies, record balances and item counts before and after.
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
This chapter is an operating procedure. Its steps identify when to use the related task and file references.
One step at a time
- STEP 1
Write down the goal, affected subserver, filenames and expected before/after result. Example: make one Lorencia spot contain 8 monsters instead of 4.
- STEP 2
Copy the original affected files to a dated backup folder outside the folders the server scans. For SQL changes, also take a database backup and confirm the correct database.
- STEP 3
Edit one system at a time. Preserve the file encoding, section names, XML tags, quoted strings and column count. Save only when the editor shows the intended file path.
- STEP 4
Use the documented targeted reload on the affected role. If the setting is read only at startup, schedule a controlled restart. Avoid broad reloads while events, matches or transactions are active.
- STEP 5
Read the first relevant load error, log in with a test account, and perform both an allowed and a rejected action. Record the observed result and the time.
- STEP 6
If the result is wrong, restore the original files, repeat the same reload/restart, and repeat the test. Do not stack more edits on top of an unexplained failure.
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
A successful file load and a visible in-game result are both required. For currencies, record balances and item counts before and after.
If the expected result is missing, restore the backed-up files and repeat the same reload/restart before adding another change.