Sky Event, guild bosses and team arenas
Custom events have their own XML schemas. Their NPC, stage times, team or guild requirements and reward definitions must be edited as one system.
The outcome to aim for
Custom events have their own XML schemas. Their NPC, stage times, team or guild requirements and reward definitions must be edited as one system.
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
Sky Event uses Config.xml for stages/schedules/rewards and Monster.ini for its monsters. The supplied loader runs this module on the normal GS role. Verify each level bracket.
- STEP 2
BossGuild.xml combines schedule, guild admission, preparation/battle timing and boss/reward settings. Test two guilds and an unqualified character.
- STEP 3
ThanMaChien.xml configures team-event entry and rewards. Keep internal tag names unchanged and verify kills and winner rewards are not counted twice.
- STEP 4
EventGreatPK.xml and CTCMini have separate score/entry and victory rules. Gate IDs must exist in the active Gate.txt. Do not change winner-state files merely to reschedule an event.
- STEP 5
Use /reload event only when no affected event is active, then run a full entry-to-exit test including timeout and cleanup.
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.