Alliances - Revision history

Admin: Local CI auto-sync from Alliances.wikitext

2026-10-14T18:49:21Z

Local CI auto-sync from Alliances.wikitext

← Older revision		Revision as of 18:49, 14 October 2026
Line 86:		Line 86:

	'''Leaving:''' any member can leave at any time. The '''Leader cannot simply leave''' — they must first transfer leadership to another member or disband the alliance.		'''Leaving:''' any member can leave at any time. The '''Leader cannot simply leave''' — they must first transfer leadership to another member or disband the alliance.

			'''Inactive alliances:''' if no member has played for '''14 days''', an alliance with ''Open'' recruitment switches to ''Invite Only'', so new players apply instead of joining an empty alliance (the leader can open it again). If no member has played for '''2 months''', the alliance is disbanded.

	== Roles & permissions ==		== Roles & permissions ==

Admin: Local CI auto-sync from Alliances.wikitext

2026-10-12T04:15:29Z

Local CI auto-sync from Alliances.wikitext

← Older revision		Revision as of 04:15, 12 October 2026
Line 171:		Line 171:
	\|-		\|-
	\|'''Garrison Capacity'''		\|'''Garrison Capacity'''
	\|+1 defense build slot.		\| +1 defense build slot.
	\|}		\|}

Admin: Local CI auto-sync from Alliances.wikitext

2026-10-08T16:02:31Z

Local CI auto-sync from Alliances.wikitext

← Older revision		Revision as of 16:02, 8 October 2026
Line 56:		Line 56:
	* You can have only '''one''' pending application at a time.		* You can have only '''one''' pending application at a time.
	* An alliance can't exceed its member limit (raised by the ''Recruitment Doctrine'' research — see below).		* An alliance can't exceed its member limit (raised by the ''Recruitment Doctrine'' research — see below).

			=== Alliance tribute (Realm 1–3) ===

			Alliances that hold star systems share part of their daily harvest pool with members in Realms 1–3. In the alliance list these alliances are marked '''Tribute'''.

			* Your daily tribute is '''cap × your score ÷ the next Realm gate''', never less than '''a quarter''' of the cap and never more than the full cap.
			* It only includes resources your Realm has (Realm 1: steel, quartz, gas; Realm 2 adds iridium and silicium; Realm 3 adds elerium), in the same mix as the pool.
			* Your first tribute comes from the pool day that ends at least '''2 days''' after you join.
			* Tributes are paid first, before the Realm 4 split. Together they never take more than '''10%''' of the pool.
			* Collect it from the '''Harvest''' tab like a Realm 4 share. The Trade Union convoy starts at your capital, and uncollected tribute is lost on the next rollover.

			{\| class="wikitable"
			!Realm
			!Daily cap (total resources)
			!At the floor (¼ cap)
			\|-
			\|1
			\|1M
			\|250K
			\|-
			\|2
			\|300M
			\|75M
			\|-
			\|3
			\|10B
			\|2.5B
			\|}

	'''Leaving:''' any member can leave at any time. The '''Leader cannot simply leave''' — they must first transfer leadership to another member or disband the alliance.		'''Leaving:''' any member can leave at any time. The '''Leader cannot simply leave''' — they must first transfer leadership to another member or disband the alliance.
Line 71:		Line 99:
	\|-		\|-
	\|'''Officer'''		\|'''Officer'''
	\|Everything a member can, plus: approve/reject applications~~, promote/demote members~~, remove members, edit alliance settings, send broadcasts, manage branding and diplomacy, and upgrade '''or downgrade''' alliance buildings.		\|Everything a member can, plus: approve/reject applications, remove members, edit alliance settings, send broadcasts, manage branding and diplomacy, and upgrade '''or downgrade''' alliance buildings.
	\|-		\|-
	\|'''Deputy'''		\|'''Deputy'''
	\|Everything an officer can, plus start and cancel '''alliance research'''.		\|Everything an officer can, plus start and cancel '''alliance research''', promote members to Officer, demote Officers, and remove Officers.
	\|-		\|-
	\|'''Leader'''		\|'''Leader'''
	\|Full control: transfer leadership and disband the alliance.		\|Full control: appoint and demote Deputies, remove anyone, transfer leadership and disband the alliance.
	\|}		\|}

			You can only promote, demote or remove members ranked '''below''' you, and only give a rank below your own. Nobody can change their own rank, and the Leader's rank changes only by transferring leadership.

	When a Leader transfers leadership, they step down to '''Deputy''' and the chosen member becomes the new Leader.		When a Leader transfers leadership, they step down to '''Deputy''' and the chosen member becomes the new Leader.
Line 263:		Line 293:
	* Your first system becomes the '''HQ'''; the rest are '''Divisions''', or '''Bastions''' when you anchor a system far from your existing space. A Deputy or Leader can later '''move the Headquarters''' to a connected Division or an Expansion Bastion — see [[Alliance Territory#moving the headquarters\|Alliance Territory → Moving the Headquarters]].		* Your first system becomes the '''HQ'''; the rest are '''Divisions''', or '''Bastions''' when you anchor a system far from your existing space. A Deputy or Leader can later '''move the Headquarters''' to a connected Division or an Expansion Bastion — see [[Alliance Territory#moving the headquarters\|Alliance Territory → Moving the Headquarters]].
	* Each Division and Bastion carries one '''Doctrine''' — production, shipbuilding, defence, logistics, or intel — and connected nodes pay alliance-wide bonuses. See [[Alliance Territory]].		* Each Division and Bastion carries one '''Doctrine''' — production, shipbuilding, defence, logistics, or intel — and connected nodes pay alliance-wide bonuses. See [[Alliance Territory]].
	* Controlled systems support a shared '''harvest & survey pool''': production each cycle is split between the runner, guardians, and an alliance daily pool that members collect their share from. The runner's and guardians' shares ride home in their '''fleet cargo''' and are credited when the fleet returns. Each share is capped by free cargo space, and anything that does not fit goes to the alliance pool. A full Harvest/Survey fleet ends its run early and flies home; a full Guardian keeps guarding for its whole station time but earns nothing more. The pool pays out in full only once '''15''' eligible (Realm 4+) members are on the roster — a 1-member alliance receives '''1/15'''; the rest is discarded.		* Controlled systems support a shared '''harvest & survey pool''': production each cycle is split between the runner, guardians, and an alliance daily pool that members collect their share from. The runner's and guardians' shares ride home in their '''fleet cargo''' and are credited when the fleet returns. Each share is capped by free cargo space, and anything that does not fit goes to the alliance pool. A full Harvest/Survey fleet ends its run early and flies home; a full Guardian keeps guarding for its whole station time but earns nothing more. The pool pays out in full only once '''15''' eligible (Realm 4+) members are on the roster — a 1-member alliance receives '''1/15'''; the rest is discarded. Before that split, members in Realms 1–3 receive a capped [[#Alliance tribute (Realm 1–3)\|alliance tribute]].
	* Controlled systems can be dressed up with '''system themes''' and '''monuments''' (see below).		* Controlled systems can be dressed up with '''system themes''' and '''monuments''' (see below).

Line 373:		Line 403:
	\|Harvest pool full payout		\|Harvest pool full payout
	\|15 eligible (Realm 4+) members		\|15 eligible (Realm 4+) members
			\|-
			\|Realm 1–3 tribute cap per day
			\|1M · 300M · 10B (at least ¼ of the cap)
	\|-		\|-
	\|Roles		\|Roles

Admin: Local CI auto-sync from Alliances.wikitext

2026-10-02T12:27:56Z

Local CI auto-sync from Alliances.wikitext

← Older revision		Revision as of 12:27, 2 October 2026
Line 263:		Line 263:
	* Your first system becomes the '''HQ'''; the rest are '''Divisions''', or '''Bastions''' when you anchor a system far from your existing space. A Deputy or Leader can later '''move the Headquarters''' to a connected Division or an Expansion Bastion — see [[Alliance Territory#moving the headquarters\|Alliance Territory → Moving the Headquarters]].		* Your first system becomes the '''HQ'''; the rest are '''Divisions''', or '''Bastions''' when you anchor a system far from your existing space. A Deputy or Leader can later '''move the Headquarters''' to a connected Division or an Expansion Bastion — see [[Alliance Territory#moving the headquarters\|Alliance Territory → Moving the Headquarters]].
	* Each Division and Bastion carries one '''Doctrine''' — production, shipbuilding, defence, logistics, or intel — and connected nodes pay alliance-wide bonuses. See [[Alliance Territory]].		* Each Division and Bastion carries one '''Doctrine''' — production, shipbuilding, defence, logistics, or intel — and connected nodes pay alliance-wide bonuses. See [[Alliance Territory]].
	* Controlled systems support a shared '''harvest & survey pool''': production each cycle is split between the runner, guardians, and an alliance daily pool that members collect their share from. The pool pays out in full only once '''15''' eligible (Realm 4+) members are on the roster — a 1-member alliance receives '''1/15'''; the rest is discarded.		* Controlled systems support a shared '''harvest & survey pool''': production each cycle is split between the runner, guardians, and an alliance daily pool that members collect their share from. The runner's and guardians' shares ride home in their '''fleet cargo''' and are credited when the fleet returns. Each share is capped by free cargo space, and anything that does not fit goes to the alliance pool. A full Harvest/Survey fleet ends its run early and flies home; a full Guardian keeps guarding for its whole station time but earns nothing more. The pool pays out in full only once '''15''' eligible (Realm 4+) members are on the roster — a 1-member alliance receives '''1/15'''; the rest is discarded.
	* Controlled systems can be dressed up with '''system themes''' and '''monuments''' (see below).		* Controlled systems can be dressed up with '''system themes''' and '''monuments''' (see below).

Admin: Publish Alliances.wikitext → Alliances

2026-09-23T10:59:19Z

Publish Alliances.wikitext → Alliances

← Older revision		Revision as of 10:59, 23 September 2026
Line 243:		Line 243:
	== Alliance Power ==		== Alliance Power ==

	'''Alliance Power''' ranks how much your alliance has invested in shared buildings and research — not how full the vault is. Territory empires earn a fleet title from '''Flotilla''' up through '''Grand Fleet''' (and beyond), which also sets the weekly [[Riftwake Incursion#~~wakeheart contest fund~~\|~~Wakeheart contest fund~~]].		'''Alliance Power''' ranks how much your alliance has invested in shared buildings and research — not how full the vault is. Territory empires earn a fleet title from '''Flotilla''' up through '''Grand Fleet''' (and beyond), which also sets the weekly [[Riftwake Incursion#war guild levy\|War Guild levy]] on the Active Scar.

	Alliances with '''no territory''' are unranked and cannot fight in Riftwake.		Alliances with '''no territory''' are unranked and cannot fight in Riftwake.
Line 347:		Line 347:
	* '''Alliance Power''' is a separate investment ranking (buildings + alliance research) with fleet titles — see [[Alliance Power]].		* '''Alliance Power''' is a separate investment ranking (buildings + alliance research) with fleet titles — see [[Alliance Power]].
	* '''Weekly alliance events''' offer alliance-tier rewards for collective effort (a separate event-score, not empire total).		* '''Weekly alliance events''' offer alliance-tier rewards for collective effort (a separate event-score, not empire total).
	* '''Riftwake Incursion''' is a weekly AvA assault on a rotating alien scar — the winner becomes Realmwarden. Wakeheart ~~entry costs scale~~ with Alliance Power. See [[Riftwake Incursion]].		* '''Riftwake Incursion''' is a weekly AvA assault on a rotating alien scar — the winner becomes Realmwarden. The '''War Guild levy''' to contest the Wakeheart scales with Alliance Power. See [[Riftwake Incursion]].
	* Your active alliance '''badge''' appears beside your alliance name across these screens.		* Your active alliance '''badge''' appears beside your alliance name across these screens.

Admin: Publish Alliances.wikitext → Alliances

2026-09-23T10:10:23Z

Publish Alliances.wikitext → Alliances

← Older revision		Revision as of 10:10, 23 September 2026
Line 14:		Line 14:
	* Alliance Research		* Alliance Research
	* Alliance Buildings		* Alliance Buildings
			* Alliance Power
	* Territorial control		* Territorial control
	* Bastions & doctrines		* Bastions & doctrines
Line 240:		Line 241:
	* A Headquarters downgrade is '''refused if it would drop below the level your Divisions or Bastion mains require'''. Downgrade those first.		* A Headquarters downgrade is '''refused if it would drop below the level your Divisions or Bastion mains require'''. Downgrade those first.

			== Alliance Power ==

			'''Alliance Power''' ranks how much your alliance has invested in shared buildings and research — not how full the vault is. Territory empires earn a fleet title from '''Flotilla''' up through '''Grand Fleet''' (and beyond), which also sets the weekly [[Riftwake Incursion#wakeheart contest fund\|Wakeheart contest fund]].

			Alliances with '''no territory''' are unranked and cannot fight in Riftwake.

			Full formula, title thresholds, and examples: [[Alliance Power]].

	== Territorial control ==		== Territorial control ==
Line 337:		Line 345:

	* '''Alliance leaderboards''' rank alliances against one another by the '''sum of members' empire scores'''. See [[Score]].		* '''Alliance leaderboards''' rank alliances against one another by the '''sum of members' empire scores'''. See [[Score]].
			* '''Alliance Power''' is a separate investment ranking (buildings + alliance research) with fleet titles — see [[Alliance Power]].
	* '''Weekly alliance events''' offer alliance-tier rewards for collective effort (a separate event-score, not empire total).		* '''Weekly alliance events''' offer alliance-tier rewards for collective effort (a separate event-score, not empire total).
	* '''Riftwake Incursion''' is a weekly AvA assault on a rotating alien scar — the winner becomes Realmwarden. See [[Riftwake Incursion]].		* '''Riftwake Incursion''' is a weekly AvA assault on a rotating alien scar — the winner becomes Realmwarden. Wakeheart entry costs scale with Alliance Power. See [[Riftwake Incursion]].
	* Your active alliance '''badge''' appears beside your alliance name across these screens.		* Your active alliance '''badge''' appears beside your alliance name across these screens.

Admin: Local CI auto-sync from Alliances.wikitext

2026-09-18T09:31:02Z

Local CI auto-sync from Alliances.wikitext

← Older revision		Revision as of 09:31, 18 September 2026
Line 264:		Line 264:
	Once '''Alliance Territory''' is enabled, your holdings gain shape and specialisation:		Once '''Alliance Territory''' is enabled, your holdings gain shape and specialisation:

	* '''Bastions''' are secondary anchors you plant on a '''standalone''' system — one not bordering anything you already hold. Three archetypes: '''Embassy''' (1 system, max 5), '''War''' (root + 2 Divisions, max 3), and '''Expansion''' (root + 5 Divisions, max 2). Every Bastion is always conquerable, and capturing a Bastion root hands over its '''entire cluster'''.		* '''Bastions''' are secondary anchors you plant on a '''standalone''' system — one not bordering anything you already hold. Three archetypes: '''Embassy''' (1 system, max 8), '''War''' (root + 2 Divisions, max 3), and '''Expansion''' (root + 5 Divisions, max 2). Every Bastion is always conquerable, and capturing a Bastion root hands over its '''entire cluster'''.
	* '''Doctrines''' give each system center — HQ included — exactly one job. '''Fortress''' feeds tonnage capacity and projects defence to neighbours, '''Production Hub''' raises resource output, '''Shipyard Outpost''' cuts ship build time, '''Logistics Center''' hosts a Warp Gate, and '''Anti-Intel & Sensor''' scans and blinds enemy scouts. The HQ is limited to '''Production Hub''' or '''Shipyard Outpost''', and can build that doctrine's signature building alongside its normal HQ buildings.		* '''Doctrines''' give each system center — HQ included — exactly one job. '''Fortress''' feeds tonnage capacity and projects defence to neighbours, '''Production Hub''' raises resource output, '''Shipyard Outpost''' cuts ship build time, '''Logistics Center''' hosts a Warp Gate, and '''Anti-Intel & Sensor''' scans and blinds enemy scouts. The HQ is limited to '''Production Hub''' or '''Shipyard Outpost''', and can build that doctrine's signature building alongside its normal HQ buildings.
	* '''Connection decides value.''' Only systems that chain back to your HQ or to one of your Bastions pay alliance-wide bonuses, project defence, scan, or route warp hops. Orphaned systems keep their buildings and harvest but contribute nothing.		* '''Connection decides value.''' Only systems that chain back to your HQ or to one of your Bastions pay alliance-wide bonuses, project defence, scan, or route warp hops. Orphaned systems keep their buildings and harvest but contribute nothing.
Line 390:		Line 390:
	\|-		\|-
	\|Bastion instances		\|Bastion instances
	\|Embassy 5 · War 3 · Expansion 2		\|Embassy 8 · War 3 · Expansion 2
	\|-		\|-
	\|Doctrines per system		\|Doctrines per system

Admin: Local CI auto-sync from Alliances.wikitext

2026-09-14T12:21:10Z

Local CI auto-sync from Alliances.wikitext

@@ Line 70: / Line 70: @@
 |-
 |'''Officer'''
-|Everything a member can, plus: approve/reject applications, promote/demote members, remove members, edit alliance settings, send broadcasts, manage branding and diplomacy, and upgrade alliance buildings.
+|Everything a member can, plus: approve/reject applications, promote/demote members, remove members, edit alliance settings, send broadcasts, manage branding and diplomacy, and upgrade '''or downgrade''' alliance buildings.
 |-
 |'''Deputy'''
@@ Line 212: / Line 212: @@
 The last three are '''doctrine-gated''': a system must carry the matching doctrine before you can build them. See [[Alliance Territory#doctrines|Alliance Territory → Doctrines]].
 == Territorial control ==

Admin: Sync local draft Alliances.md

2026-09-13T06:21:27Z

Sync local draft Alliances.md

Show changes

Admin at 13:44, 28 July 2026

2026-07-28T13:44:52Z

← Older revision		Revision as of 13:44, 28 July 2026
Line 176:		Line 176:
	<blockquote>Most advanced alliance systems — buildings, conquest, and shared harvest — open up around '''Realm 4'''.</blockquote>		<blockquote>Most advanced alliance systems — buildings, conquest, and shared harvest — open up around '''Realm 4'''.</blockquote>

	== ~~System conquest &~~ control ==		== Territorial control ==
	Alliances ~~can~~ capture star systems ~~by winning a~~ '''coordinated ~~attack~~''' (~~Fleet Coordination System~~) ~~against a system's protector~~. You must be in an active alliance to participate.		'''Territorial control''' is the long game of alliance play: the more star systems your alliance holds — and the longer it holds them — the bigger your shared advantage. A single system is useful, but a '''territory''' of many systems compounds into a serious economic and military edge: more harvest and survey deposits, a larger daily resource pool for every member, more building capacity across your HQ and Divisions, and more ground a rival must fight through before they can hurt you.

			The winning strategy is to '''conquer aggressively, defend relentlessly, and keep expanding''':

			* '''Conquer.''' Alliances capture star systems through '''coordinated (FCS)''' assaults on the system center. With '''Territory Siege''' enabled, that is a two-phase Campaign (Contest, then Takeover) — see Territory Siege. You must be in an active alliance to participate.
			* '''Hold.''' Control fades if a system is left undefended, so treat every capture as territory you must keep — station Guardian fleets and build alliance defenses to secure it for the long haul.
			* '''Expand.''' Keep pushing into neutral and rival systems; the alliances that hold the widest territory the longest dominate the galaxy.

	Once captured:		Once captured:
Line 184:		Line 190:
	* Controlled systems support a shared '''harvest & survey pool''': production each cycle is split between the runner, guardians, and an alliance daily pool that members collect their share from.		* Controlled systems support a shared '''harvest & survey pool''': production each cycle is split between the runner, guardians, and an alliance daily pool that members collect their share from.
	* Controlled systems can be dressed up with '''system themes''' and '''monuments''' (see below).		* Controlled systems can be dressed up with '''system themes''' and '''monuments''' (see below).

			== Territory Siege ==
			When the Territory Siege feature is enabled, taking a neutral system or a rival '''Division''' is no longer a single fight.

			# '''Contest''' — Win an FCS assault → the system is Contested for a '''random 20–28 hours'''. Ownership does '''not''' change yet; income from that system is reduced.
			# '''Takeover''' — A '''2-hour Vulnerable''' window opens. Only the Contester can win a second FCS fight in that window to claim the system.
			# Fail, lose, or miss the window → the holder keeps it, and a '''24-hour''' re-contest cooldown applies.

			Headquarters cannot be sieged. An alliance may have at most '''5''' systems Contested or Vulnerable at once. Station Guardians before the window; amber/red borders on the galaxy map and live countdowns in Alliance Systems / Division Center mark the siege.

			Full rules — Graveyard debris rates, building −3 penalty, diplomacy cancels — are on the dedicated Territory Siege page. In-game: '''Settings → Quick Guides → Alliance Territorial Control'''.

	== Diplomacy & war ==		== Diplomacy & war ==
Line 263:		Line 280:
	\|-		\|-
	\|Vault capacity (per resource)		\|Vault capacity (per resource)
	\|2 billion base, +10 billion per Vault level		\|20 billion base, +20 billion per Vault level
	\|-		\|-
	\|HQ building slots		\|HQ building slots