Configure Chaos Machine, jewels and custom recipes
A mix needs an activation switch, valid materials, a cost, a success policy and an output. Client display alone does not determine success.
The outcome to aim for
A mix needs an activation switch, valid materials, a cost, a success policy and an output. Client display alone does not determine success.
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 +10..+15 upgrades, pair each PlusItemLevelXXSwitch with the corresponding PlusItemLevelMixRate1..6_AL0..AL3 rates.
- STEP 2
Change only the intended account tier. Luck, extra jewels and other rules can affect the final result, so the configured base rate is not necessarily the displayed final rate.
- STEP 3
For custom recipes, keep the same recipe ID across all numbered sections: price/rates, material groups, required items and outputs. Copy a complete working recipe rather than one isolated row.
- STEP 4
Verify failure behavior, option retention and material consumption before enabling a recipe for players. Do not interpret every -1 or every Rate as the same rule.
- STEP 5
Use /reload chaosmix for base mix rates, /reload custom for custom tables and /reload spk for MOMU XML refinement systems. Test success and failure paths with disposable items.
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.