Guilds, parties, trading and PK rules
Global switches and map restrictions both affect player permissions. Enable a feature globally and on the intended map, then check account and guild requirements.
The outcome to aim for
Global switches and map restrictions both affect player permissions. Enable a feature globally and on the intended map, then check account and guild requirements.
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
TradeSwitch and PersonalShopSwitch are global controls; MapManager Trade and CustStore add map-specific restrictions. Test both transaction participants.
- STEP 2
GuildCreateSwitch/DeleteSwitch, GuildCreateMinLevel and alliance/member limits control guild operations. GuildWarehouseEnable is a separate Custom.ini feature.
- STEP 3
Party experience fields and level difference limits affect group play. Test two accounts with different levels and reconnect behavior.
- STEP 4
PK safety and item loss are separate settings. Review MapManager NonPK/PkDrop and Common.ini PkItemDrop settings together before opening a PvP map.
- STEP 5
Apply the relevant common/custom/util reload and test creation, rejection, trade completion, cancellation and relog 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.