Relife, wheel, milestones, refinement and exchanges
These systems spend items, stored currencies or progression. Preserve stable IDs and validate both successful and rejected operations before opening them to players.
The outcome to aim for
These systems spend items, stored currencies or progression. Preserve stable IDs and validate both successful and rejected operations before opening them to players.
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
Relife.xml: edit its existing Enabled/Config, level conditions, per-rebirth requirements and rewards together. The supplied BatTat value is not a normal 0/1 example; do not replace it by analogy with another XML system.
- STEP 2
CustomVongQuay.xml: Enable controls the wheel; each VongQuay defines a wheel and its costs, while ItemNhan defines its reward pool. Check cost consumption and the actual weighting rules before changing rates.
- STEP 3
CustomMocNap.xml: each MocNap GiaTriNap is a milestone, with CoinNhan and item rewards. A milestone configuration does not itself implement payment collection; preserve claim history and validate the recorded deposit source.
- STEP 4
DungLuyen.xml: Enable/KeepOptions and each RefineGroup’s Rate/FailType work with MainItem, support items and output rows. Check the local rate scale rather than assuming Rate=300 means 300%.
- STEP 5
ChangeItem.xml: Enable controls exchange availability and its groups define required fees and accepted sets. CustomHarmony has its own Enable, PriceType, Price and Rate, plus separate weapon/staff option pools.
- STEP 6
CustomCongHuong.xml: the actual enable field is Status Enabled, not an invented root Enable. Its NPC uses a placeholder-like map in this copy; verify a real allowed map, location and loader behavior before enabling public use.
- STEP 7
Apply /reload spk during a quiet period or restart in maintenance. Test material shortage, exact materials, inventory full, success, failure, option retention and persistence after relog.
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.