Pets, Muun life, mounts and bonuses
Separate pet registration, life/feeding, bonus conditions and mount quests. Server behavior and client descriptions must agree.
The outcome to aim for
Separate pet registration, life/feeding, bonus conditions and mount quests. Server behavior and client descriptions must agree.
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
MomuPetOption defines effects, scope, conditions and pet groups. Preserve its numbered sections and use the file’s Effect/Scope/Cond legend. Do not treat an effect ID as a raw percentage.
- STEP 2
Group 1 is helper pet, 2 is Muun and 3 is mount in this table. One pet per group applies, and the MINI slot has precedence over slot 8. Verify the actual equipped combination.
- STEP 3
Keep the equivalent MomuPetOption server tables and the client Data/Custom/MomuPetOption.txt display copy identical when distributing a change. /reload custom refreshes online bonuses in this version.
- STEP 4
MuunPetLife handles life/feeding-related data; keep the complete row layout. Use /reload muunpet only after checking the entries. Test an exhausted pet, feeding, swapping and removal.
- STEP 5
GiantMountQuest uses Enable, stage timers, BossClass and packed reward item IDs. Confirm the boss and reward items exist before enabling the quest.
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.