Castle Siege Point System - Aug 17 Updates
Posted on May 10,2018 at 08:59
Dear Muphizens,

Castle Siege event has been designed decades ago and its current system failed to use the 2 hrs duration meaningful, most of the actual event only happened on its last 2 to 5 minutes. 

This is really a great event so it will be a waste if the actual fight will be within few minutes only. Now we will attempt to make this event more alive and try to have the 2 hours of event meaningful, if this succeeded then it will be our new Castle Siege mechanics. With that said, our incoming Castle Siege event will have now the Point System, basically the alliance with more points will win the event and not the one who sealed last...

Point System Mechanic
  • The Castle Owner (defender) will have an initial of 10 points.
  • Each successful sealing will award 25 points to the alliance.
  • Killing the main Guild Master of the defending alliance  by the opposing NON-GM member inside the throne will award 1 point to the alliance.
  • Killing the main Guild Master of the defending alliance  by any Guild Master of opposing alliance inside the throne will award 3 point to the alliance.
  • Killing the main Guild Master of the attacking alliance by any NON-GM member of the defending alliance inside the throne will award 1 point to the alliance.
  • Killing the main Guild Master of the attacking alliance by any Guild Master of the defending alliance inside the throne will award 3 points to the alliance.
  • Killing the main Guild Master of the attacking alliance by any member of another attacking alliance will not award you point.
  • After 10 minutes when the Castle Siege event started, defender will get 5 points every 3 minutes. The 3 minutes defending rule will also apply to every alliance who will seal the crown.  (eX Season 10)
  • After 30 minutes when the Castle Siege event started, defender will get 5 points every 3 minutes. The 3 minutes defending rule will also apply to every alliance who will seal the crown.  (Classic Season 2)
  • The alliance who will seal last will get a bonus of 15 points.
Total Points
  • The alliance with the highest points will be declared winner.

TieBreaker (Total member count basis)
  • If 2 or more alliance got the same points, the alliance with most members online in the Castle Siege map will be declared winner.
TieBreaker (SOL registered basis)
  • The current owner of the Castle will be the default winner.
  • if still 2 or more alliance still got the same points and none of them is the current owner of Castle, the alliance with most SOL registered will be declared winner.
Accumulated Investment Time Reset
  • The same old rule will apply but now the accumulated time will be cleared to 0 when the elapse time since the Guild Master seal attempt is more than 2 minutes. 

Notifications
  • The initial alliance points will be shown when the event started.
  • The alliance points will be shown every 10 minutes.
  • When the GM is killed inside the throne, info will be shown.
  • A notice will be shown stating the defender every 3 minutes points rule timer has started.
  • Final points will be shown when the event ended.
  • When the accumulated time is cleared due to elapse limit, a message will be sent to main Guild Master of the alliance.

SOL Trading

Starting on May 11 (after the maintenance) sign of lord (SOL) will not be tradeable, sellable and moveable anymore, what you can only do is register this item to the event NPC.


Notes
  1. Updated/added mechanics highlighted in green above. Last updated on August 17, 7:00 pm.
  2. If we notice you are killing a dummy GM to score, your main GM of your alliance will be banned and the right to own the castle will be removed.
  3. This is our initial designed mechanic, adjustments might be applied when fitted or necessary. 
  4. We failed to test this new mechanic due to required numbers of characters needed, we will fire it up live on Friday (Classic) and Saturday (eX), now we be monitoring the event and when we found a critical error we will proceed with the old mechanic.
  5. Please bear with us if a crash in the event occured, we did review our codes many times to avoid this, if ever this happened then we will re-schedule the event in the earliest time.

MUPH Management