Armageddon - Revision history

Jez at 15:02, 27 March 2025

2025-03-27T15:02:41Z

Jez at 16:22, 30 November 2024

2024-11-30T16:22:28Z

Jez at 16:20, 30 November 2024

2024-11-30T16:20:01Z

Show changes

Sparhawk: /* Guild Force Required to Cast Armageddon */

2017-05-16T23:59:30Z

‎Guild Force Required to Cast Armageddon

Sparhawk: /* Force Required to Cast Armageddon */

2017-03-28T00:48:21Z

‎Force Required to Cast Armageddon

Sparhawk at 00:48, 28 March 2017

2017-03-28T00:48:01Z

Laanders: /* Server vs Player-Casted Armageddon */

2016-03-21T09:25:04Z

‎Server vs Player-Casted Armageddon

Laanders: Server vs players

2016-03-21T09:22:46Z

Server vs players

Laanders: Fixed up time intervals, 12/24 hours.

2015-07-22T08:40:06Z

Fixed up time intervals, 12/24 hours.

Laanders: Updated and cleaned up to reflect new mechanics.

2015-07-09T08:29:33Z

Updated and cleaned up to reflect new mechanics.

Show changes

@@ Line 51: / Line 51: @@
 *Armageddon casters receive pillage protection ("-") according to normal rules.
 *The amount of Volcano Eruptions a mage can be targeted with in a 24 hour (12 on Lightning) period also increases (+1 per seal) as more mages cast Armageddon.
-*A pre-casting mage will be attackable by any non-friendly mage&nbsp;and be affected by the increased protection thresholds from the moment they cast.
+*A pre-casting mage will be attackable by any non-friendly mage&nbsp;and be affected by the increased protection thresholds from the moment they cast. However as for any caster it will not cause a mage to leave damage protection&nbsp;earlier, if in damage protection when pre-casting.
 *Once Armageddon proper begins, no protection (except apprentice) is available for anyone, caster or not.
 *Once cast, Armageddon can neither be cancelled nor dispelled. Serenity, Cancellation, Minor Indulgence, Indulgence from God and Spell Strike will also not affect it. However, Orb of Protection, when used by a caster, will remove the spell and cancel the current casting sequence.

@@ Line 51: / Line 51: @@
 *Armageddon casters receive pillage protection ("-") according to normal rules.
 *The amount of Volcano Eruptions a mage can be targeted with in a 24 hour (12 on Lightning) period also increases (+1 per seal) as more mages cast Armageddon.
-*<s>Pre-casting mages will only be affected by the increased protection thresholds from the time their seal breaks, and not from the time they cast the spell.</s>&nbsp;This has been confirmed to be wrong and will not change. A pre-casting mage will be attackable by any mage and be affected by the increased protection thresholds from the moment they cast.
+*A pre-casting mage will be attackable by any non-friendly mage&nbsp;and be affected by the increased protection thresholds from the moment they cast.
 *Once Armageddon proper begins, no protection (except apprentice) is available for anyone, caster or not.
 *Once cast, Armageddon can neither be cancelled nor dispelled. Serenity, Cancellation, Minor Indulgence, Indulgence from God and Spell Strike will also not affect it. However, Orb of Protection, when used by a caster, will remove the spell and cancel the current casting sequence.

@@ Line 50: / Line 50: @@
 ==Guild Force Required to Cast Armageddon==
-*GuildWar: The Guild Force Required to cast Armageddon on GuildWar Server starts at 2,000 Guild Force and drops by 30 every day. For example, after the server is 10 days old, the required Guild Force to cast Armageddon drops by 300, to 1700 Guild Force.
+*GuildWar/Blitz/Beta: The Guild Force Required to cast Armageddon on GuildWar/Blitz/Beta Server starts at 2,000 Guild Force and drops by 30 every day. For example, after the server is 10 days old, the required Guild Force to cast Armageddon drops by 300, to 1700 Guild Force.
 ==Example==

@@ Line 48: / Line 48: @@
 *Once cast, Armageddon can neither be cancelled nor dispelled. Serenity, Cancellation, Minor Indulgence, Indulgence from God and Spell Strike will also not affect it. However, Orb of Protection, when used by a caster, will remove the spell and cancel the current casting sequence.
-==Force Required to Cast Armageddon==
+==Guild Force Required to Cast Armageddon==
 *GuildWar: The Guild Force Required to cast Armageddon on GuildWar Server starts at 2,000 Guild Force and drops by 30 every day. For example, after the server is 10 days old, the required Guild Force to cast Armageddon drops by 300, to 1700 Guild Force.

← Older revision		Revision as of 00:48, 28 March 2017
Line 48:		Line 48:
	*Once cast, Armageddon can neither be cancelled nor dispelled. Serenity, Cancellation, Minor Indulgence, Indulgence from God and Spell Strike will also not affect it. However, Orb of Protection, when used by a caster, will remove the spell and cancel the current casting sequence.		*Once cast, Armageddon can neither be cancelled nor dispelled. Serenity, Cancellation, Minor Indulgence, Indulgence from God and Spell Strike will also not affect it. However, Orb of Protection, when used by a caster, will remove the spell and cancel the current casting sequence.

		+	==Force Required to Cast Armageddon==
		+
		+	*GuildWar: The Guild Force Required to cast Armageddon on GuildWar Server starts at 2,000 Guild Force and drops by 30 every day. For example, after the server is 10 days old, the required Guild Force to cast Armageddon drops by 300, to 1700 Guild Force.

	==Example==		==Example==

@@ Line 64: / Line 64: @@
 =Server vs Player-Casted Armageddon=
 *Server-casted Armageddon has its own casting sequence. It is fully independent of player-casted Armageddon, and vice versa.
-*Since players cannot break seals faster than the server, a player-casting sequence that falls behind the server sequence can never catch up, but all effects of the Armageddon enchantment still remain in place.
+*Since players cannot break seals faster than the server, a player-casting sequence that falls behind the server sequence can never catch up, but the Armageddon enchantment, with all its effects, still remains in place.
 *There are some display issues with the seal messages when the server and player sequence are active at the same time. Players are encouraged not to rely on the messages but track seals by themselves.
 =Armageddon day=

← Older revision		Revision as of 09:22, 21 March 2016
Line 60:		Line 60:

	At 04:00 on the fifth day, Orcs member Plonk (pre-)casts Armageddon and begins preparing his mage's defenses for the breaking of the fifth seal, due to take place at 21:02 the same day. However, his preparations are in vain since a few hours later, the Treant Hill Mob, who like elves but can't really stand faeries, kill Tippletoes. Because a successful Armageddon casting requires all seven casters to survive until the seventh seal is broken, the death of Tippletoes breaks the spell, restoring all previously broken seals, and dispelling all existing instances of the Armageddon spell. If Orcs wish to get their mages into the caster Hall of Immortals, they will have to start over from the beginning. If there is a new casting sequence, whoever breaks the first seal will be its owner.		At 04:00 on the fifth day, Orcs member Plonk (pre-)casts Armageddon and begins preparing his mage's defenses for the breaking of the fifth seal, due to take place at 21:02 the same day. However, his preparations are in vain since a few hours later, the Treant Hill Mob, who like elves but can't really stand faeries, kill Tippletoes. Because a successful Armageddon casting requires all seven casters to survive until the seventh seal is broken, the death of Tippletoes breaks the spell, restoring all previously broken seals, and dispelling all existing instances of the Armageddon spell. If Orcs wish to get their mages into the caster Hall of Immortals, they will have to start over from the beginning. If there is a new casting sequence, whoever breaks the first seal will be its owner.
		+
		+
		+	=Server vs Player-Casted Armageddon=
		+	*Server-casted Armageddon has its own casting sequence. It is fully independent of player-casted Armageddon, and vice versa.
		+	*Since players cannot break seals faster than the server, a player-casting sequence that falls behind the server sequence can never catch up, but all effects of the Armageddon enchantment still remain in place.
		+	*There are some display issues with the seal messages when the server and player sequence are active at the same time. Players are encouraged not to rely on the messages but track seals by themselves.

@@ Line 9: / Line 9: @@
 * Takes place at a pre-announced date and time, typically around one or two months after the game round started.
 * The seven seals break on regular intervals, leading up to Armageddon proper, which begins when the 7th seal breaks.
@@ Line 22: / Line 23: @@
 ==Casting==
-*Mages may break seals of Armageddon by casting the Armageddon spell. Seals must break on intervals of at least 12 hours.
+*Mages may break seals of Armageddon by casting the Armageddon spell. Seals must break on intervals of at least 24 hours (12 on Lightning).
 *There are seven seals in total. Each successful cast of the Armageddon spell breaks one seal. When the seventh seal is broken, Armageddon begins.
 *A mage can only break a single seal per casting sequence.
@@ Line 30: / Line 31: @@
 *The guild that breaks the first seal of any casting sequence is considered to be the "owning" guild of that sequence.
-*Members of the owning guild may cast Armageddon again immediately after a seal has broken. The corresponding seal will then break exactly 12 hours after the previous one. This is known as "pre-casting".
+*Members of the owning guild may cast Armageddon again immediately after a seal has broken. The corresponding seal will then break exactly 24 hours (12 on Lightning) after the previous one. This is known as "pre-casting".
-*If the owning guild does not pre-cast within 12 hours of the last seal, any qualifying (guilded) mage regardless of guild affiliation may cast Armageddon, causing the next seal to break immediately. This does not change the ownership of the casting sequence.
+*If the owning guild does not pre-cast within 24 hours (12 on Lightning) of the last seal, any qualifying (guilded) mage regardless of guild affiliation may cast Armageddon, causing the next seal to break immediately. This does not change the ownership of the casting sequence.
@@ Line 42: / Line 43: @@
 *Armageddon casters can receive damage protection ("D"), but it becomes increasingly difficult (+8% damage per seal) as the casting sequence progresses. The increased protection threshold applies equally and immediately to all casters, regardless of which seal they broke. Exception: if a previous caster is already in damage protection at the moment a later seal is broken, that mage will not be affected by the increased threshold until the time at which he is due to leave protection.
 *Armageddon casters receive pillage protection ("-") according to normal rules.
-*The amount of Volcano Eruptions a mage can be targeted with in a 12 hour period also increases (+1 per seal) as more mages cast Armageddon.
+*The amount of Volcano Eruptions a mage can be targeted with in a 24 hour (12 on Lightning) period also increases (+1 per seal) as more mages cast Armageddon.
 *Pre-casting mages will only be affected by the increased protection thresholds from the time their seal breaks, and not from the time they cast the spell.
 *Once Armageddon proper begins, no protection (except apprentice) is available for anyone, caster or not.
@@ Line 50: / Line 51: @@
 ==Example==
-The Orcs guild is in a strong position, and decides to cast Armageddon to end the set early. After Grok, the leader of Orcs, has set the appropriate permissions in the Guild Manager, he casts Armageddon, immediately breaking the first seal and raising his damage threshold from the normal 30% to 38%. This happens at 21:00 game time. One hour later, at 22:00, Orcs member Wark also casts Armageddon. Nothing happens immediately, but at 09:00 the following day, exactly 12 hours after Grok broke the first seal, Wark's casting breaks the second seal. At the same time both Grok's and Wark's damage threshold is raised to 46%.
+This example takes place on a server where the seals interval is 24 hours.
-Orcs had planned for their member Smak to break the third seal, but he's mysteriously absent, and Orcs fail to pre-cast the third seal. Instead, at 21:02 on the second day, Tippletoes, a member of rival guild Faeries, casts Armageddon and immediately breaks the third seal. As she does so, raising her own damage threshold as well as those of the previous orc casters to 54%, Orcs are faced with a decision of whether to kill Tippletoes and restart the casting sequence, or to let Faeries keep the third seal and continue with their casting. Because Grok is an impatient orc, he decides not to break off the casting sequence, instead seeking out Smak and chastizing him for being late. As a result, Smak immediately proceeds to pre-cast the fourth seal, which he can do because Orcs are still the owning guild for the current casting sequence, despite Faeries breaking the last seal.
+The Orcs guild is in a strong position, and decides to cast Armageddon to end the set early. After Grok, the leader of Orcs, has set the appropriate permissions in the Guild Manager, he casts Armageddon, immediately breaking the first seal and raising his damage threshold from the normal 30% to 38%. This happens at 21:00 game time. One hour later, at 22:00, Orcs member Wark also casts Armageddon. Nothing happens immediately, but at 21:00 the following day, exactly 24 hours after Grok broke the first seal, Wark's casting breaks the second seal. At the same time both Grok's and Wark's damage threshold is raised to 46%.
-At 09:02 on the third day, Smak's earlier casting leads to the breaking of the fourth seal, immediately raising the damage threshold of Grok, Tippletoes and himself to 62%. Wark's threshold would have similarly gone up, were it not for the fact that he is in damage protection with 60% damage suffered when the fourth seal breaks, with his status report showing he will come out of D at 14:30. Because of this, the damage threshold does not affect Wark until 14:30, and he avoids being dumped out early, in conflict with what his status report had told him.
+Orcs had planned for their member Smak to break the third seal, but he's mysteriously absent, and Orcs fail to pre-cast the third seal. Instead, at 21:02 on the third day, Tippletoes, a member of rival guild Faeries, casts Armageddon and immediately breaks the third seal. As she does so, raising her own damage threshold as well as those of the previous orc casters to 54%, Orcs are faced with a decision of whether to kill Tippletoes and restart the casting sequence, or to let Faeries keep the third seal and continue with their casting. Because Grok is an impatient orc, he decides not to break off the casting sequence, instead seeking out Smak and chastizing him for being late. As a result, Smak immediately proceeds to pre-cast the fourth seal, which he can do because Orcs are still the owning guild for the current casting sequence, despite Faeries breaking the last seal.
-At 16:00 on the third day, Orcs member Plonk (pre-)casts Armageddon and begins preparing his mage's defenses for the breaking of the fifth seal, due to take place at 21:02 the same day. However, his preparations are in vain since a few hours later, the Treant Hill Mob, who like elves but can't really stand faeries, kill Tippletoes. Because a successful Armageddon casting requires all seven casters to survive until the seventh seal is broken, the death of Tippletoes breaks the spell, restoring all previously broken seals, and dispelling all existing instances of the Armageddon spell. If Orcs wish to get their mages into the caster Hall of Immortals, they will have to start over from the beginning. If there is a new casting sequence, whoever breaks the first seal will be its owner.
+At 21:02 on the fourth day, Smak's earlier casting leads to the breaking of the fourth seal, immediately raising the damage threshold of Grok, Tippletoes and himself to 62%. Wark's threshold would have similarly gone up, were it not for the fact that he is in damage protection with 60% damage suffered when the fourth seal breaks, with his status report showing he will come out of D at 02:30. Because of this, the damage threshold does not affect Wark until 02:30, and he avoids being dumped out early, in conflict with what his status report had told him.