Castle Siege, Crywolf and Castle Deep
These systems depend on the GSCS role and map ownership. Do not enable an event on both roles merely to make it appear.
The outcome to aim for
These systems depend on the GSCS role and map ownership. Do not enable an event on both roles merely to make it appear.
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
CastleSiegeEvent enables the siege system. MuCastleData.ini supplies its cycle/state schedule. Keep automatic weekly scheduling separate from manually forced states.
- STEP 2
The supplied schedule comments assume a Sunday cycle start and a Saturday siege. Replace old literal dates with a planned cycle and verify day offsets; copying an old date blindly is unsafe.
- STEP 3
CrywolfEvent and CastleDeepEvent control their systems. Crywolf benefits and penalties can affect EXP, jewels and monster life; inspect those values as part of economy tuning.
- STEP 4
Confirm map ownership, valid gates, required NPCs and event monster templates on GSCS before testing entry.
- STEP 5
Apply event changes in maintenance. Test the sequence from waiting to active to completion, including winner/benefit state and reconnect after restart.
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.