Triglavian Invasion (Chapter 3): Difference between revisions

Line 266:

== Massive EDENCOM fortification ==

~~The~~ invasion ~~event occured simultaneously~~ on ~~the~~ [[Tranquility]] and [[Serenity]] ~~servers (chinese EVE~~ server~~). The progress between the two is synchronized by bringing EDENCOM victories from Serenity to Tranquility in form~~ of ~~Massive EDENCOM Fortifications~~.

For database management reasons, the invasion results on [[Tranquility]] and [[Serenity]] needed to match. Each server had their own separate lists of viable invasion target systems, so there could be no cross-server conflicts over system ownership.

A system ~~that~~ EDENCOM ~~won on Serentiy would become~~ a Massive EDENCOM Fortification ~~on Tranquility~~. ~~EDENCOM forces~~ would ~~partrol the system~~ and ~~only EDENCOM anomalies spawn. After a few~~ days ~~the system turned into a normal~~ EDENCOM Fortress.

In order to enforce system synchronization, any time a system on either server reached either EDENCOM Fortress or Final Liminality, its state propagated to the other server as either a Massive EDENCOM Fortification, or a Massive Triglavian Invasion. Massive Fortification/Invasion systems would contain combat sites and large roaming fleets for several days, before transforming in to EDENCOM Fortress or Final Liminality systems.

~~Massive Triglavian Invasion was another way to sync the servers. But since the Triglavians did not win a single system on Serenity{{verify}}, this state was not observed~~.

== Standings ==

@@ Line 266: / Line 266: @@
 == Massive EDENCOM fortification ==
-The invasion event occured simultaneously on the [[Tranquility]] and [[Serenity]] servers (chinese EVE server). The progress between the two is synchronized by bringing EDENCOM victories from Serenity to Tranquility in form of Massive EDENCOM Fortifications.
+For database management reasons, the invasion results on [[Tranquility]] and [[Serenity]] needed to match. Each server had their own separate lists of viable invasion target systems, so there could be no cross-server conflicts over system ownership.
-A system that EDENCOM won on Serentiy would become a Massive EDENCOM Fortification on Tranquility. EDENCOM forces would partrol the system and only EDENCOM anomalies spawn. After a few days the system turned into a normal EDENCOM Fortress.
+In order to enforce system synchronization, any time a system on either server reached either EDENCOM Fortress or Final Liminality, its state propagated to the other server as either a Massive EDENCOM Fortification, or a Massive Triglavian Invasion. Massive Fortification/Invasion systems would contain combat sites and large roaming fleets for several days, before transforming in to EDENCOM Fortress or Final Liminality systems.
-Massive Triglavian Invasion was another way to sync the servers. But since the Triglavians did not win a single system on Serenity{{verify}}, this state was not observed.
 == Standings ==