Change drops, EXP and restrictions on one map
Each row is one map. Edit the active Data/MapManager.txt for the owning role, regardless of whether profile 603 or 621 is selected.
The outcome to aim for
- Distinguish percent multipliers from million-unit quality checks.
- Edit the active global map row while preserving its other columns.
- Control test conditions instead of assuming a short loot sample proves a probability.
Before you start
Use Data/MapManager.txt under the correct role, not a Move/Profiles copy. Preserve all unchanged columns.
Files you need
Understand the fields
| Field | Meaning & dependencies |
|---|---|
Index | Map ID: choose the row for your target map. |
ItemDrop | Multiplier percent: 100 = ×1, 200 = ×2, 1000 = ×10. |
ExcDrop / SetDrop | Out of 1,000,000: 1000 = 0.1%, 100000 = 10%. Eligible equipment checks still apply. |
SockDrop | 0 excludes normal socket candidates; 1 permits eligible candidates. |
ExpRate | Map EXP scaling, combined with other account/event/party settings. |
DeathGate | A valid gate in the selected movement profile. |
One step at a time
- STEP 1
Find the row by Index and map comment. Copy the original row to your external backup; keep the original column order.
- STEP 2
To double the map multiplier relative to normal, set ItemDrop to 200. If its old value was 1000, changing it to 200 reduces that multiplier from ×10 to ×2.
- STEP 3
Set ExcDrop and SetDrop independently using the million-unit scale. SockDrop=1 allows eligible socket candidates; it does not guarantee sockets or a socket drop.
- STEP 4
ExpRate changes map EXP scaling. Helper, CustAtt, CustStore, CustPick and Trade control the corresponding map permissions. DeathGate must refer to a valid gate. Keep unneeded values unchanged.
- STEP 5
Apply with /reload common on the affected role. Test ordinary equipment, an explicit jewel rule and a box reward separately.
Progress is saved only in this browser. Completion is your learning record, not proof of a live server change.
Configuration example
Keep the existing root/sections and unrelated rows. This example is not a complete original or a full replacement file.
// Index NonPK ViewRange ExpRate ItemDrop ExcDrop SetDrop SockDrop Helper Gens CustAtt CustStore CustPick PkDrop Trade DeathGate Name
0 * 12 100 200 10000 0 0 1 0 1 1 1 0 1 17 "Lorencia"
endWhat changed?
In the default Lorencia demonstration, ItemDrop changes from 1000 (×10) to 200 (×2), while ExcDrop changes from 1000 (0.1%) to 10000 (1%) at its eligible quality check. The lower ItemDrop value reduces that multiplier.
The lab names changed fields and keeps the example separate from your real configuration.
Open this demonstrationApply the real change
Edit the existing row in the owning role’s Data/MapManager.txt. Do not append a duplicate map ID. Use /reload common on each changed role.
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.
If something goes wrong
No change
Check the root Data copy, owning subserver and /reload common. Profile copies do not override it.
Loot does not match the percentage
ItemDrop is a multiplier. Excellent/Set use million-unit checks on eligible loot; dedicated rewards have other paths.
Dependencies & important details
Ancient is checked before Excellent in the ordinary equipment path. Raising both to 100% does not mean both qualities will be placed on every item. Monster level and item eligibility still matter.