Riftwake Incursion - Revision history

Admin: Local CI auto-sync from RiftwakeIncursion.wikitext

2026-10-27T10:03:50Z

Local CI auto-sync from RiftwakeIncursion.wikitext

← Older revision		Revision as of 10:03, 27 October 2026
Line 165:		Line 165:
	\|-		\|-
	\|UI		\|UI
	\|System view like nebula: show Wakeheart + 4 spines only, hide normal planet strip. '''Cleared Siphon Spines''' appear dimmed with a muted status ring (same idea as cleared pirate sites). Tapping a spine opens its details with '''Active / Cleared''' status and which alliance last cleared it. '''Riftwake Command''' opens with the current objective and a '''Road to Realmwarden''' checklist (clear a spine → pay the War Guild levy → hold the Wakeheart; the spine step stays open until your own alliance has Wakeheart entry), shows a tile per Siphon Spine (tap to jump to it) in one of four states — '''Active''', '''Cleared''', '''Respawning''' (with a time range) or '''Respawned''' — and can navigate the galaxy map to the Scar center. The navigate button reads '''Navigate to Active Scar''' only while a combat window is open; before that it reads '''Navigate to Upcoming Scar''', or '''Navigate to Next Week's Scar''' when the next window opens a new Riftwake week. The top panel shows the Scar's mode badge ('''Alliance only''' / '''Ally collaboration'''), and once a window is won it shows the winning alliance's tag and name with the time left on its Mandate. The '''Mandate effects''' panel only appears while a Siphon drain, the Realmwarden bonus, your Regnal Honor or Mandate fatigue is active, and lists your Honor's full effects		\|System view like nebula: show Wakeheart + 4 spines only, hide normal planet strip. '''Cleared Siphon Spines''' appear dimmed with a muted status ring (same idea as cleared pirate sites). Tapping a spine opens its details with '''Active / Cleared''' status and which alliance last cleared it. When a battle leaves a debris field at a Siphon Spine or the Wakeheart, its panel lists the debris and shows a '''Collect Debris''' button, as on pirate and planet panels. '''Riftwake Command''' opens with the current objective and a '''Road to Realmwarden''' checklist (clear a spine → pay the War Guild levy → hold the Wakeheart; the spine step stays open until your own alliance has Wakeheart entry), shows a tile per Siphon Spine (tap to jump to it) in one of four states — '''Active''', '''Cleared''', '''Respawning''' (with a time range) or '''Respawned''' — and can navigate the galaxy map to the Scar center. The navigate button reads '''Navigate to Active Scar''' only while a combat window is open; before that it reads '''Navigate to Upcoming Scar''', or '''Navigate to Next Week's Scar''' when the next window opens a new Riftwake week. The top panel shows the Scar's mode badge ('''Alliance only''' / '''Ally collaboration'''), and once a window is won it shows the winning alliance's tag and name with the time left on its Mandate. The '''Mandate effects''' panel only appears while a Siphon drain, the Realmwarden bonus, your Regnal Honor or Mandate fatigue is active, and lists your Honor's full effects
	\|}		\|}

Line 815:		Line 815:
	'''No personal debuff titles in v1.''' Soft power is buffing allies / diplomats and distributing Mandate Caches — not nerfing rivals.		'''No personal debuff titles in v1.''' Soft power is buffing allies / diplomats and distributing Mandate Caches — not nerfing rivals.

	Realmwarden leadership assigns up to '''8''' unique Honors to '''any player on the server'''. Effects last while assigned (up to 7 days). '''24h cooldown''' per slot after reassignment. One player may hold '''at most one''' Honor at a time. Active Honors appear as a badge on the holder's '''player profile''' and next to their name on '''leaderboards''', '''alliance member lists''', and related player listings.		Realmwarden leadership assigns up to '''8''' unique Honors to '''any player on the server'''. Effects last while assigned and end when the next Riftwake week opens (up to 7 days), so they never apply to next week's Siphon Spine or Wakeheart battles. '''24h cooldown''' per slot after reassignment. One player may hold '''at most one''' Honor at a time. Active Honors appear as a badge on the holder's '''player profile''' and next to their name on '''leaderboards''', '''alliance member lists''', and related player listings.

	{\| class="wikitable"		{\| class="wikitable"
Line 841:		Line 841:
	\|High Inquisitor		\|High Inquisitor
	\|Ops / PvE		\|Ops / PvE
	\|<code>fleetSpeedPct +15%</code> (no extra fuel), <code>pveBossDamagePct +10%</code> — fleet attack against '''any''' pirate target and Siphon Spines		\|<code>fleetSpeedPct +15%</code> (no extra fuel), <code>pveBossDamagePct +10%</code> — fleet attack against '''any''' pirate target and the Siphon Spines of the week it was won (it ends before next week's spines open)
	\|-		\|-
	\|<code>veilwarden</code>		\|<code>veilwarden</code>

Admin: Local CI auto-sync from RiftwakeIncursion.wikitext

2026-10-24T09:56:58Z

Local CI auto-sync from RiftwakeIncursion.wikitext

← Older revision		Revision as of 09:56, 24 October 2026
Line 676:		Line 676:
	\|-		\|-
	\|Mandate fatigue		\|Mandate fatigue
	\|Counts the alliance's Realmwarden wins over the last '''4''' Riftwake weeks: every win after the first, back to back or not, is '''−5%''' attack, hull and shields (cap '''−15%''') in Siphon Spine and Wakeheart ~~battles~~; fades as older wins drop out of the 4 weeks		\|Counts the alliance's Realmwarden wins over the last '''4''' Riftwake weeks: every win after the first, back to back or not, is '''−5%''' attack, hull and shields (cap '''−15%''') for your alliance's fleets in every Siphon Spine and Wakeheart battle — '''attacking and defending a held Wakeheart''' alike; fades as older wins drop out of the 4 weeks
	\|}		\|}

	'''Mandate fatigue example.''' An alliance wins weeks 1 and 2: it fights week 3's Incursion at '''−5%'''. Winning week 3 as well makes week 4 '''−10%''', then '''−15%''' at most. Taking turns does not avoid it: if alliance A wins weeks 1 and 3 and alliance B wins week 2, A still fights week 4 at '''−5%'''. A win only stops counting once it is more than 4 weeks old. A period counts once even if it ran several daily windows. Fatigue ~~only~~ applies ~~against~~ Siphon ~~Spines~~ and ~~the~~ Wakeheart, never in other battles. The Realmwarden mail announces it, '''Riftwake Command''' and ship info show your own fatigue while it applies, and the '''Mandate fatigue''' list in Riftwake Command → Command shows every alliance with a win in the last 4 weeks, its win count and its fatigue this week.		'''Mandate fatigue example.''' An alliance wins weeks 1 and 2: it fights week 3's Incursion at '''−5%'''. Winning week 3 as well makes week 4 '''−10%''', then '''−15%''' at most. Taking turns does not avoid it: if alliance A wins weeks 1 and 3 and alliance B wins week 2, A still fights week 4 at '''−5%'''. A win only stops counting once it is more than 4 weeks old. A period counts once even if it ran several daily windows. Fatigue applies in every Siphon Spine and Wakeheart battle: when your fleets attack, and when they are stationed at a Wakeheart your alliance holds and rivals attack it. It never applies in other battles. It follows each commander's own alliance, so diplomatic allies who join your rallies or station at your Wakeheart fight at their own strength (with their own fatigue, if any). The Realmwarden mail announces it, '''Riftwake Command''' and ship info show your own fatigue while it applies, and the '''Mandate fatigue''' list in Riftwake Command → Command shows every alliance with a win in the last 4 weeks, its win count and its fatigue this week.

	'''Contribution board''' (Riftwake Command → Command) tracks this week’s fighters as soon as the Incursion opens — spine damage, Wakeheart PvP damage, hold time, and spine clears all count (top 5 shown, expand for the full list). It is '''not''' locked behind winning the Wakeheart.		'''Contribution board''' (Riftwake Command → Command) tracks this week’s fighters as soon as the Incursion opens — spine damage, Wakeheart PvP damage, hold time, and spine clears all count (top 5 shown, expand for the full list). It is '''not''' locked behind winning the Wakeheart.
Line 954:		Line 954:
	\|-		\|-
	\|Mandate fatigue		\|Mandate fatigue
	\|Each extra Realmwarden win by the '''same''' alliance within 4 weeks: '''−5%''' Riftwake battle stats (cap '''−15%'''; spines / Wakeheart only); taking turns with another alliance does not reset it		\|Each extra Realmwarden win by the '''same''' alliance within 4 weeks: '''−5%''' Riftwake battle stats (cap '''−15%'''; spines / Wakeheart only, attacking and defending the hold); taking turns with another alliance does not reset it
	\|-		\|-
	\|Manual caches / titles		\|Manual caches / titles
Line 1,066:		Line 1,066:
	\|-		\|-
	\|Mandate fatigue		\|Mandate fatigue
	\|−5% per win after the first in the last 4 weeks (back to back or not), max −15%, Riftwake ~~targets~~ only		\|−5% per win after the first in the last 4 weeks (back to back or not), max −15%, Riftwake battles only (attacking and defending the Wakeheart); own alliance's fleets only
	\|-		\|-
	\|Cache rollover after a week with no winner		\|Cache rollover after a week with no winner

Admin: Local CI auto-sync from RiftwakeIncursion.wikitext

2026-10-22T08:23:23Z

Local CI auto-sync from RiftwakeIncursion.wikitext

← Older revision		Revision as of 08:23, 22 October 2026
Line 222:		Line 222:
	▼		▼
	Winner — Realmwarden until the next Riftwake week opens (up to 7 days)		Winner — Realmwarden until the next Riftwake week opens (up to 7 days)
	Mandate Caches + Regnal Honors; a ~~back-to-back~~ win adds Mandate fatigue for the next week's fights		Mandate Caches + Regnal Honors; a repeat win within 4 weeks adds Mandate fatigue for the next week's fights
	Spinebreaker Caches delivered straight to the commanders who cleared spines (any alliance)		Spinebreaker Caches delivered straight to the commanders who cleared spines (any alliance)
	Auto participation packs for 2nd / 3rd / spine-clear fighters, per window		Auto participation packs for 2nd / 3rd / spine-clear fighters, per window
Line 676:		Line 676:
	\|-		\|-
	\|Mandate fatigue		\|Mandate fatigue
	\|~~From~~ the '''~~second~~''' back-to-back ~~win:~~ '''−5%''' attack, hull and shields ~~per extra consecutive win~~ (cap '''−15%''') in ~~the '''following''' week's~~ Siphon Spine and Wakeheart battles; ~~resets after a week~~ the ~~alliance does not win~~		\|Counts the alliance's Realmwarden wins over the last '''4''' Riftwake weeks: every win after the first, back to back or not, is '''−5%''' attack, hull and shields (cap '''−15%''') in Siphon Spine and Wakeheart battles; fades as older wins drop out of the 4 weeks
	\|}		\|}

	'''Mandate fatigue example.''' An alliance wins weeks 1 and 2: it fights week 3's Incursion at '''−5%'''. Winning week 3 as well makes week 4 '''−10%''', then '''−15%''' at most. ~~If any~~ week ~~passes without its win~~, ~~the next~~ week is ~~back to full strength~~. Fatigue only applies against Siphon Spines and the Wakeheart, never in other battles. The Realmwarden mail announces it, ~~and~~ '''Riftwake Command''' and ship info show it while it applies.		'''Mandate fatigue example.''' An alliance wins weeks 1 and 2: it fights week 3's Incursion at '''−5%'''. Winning week 3 as well makes week 4 '''−10%''', then '''−15%''' at most. Taking turns does not avoid it: if alliance A wins weeks 1 and 3 and alliance B wins week 2, A still fights week 4 at '''−5%'''. A win only stops counting once it is more than 4 weeks old. A period counts once even if it ran several daily windows. Fatigue only applies against Siphon Spines and the Wakeheart, never in other battles. The Realmwarden mail announces it, '''Riftwake Command''' and ship info show your own fatigue while it applies, and the '''Mandate fatigue''' list in Riftwake Command → Command shows every alliance with a win in the last 4 weeks, its win count and its fatigue this week.

	'''Contribution board''' (Riftwake Command → Command) tracks this week’s fighters as soon as the Incursion opens — spine damage, Wakeheart PvP damage, hold time, and spine clears all count (top 5 shown, expand for the full list). It is '''not''' locked behind winning the Wakeheart.		'''Contribution board''' (Riftwake Command → Command) tracks this week’s fighters as soon as the Incursion opens — spine damage, Wakeheart PvP damage, hold time, and spine clears all count (top 5 shown, expand for the full list). It is '''not''' locked behind winning the Wakeheart.
Line 954:		Line 954:
	\|-		\|-
	\|Mandate fatigue		\|Mandate fatigue
	\|Each ~~consecutive week~~ the '''same''' alliance ~~retains Realmwarden~~: '''−5%''' Riftwake battle stats (cap '''−15%'''; spines / Wakeheart only); ~~resets when~~ another alliance ~~wins~~		\|Each extra Realmwarden win by the '''same''' alliance within 4 weeks: '''−5%''' Riftwake battle stats (cap '''−15%'''; spines / Wakeheart only); taking turns with another alliance does not reset it
	\|-		\|-
	\|Manual caches / titles		\|Manual caches / titles
Line 1,066:		Line 1,066:
	\|-		\|-
	\|Mandate fatigue		\|Mandate fatigue
	\|−5% per ~~back-to-back~~ win after the first, max −15%, ~~next week's~~ Riftwake targets only		\|−5% per win after the first in the last 4 weeks (back to back or not), max −15%, Riftwake targets only
	\|-		\|-
	\|Cache rollover after a week with no winner		\|Cache rollover after a week with no winner

Admin: Local CI auto-sync from RiftwakeIncursion.wikitext

2026-10-12T04:15:32Z

Local CI auto-sync from RiftwakeIncursion.wikitext

← Older revision		Revision as of 04:15, 12 October 2026
Line 457:		Line 457:
	\|-		\|-
	\|0		\|0
	\|+0%		\| +0%
	\|'''60m'''		\|'''60m'''
	\|-		\|-
	\|1		\|1
	\|+5%		\| +5%
	\|'''63m'''		\|'''63m'''
	\|-		\|-
	\|2		\|2
	\|+10%		\| +10%
	\|'''66m'''		\|'''66m'''
	\|-		\|-
	\|3		\|3
	\|+15%		\| +15%
	\|'''69m'''		\|'''69m'''
	\|-		\|-
	\|4		\|4
	\|+20%		\| +20%
	\|'''72m'''		\|'''72m'''
	\|}		\|}
Line 1,030:		Line 1,030:
	\|-		\|-
	\|Hold bonus per spine		\|Hold bonus per spine
	\|+5% (max +20%)		\| +5% (max +20%)
	\|-		\|-
	\|Spine respawn		\|Spine respawn
Line 1,063:		Line 1,063:
	\|-		\|-
	\|Realmwarden production perk		\|Realmwarden production perk
	\|+5%		\| +5%
	\|-		\|-
	\|Mandate fatigue		\|Mandate fatigue
Line 1,069:		Line 1,069:
	\|-		\|-
	\|Cache rollover after a week with no winner		\|Cache rollover after a week with no winner
	\|+10%, rounded up per tier (<code>riftwake.mandateCacheRolloverPct</code>)		\| +10%, rounded up per tier (<code>riftwake.mandateCacheRolloverPct</code>)
	\|}		\|}

Admin: Local CI auto-sync from RiftwakeIncursion.wikitext

2026-10-07T11:26:11Z

Local CI auto-sync from RiftwakeIncursion.wikitext

← Older revision		Revision as of 11:26, 7 October 2026
Line 215:		Line 215:
	│ Displacement pauses that alliance's clock — banked time is kept		│ Displacement pauses that alliance's clock — banked time is kept
	│ Ally collaboration Scars: diplomatic allies cannot displace each other (NAP still can)		│ Ally collaboration Scars: diplomatic allies cannot displace each other (NAP still can)
	│ Alliance only Scars: allies ~~contest the Wakeheart like any rival~~		│ Alliance only Scars: no joint ops with allies; they can back you by hitting hostile alliances
	│ Spines respawn (±jitter) — clear one to earn entry late or restore a bonus		│ Spines respawn (±jitter) — clear one to earn entry late or restore a bonus
	▼		▼
Line 258:		Line 258:
	Diplomatic treaties do '''not''' merge alliances for Riftwake scoring or win conditions. Each alliance remains a separate competitor.		Diplomatic treaties do '''not''' merge alliances for Riftwake scoring or win conditions. Each alliance remains a separate competitor.

	'''Scar mode.''' Each Scar is either '''Alliance only''' (Scars 1, 3, 5) or '''Ally collaboration''' (Scars 2, 4). The ally rules below apply only on an Ally collaboration Scar. On an Alliance only Scar a diplomatic ally ~~is treated as a rival: it~~ cannot join your rallies, launch from your stations or station at your Wakeheart~~, it '''may''' attack your hold~~, and any allied fleet stationed at the Wakeheart is sent home when you capture it. In the client, allies get no '''Station''' button on that Wakeheart, and rallies against that Scar hide the '''Allow inter-alliance participation''' toggle. The mail that announces an open window states the mode, and the badge sits at the top of Riftwake Command.		'''Scar mode.''' Each Scar is either '''Alliance only''' (Scars 1, 3, 5) or '''Ally collaboration''' (Scars 2, 4). The ally rules below apply only on an Ally collaboration Scar. On an Alliance only Scar each alliance takes the Wakeheart with its own fleets: a diplomatic ally cannot join your rallies, launch from your stations or station at your Wakeheart, and any allied fleet stationed at the Wakeheart is sent home when you capture it. The ally rules do not apply there, so an ally ''can'' attack your hold, but this does not make allies rivals: alliances can still help one ally take the throne by putting pressure on hostile alliances, attacking their territories and players during the incursion. In the client, allies get no '''Station''' button on that Wakeheart, and rallies against that Scar hide the '''Allow inter-alliance participation''' toggle. The mail that announces an open window states the mode, and the badge sits at the top of Riftwake Command.

	{\| class="wikitable"		{\| class="wikitable"

Admin: Local CI auto-sync from RiftwakeIncursion.wikitext

2026-10-04T06:16:42Z

Local CI auto-sync from RiftwakeIncursion.wikitext

Show changes

Admin: Local CI auto-sync from RiftwakeIncursion.wikitext

2026-09-30T21:37:46Z

Local CI auto-sync from RiftwakeIncursion.wikitext

Show changes

Admin: Local CI auto-sync from RiftwakeIncursion.wikitext

2026-09-29T04:39:50Z

Local CI auto-sync from RiftwakeIncursion.wikitext

← Older revision		Revision as of 04:39, 29 September 2026
Line 365:		Line 365:
	\|-		\|-
	\|Gating		\|Gating
	\|Wakeheart attacks '''refused''' while any Siphon Spine still has NPC ships, and until the alliance has paid the '''War Guild levy''' for this ~~Incursion~~		\|Wakeheart attacks '''refused''' while any Siphon Spine still has NPC ships, and until the alliance has paid the '''War Guild levy''' for this Riftwake week. '''One payment covers every daily window that week''' — a window closing unclaimed does not make you pay again
	\|-		\|-
	\|Reinforce		\|Reinforce
Line 515:		Line 515:
	\|}		\|}

	'''Example.''' A '''Fleet'''-title alliance (~2T power) pays a War Guild levy of '''50T steel''' and '''1.5T elerium''' (plus quartz / iridium / silicium) once ~~for the~~ week. A '''Grand Fleet''' pays '''100T steel''' and '''4T elerium'''. Leadership should top up the vault before the crown fight — emptying the vault does not lower the levy.		'''Example.''' A '''Fleet'''-title alliance (~2T power) pays a War Guild levy of '''50T steel''' and '''1.5T elerium''' (plus quartz / iridium / silicium) '''once per Riftwake week'''. A '''Grand Fleet''' pays '''100T steel''' and '''4T elerium'''. The levy is '''per week, not per window''': if Saturday's window ends with no Realmwarden, your alliance may contest Sunday's and Monday's windows on the same payment. Leadership should top up the vault before the crown fight — emptying the vault does not lower the levy.

	=== Window end ===		=== Window end ===
Line 556:		Line 556:
	\|<code>riftwake.windowStartOffsetHours</code>. Riftwake runs on its own 7-day period, independent of the weekly league rollover		\|<code>riftwake.windowStartOffsetHours</code>. Riftwake runs on its own 7-day period, independent of the weekly league rollover
	\|}		\|}

			During the pre-window hours the Scar is '''visible but read-only''': attacks, probes and stationing on Siphon Spines and the Wakeheart are all refused until the combat window begins. The structure panel shows the countdown instead of the action buttons.

	About '''6 hours''' before a window opens, the Active Scar and its Contagion belt light up on the galaxy map, the Scar hex shows a '''Riftwake inbound''' countdown, and '''Riftwake Command''' switches to an inbound state with the Scar coordinates and a navigate button. Use that lead to move fleets into Contagion range — no mail is sent, so watch the map and the hub.		About '''6 hours''' before a window opens, the Active Scar and its Contagion belt light up on the galaxy map, the Scar hex shows a '''Riftwake inbound''' countdown, and '''Riftwake Command''' switches to an inbound state with the Scar coordinates and a navigate button. Use that lead to move fleets into Contagion range — no mail is sent, so watch the map and the hub.

Admin: Local CI auto-sync from RiftwakeIncursion.wikitext

2026-09-28T14:39:29Z

Local CI auto-sync from RiftwakeIncursion.wikitext

Show changes

Admin: Local CI auto-sync from RiftwakeIncursion.wikitext

2026-09-25T08:39:43Z

Local CI auto-sync from RiftwakeIncursion.wikitext

@@ Line 349: / Line 349: @@
 |-
 |Base hold
-|'''3 hours''' wall-clock at +0% bonus
+|'''3 hours''' wall-clock with no spine credit
 |-
-|Hold bonus
+|Hold rate
-|<code>requiredHold = 3h / (1 + bonus)</code>; e.g. +20% → '''~2h 30m'''
+|Each credited spine adds '''+5% hold rate''' (max '''+20%'''). Higher rate shortens the continuous occupation needed (see table below).
 |-
 |Displacement
@@ Line 372: / Line 372: @@
 |Default '''8 hour''' active event window
 |}
 === War Guild levy ===
@@ Line 477: / Line 509: @@
 '''Example.''' A '''Fleet'''-title alliance (~2T power) pays a War Guild levy of '''50T steel''' and '''1.5T elerium''' (plus quartz / iridium / silicium) once for the week. A '''Grand Fleet''' pays '''100T steel''' and '''4T elerium'''. Leadership should top up the vault before the crown fight — emptying the vault does not lower the levy.
 === Window end (no full hold) ===