Database scripts, account creation and migrations
SQL files are executable operations, not editable game balance tables. Some add schema; some alter data or clean a template. Read the actual script before running it.
The outcome to aim for
SQL files are executable operations, not editable game balance tables. Some add schema; some alter data or clean a template. Read the actual script before running it.
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
Confirm the SQL server, target database and backup restore procedure. Keep connection credentials outside customer-facing documentation.
- STEP 2
Use DB/Diagnostics/MOMU_Ranking_SQL_Diagnostic.sql to investigate ranking connectivity according to its instructions. Distinguish diagnostic SELECT statements from schema/data-changing statements.
- STEP 3
For a migration, read its prerequisites and compare existing tables/columns before applying it. A date in the filename is not a command to execute all files in order.
- STEP 4
CreateAccount.sql is for a deliberate account-creation operation. CleanCustomerTemplate and non-reset scripts can change existing data; never run them merely because they are present.
- STEP 5
After migration, start the matching DataServer first, inspect SQL errors, test login/save/ranking or the specific new system, and record the applied migration.
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.