This is an old revision of the document!
Table of Contents
Incursion Spawn Mechanics
This guide details aspects of incursion spawn mechanics to help with your understanding of influence, incursion phases and spawn windows.
Influence
Influence is how much control Sansha has over the constellation the focus has occurred in - it is displayed in your EVE client with a “bar” in the interface that is completely red at 100%, and green/blue at 0%. The amount of influence affects us mostly with decreased dps and deceased tank through changes to our armour resists - at 100% influence, the Sansha ships we need to destroy have increased resists, and our resists are halved! Fleets that are run to reduce the Sansha influence are often called “redbar fleets” - you may be asked to fit an additional armour plate on some ships to ensure that your ship remains intact during these efforts.
At the start of each focus the influence begins at 100% and as we finish sites the influence level decreases by 1% per VG site, 2% per AS site and 3% per HQ site. As this influence decreases so does the effects Sansha exert over the constellation. Once the influence level reaches 0% the Kundalini Manifest (mothership, often called “The Mom”) site appears in the HQ system.
Spawn Phases
Each focus has three phases, Established, Mobilizing and Withdrawing.
Established
This is the starting phase of the incursion spawn and is the only phase which is variable in timing. The established phase may last from as little as 24 hrs through to 5 days
Mobilizing
Once the established phase has finished the spawn becomes mobilizing. This phase lasts for 48 hours.
Withdrawing
Once the mobilizing phase has finished the spawn becomes withdrawing. This phase lasts for 24 hours. In the withdrawing phase The Kundalini Manifest, aka “Mom”, site is normally completed in the final hour of withdrawing. The “Mom” site must be completed before the Withdrawing phase ends for the Concord Loyalty Points that pilots have accrued during the focus to be paid out.
Spawn and Phase Timers
So with the above phase timers each spawn can last from a minimum of 4 days to a maximum of 8 days. Once the spawn finishes there is a 12hr delay before the spawn window opens. Once the spawn window opens a spawn can happen anytime in the next 24 hours. Because of CCP coding, sometimes the spawn timer can run past this 36 hour window before a new focus starts.
Once the new spawn is up a move order will be posted to discord and the in-game channel listing the dock up station for the new focus.
To get to the new focus safely please see our traveling between focuses guide.
Kundalini Agreement
In the past the mom site has had a lot of drama involved with it, where one community would kill the Kundalini cause they got contested too much, or because they finished their shift and wouldn't fly again before it despawned or because they wanted a better window of respawn. It has also been jokingly done after fun fleets, or by a slightly drunk FC. This caused a lot of animosity between the HQ communities and the VG/AS communities and with only 1 spawn we are all affected. We can not just go to a different focus. In Fall/Winter 2020 it got really bad so in January 2021 the “Kundalini Agreement Discord” was born. In this discord all HQ communities capable and willing of killing the Kundalini are represented and when a spawn goes mobilizing it gets discussed whose turn it is. There is a rotation so that all communities get their turn. If it's the turn of a community but they are unable to form due to wrong timezone, they pass to the next one but generally keep their spot for when a focus dies in their timezone.
If an FC decides to kill the Kundalini early, it is not entirely on him alone, but the whole fleet. A fleet is only as strong as all the line pilots. Knowingly taking the Kundalini early and killing her can be cause for temp ban with Contingency.