Per Regna - Recent changes [en]

Score

Admin — Tue, 18 Aug 2026 09:11:47 GMT

Expeditions

Admin — Tue, 18 Aug 2026 09:00:49 GMT

Patch Notes

Admin — Tue, 18 Aug 2026 06:39:09 GMT

← Older revision		Revision as of 06:39, 18 August 2026
Line 1:		Line 1:

			[[Version 1.3.8]]

	[[Version 1.3.7]]		[[Version 1.3.7]]

Version 1.3.8

Admin — Tue, 18 Aug 2026 06:09:33 GMT

Created page with "A logistics-and-fairness release: pull cargo home with '''Collect Resources''', relocate your alliance '''Headquarters''', save '''resource templates''', and keep late-game '''building / research scores''' in line with fleet tonnage — plus harvest payouts that scale with roster size, clearer inbound fleet intel, and a batch of QoL.<blockquote>Headquarters moves are covered in Alliance Territory → Moving the Headquarters. Harvest pool shares are in Alliances. Or open..."

New page

A logistics-and-fairness release: pull cargo home with '''Collect Resources''', relocate your alliance '''Headquarters''', save '''resource templates''', and keep late-game '''building / research scores''' in line with fleet tonnage — plus harvest payouts that scale with roster size, clearer inbound fleet intel, and a batch of QoL.<blockquote>Headquarters moves are covered in Alliance Territory → Moving the Headquarters. Harvest pool shares are in Alliances. Or open '''Settings → Quick Guides''' in-game.</blockquote>

== New Features ==

=== Collect Resources ===

* New mission type: send a fleet to '''your own''' planet or moon, pick up cargo, and fly it home. Alliance systems, allied colonies, and enemy targets are rejected.
* Amounts are decided '''on arrival''' from live stock: take a '''% of full stock''', then clamp so a '''leave-behind''' amount remains. If cargo is short, the take scales down proportionally. '''No tax'''. First fleet to arrive wins the pickup.
* Configure a shared rate + leave-behind, or go '''per resource'''. Save collect setups locally (QoL). Reports show requested rates, leave-behind, stock on arrival, and what was actually taken.
* Open '''Collect''' from your own colony overlay, or pick it in the mission list when the target is yours.

=== Headquarters relocation ===

* A Deputy or Leader can '''Set as HQ''' on a '''connected Division''' or an '''Expansion Bastion''' from '''Alliance → Territories'''.
* The two systems '''trade roles and swap everything built on them''', so HQ-only buildings (Vault, Research Lab, Diplomacy, Archive, Bazaar) travel with the seat.
* When the target is a standalone Expansion Bastion, the old HQ blob must fit Expansion's child cap ('''5''' Divisions) — abandon extras first. An Expansion that already touches the blob is absorbed (old HQ becomes a Division); a distant one swaps so the old HQ becomes the new Expansion root.
* Blocked while either system is under siege. Alliance-wide cooldown '''48 hours'''. A doctrine that is illegal in the new role is cleared and can be picked again for free.

=== Resource templates ===

* Save cargo loadouts — '''fixed amounts''' or '''% of available''', one mode per template — under '''Settings → Fleet''', same pattern as fleet templates.
* Load them from the fleet cargo card when filling Transport (and similar) missions.

=== Fleet template leave-behind ===

* Templates can now be marked '''Leave behind''': the amounts you set stay at the colony, and every remaining ship of those types goes with the fleet — useful for garrison vs sortie compositions.

== Improvements ==

* '''Upgrade ×5''' — QoL commanders can queue five consecutive upgrades when the next build is under '''30 seconds''', resources cover the batch, and the building is not at max / blocked. Hidden whenever a single upgrade would be disabled.
* '''Hostile fleet intel''' — inbound composition unlocks from your '''sensor rate advantage''' vs the attacker (types / counts / full). Equal sensors show full composition; being '''20%''' behind still reveals types. The last '''5 minutes''' before arrival bump intel one tier.
* '''Boss loot reports''' show '''entitled share''' vs '''carried share'''. Uncarried entitled loot stays on the boss — it is no longer water-filled onto high-cargo haulers.
* Bastion and doctrine buildings (Embassy / War / Expansion, Shipyard Outpost, Intelligence Center, Warp Gate) have proper art, including cosmetic variants.
* Fleet ship-quantity +/− no longer caps an entered amount at '''99,999''' per tap.

== Balance ==

* '''Score soft-cap:''' building and research scores count 1:1 up to '''500B''', then diminish toward a ~'''1T''' ceiling so they stay in the same ballpark as tonnage-limited fleet + defense (~500B). Ships, defenses, and alliance donations are not soft-capped. Profile tooltips explain the curve.
* '''Harvest pool floor:''' the daily alliance harvest/survey pool pays out in full only once '''15''' eligible (Realm 4+, active) members are on the roster. A 1-member alliance receives '''1/15'''; the rest is discarded. Matches default alliance size.

== Bug Fixes ==

* FCS battles apply '''class loot multipliers''' and hangar '''stun''' correctly for coordinated strikes; uncarried boss share is no longer redistributed to other participants.
* Tonnage-based bully / war-fatigue checks read fleet + hangar tonnage more consistently.
* Building upgrades no longer fail with an unresolvable build-time in edge cases.
* Latest scout reports look up the stored planet id instead of a brittle JSON extract.

Fleet Combat

Admin — Wed, 05 Aug 2026 11:37:40 GMT

Show changes

Patch Notes

Admin — Tue, 04 Aug 2026 11:21:39 GMT

← Older revision		Revision as of 11:21, 4 August 2026
Line 1:		Line 1:

			[[Version 1.3.7]]

	[[Version 1.3.6]]		[[Version 1.3.6]]

Version 1.3.7

Admin — Tue, 04 Aug 2026 11:20:02 GMT

Created page with "A territory-and-combat release: alliances assign each system a '''Doctrine''', plant '''Bastions''' far from home, and fight '''defence-window sieges''' that scale with Bastion roots — plus '''Carrier''' rapid-fire screens, a '''boss loot''' rework, safer '''expeditions''', score-gap war fatigue, and '''Diplomacy / FCS chat'''.<blockquote>New to Bastions and Doctrines? See the full Alliance Territory guide. Staged conquest and defence windows are in Territory Siege. Bo..."

New page

A territory-and-combat release: alliances assign each system a '''Doctrine''', plant '''Bastions''' far from home, and fight '''defence-window sieges''' that scale with Bastion roots — plus '''Carrier''' rapid-fire screens, a '''boss loot''' rework, safer '''expeditions''', score-gap war fatigue, and '''Diplomacy / FCS chat'''.<blockquote>New to Bastions and Doctrines? See the full Alliance Territory guide. Staged conquest and defence windows are in Territory Siege. Boss haul math is in Pirate Bosses. Or open '''Settings → Quick Guides''' in-game.</blockquote>

== New Features ==

=== Doctrines ===

* Every system center — Headquarters, Division, and Bastion — carries exactly '''one Doctrine''', set on the main building by a Deputy or Leader.
* Five doctrines: '''Production Hub''' (resource production), '''Shipyard Outpost''' (ship build-time reduction), '''Fortress''' (tonnage capacity + neighbour defence projection), '''Logistics Center''' (alliance Warp Gate), and '''Anti-Intel & Sensor''' (alliance scans / counter-scout).
* The signature building is an '''activation gate''': the effect stays at zero until that building exists at level ≥ 1; the ''size'' of the bonus comes from the node's '''main building level'''.
* First doctrine pick is free; switching costs the last upgrade of the main building, may demolish incompatible signature buildings (with confirmation), and starts a '''72h''' cooldown.
* The '''HQ''' may only take Production Hub or Shipyard Outpost. Fortress, Logistics, and Anti-Intel stay out on Divisions and Bastions where positioning still matters.
* Alliance-wide bonuses use a diminishing-returns curve with a hard ceiling (tonnage '''+5%''', production '''+10%''', ship time '''−25%'''). Only '''connected''' (effective) nodes with an active signature contribute.

=== Bastions ===

* Standalone territory anchors for systems that are '''not''' adjacent to your HQ blob. The Bastion main ''is'' the system main — no separate Division Center on that system.
* Three archetypes (instance caps apply):
** '''Embassy''' — 1 system, 0 children (max '''5''')
** '''War''' — root + up to '''2''' child Divisions (max '''3''')
** '''Expansion''' — root + up to '''5''' child Divisions (max '''2''')
* Each Bastion's territory-cap grant matches its child capacity, so a Bastion is '''capacity-neutral''' for the main blob. Capturing a whole cluster nets '''+1''' slot.
* Embassy placement requires hex adjacency to Ally / NAP territory; Expansion needs clearance from at-war territory. Bastions are '''always conquerable'''.
* Abandon (Deputy+) releases the entire cluster, frees the archetype slot, and starts a '''168h''' per-archetype cooldown. Blocked while any siege is open in the cluster.
* New '''Alliance → Territories''' tab shows HQ / Bastion / Division nesting, connection flags, capacity, and live territory effects.

=== Connected territory ===

* Bonuses, Fortress projection, alliance scans, and warp hops only count while a system is '''linked''' back to the HQ blob or its Bastion root over hex adjacency.
* Cutting a corridor orphans systems: they keep buildings, harvest, and missions, but feed '''nothing''' alliance-wide until reconnected.

=== Fortress projection & Anti-Intel ===

* The '''strongest''' adjacent Fortress projects '''50%''' of its held defence into a neighbour's fight. Borrowed units are never consumed from the projecting colony.
* Anti-Intel Intelligence Centers enable vault-paid '''alliance scans''' (radius scales with level) and strengthen counter-scouting nearby.

=== Territory Siege defence windows ===

* Rival-held system conquest no longer uses a fully random Contested timer. After Contest, later stages wait at least '''24h''', then open a random '''2h''' Vulnerable slot inside the defender alliance's '''8-hour defence window''' (start hour chosen by Deputy/Leader, default '''17:00 UTC''').
* '''Divisions / Bastion children / neutrals:''' '''2''' stages (1 wait). '''Bastion roots:''' '''3''' stages (2 waits) — capturing the root takes the '''whole cluster'''.
* Defence window start hour has a '''168h''' change cooldown and is blocked while the alliance has any open siege. If no alliance member has been active within '''7 days''', the defence-window benefit is skipped.
* Contested income ('''×0.5'''), Graveyard debris rates, building penalty ('''−3''' levels; mains floor at 1), and the '''7-day''' previous-owner waiver are unchanged in spirit from 1.3.6.

=== Carrier rapid-fire screen ===

* '''Carriers''' project a rapid-fire screen that cancels part of the enemy RF value aimed at their own ships each round (escorts thinning as Carriers fall).
* The screen is deliberately partial: a line keeps at least '''half''' of its RF advantage and can never be pushed down to RF '''1''' (max cancel fraction '''50%''', capped cancel points).
* '''Guardian''' class amplifies the screen via '''+50% Rapid fire cancel'''. Battle reports, Item Info, and the combat simulator surface the effect.

=== Boss loot in owned space & haul rework ===

* Pirate boss group loot gains a territory ownership modifier: '''+10%''' when the boss sits in a '''hostile''' alliance's system, '''+5%''' in '''your own''' alliance's space, and none in neutral or Ally / NAP territory.
* The modifier is resolved from the alliance '''most participants belong to''', so arrival order or an unallied tag-along cannot rewrite the payout.
* Hauls now extract a '''curve fraction of the boss's actual stockpile''' (not a detached baseline that could empty a thin stock):
** '''Mid-Boss:''' per-player curve '''0.8× → 3.75×'''; a full '''6'''-player rally accesses ≈'''90%''' of the '''25×''' pool.
** '''Boss:''' front-loaded group curve — ~'''60%''' of the '''100×''' pool by '''10''' players, full stock by '''20'''.
* Share blend weights lean on '''fleet build-cost (50%)''', with combat power and damage at '''25%''' each (linear, not ^1.8). Inverse-score boost for smaller commanders caps at '''2×''' the least-boosted fleet.
* High-Boss '''per-alliance''' join cap raised to '''12''' (overall still '''20'''). Full rules: Pirate Bosses.

=== Score-gap protections ===

* '''Score-bully attack limits:''' when your total score is at least '''10×''' the defender's, attacks against that player are capped at '''1''' distinct event per rolling week and '''2''' per rolling month. Strikes within '''1 hour''' on the same pair count as a single event. Scouting remains allowed.
* '''Score-gap war fatigue:''' separately, attacking a much weaker player trims loot — '''−5%''' from '''5×''' score ratio, scaling to '''−20%''' at '''50×+'''. Stacks multiplicatively with repeat-raid war fatigue.

=== Diplomacy & FCS chat ===

* '''Diplomacy chat''' — Ally treaties unlock a shared chat channel between the two alliances (Messages → Diplomacy).
* '''FCS chat''' — each open FCS rally gets a participant-only room for coordinating the strike (Messages → FCS). Rooms stay available for a short window after the rally closes.

== Improvements ==

* Galaxy map and system UIs tint your own systems by doctrine, show Bastion / Division nesting, and surface siege stage countdowns on Bastion mains as well as HQ / Division centers.
* Alliance Admin Settings expose the defence-window start hour for Deputies and Leaders.
* Tonnage summary and resource overlays call out Fortress and Production Hub territory contributions.
* Quick Guides cover Bastions, Doctrines, territory buildings, and the updated Territory Siege flow.
* '''Expedition Protocols''' risk reduction and '''Legendary Expeditions''' insurance now reduce expedition '''ship-loss rate''' and '''stun duration''' (combined, capped at '''25%'''). Per-level values retuned so the cap is reachable without overshooting.
* Mass '''Explorer / Science Vessel''' stacks count at '''1/1000''' of stack size when applying expedition ship-loss percentages (still at least 1 hull if present), so large explorer fleets are not wiped by the same % as combat hull.
* Daily Race reward mails use distinct daily subject/body copy. Direct-message threads can be deleted from your side.
* FCS combat simulation applies per-player class bonuses correctly when mixed fleets fight together.

== Balance ==

* Fortress tonnage, Production Hub output, and Shipyard Outpost build-time bonuses use diminishing returns with hard ceilings so wide empires do not stack endlessly.
* Bastion archetype and territory caps are checked when a Contest '''starts''', not at the final stage — no three-stage surprise blocks.
* System protector garrisons still scale with how many systems you already control.
* Boss loot fairness leans toward invested fleet value and pool access rates that match the designed occupied-rate curve (mid full rally ≈90%; high boss fills by 20).

== Bug Fixes ==

* Fixed pirate stronghold / outpost respawn edge cases that could leave cleared pirate sites stuck or respawning incorrectly.
* Fixed boss FCS target joins that failed to resolve the stronghold when launch stored planet/moon <code>targetType</code> without <code>toPirateStrongholdId</code>.
* Siege, Bastion cluster, and doctrine UI edge cases cleaned up alongside the territory features above.
* FCS per-player bonus and rapid-fire screen edge cases cleaned up in battle reports and the simulator.

Fleet Combat

Admin — Sat, 01 Aug 2026 00:53:08 GMT

Attack Protection

← Older revision		Revision as of 00:53, 1 August 2026
Line 209:		Line 209:
	* the player is significantly weaker than the attacker		* the player is significantly weaker than the attacker

	Protection gradually expires as the empire develops.		Protection gradually expires as the empire develops.

			Extended attack protection for high-score farming of much weaker active players.

			Rules

			* Applies when attacker score ≥ 10× defender score
			* Max 1 attack event / rolling week, 2 / rolling month
			* Strikes within a 1-hour window (from event start) count as one event
			* Inactive / vacation / immunity paths unchanged; scouting still allowed

	----		----

Shipyard

Admin — Fri, 31 Jul 2026 11:43:20 GMT

← Older revision		Revision as of 11:43, 31 July 2026
Line 75:		Line 75:
	* Engineering Lab always matters.		* Engineering Lab always matters.
	* Nano Construction only matters if it is active in your game ruleset.		* Nano Construction only matters if it is active in your game ruleset.
	* No other construction-speed research is referenced in the currently loaded live building/research data for ship production. [~~oai_citation:2‡buildings.json~~]~~(sediment://file_00000000c100720a88ad0b1e9bc0bd5e) [oai_citation:3‡buildings.json~~]~~(sediment://file_00000000c100720a88ad0b1e9bc0bd5e)~~		* No other construction-speed research is referenced in the currently loaded live building/research data for ship production.

			=== References ===

			* [[Tonnage]]

Tonnage

Admin — Fri, 31 Jul 2026 11:42:31 GMT

Created page with "'''Tonnage''' is a soft empire-wide ceiling on military mass — ships and planetary defenses. It does not block construction outright; going over capacity multiplies ship and defense '''build time'''. Capacity comes from your Shipyard and Defense Yard levels across colonies (with moon yards counting at a reduced weight). Long-term power is meant to grow from monuments and strategy more than from endless fleet size. This page covers how capacity is calculated, what coun..."

New page

'''Tonnage''' is a soft empire-wide ceiling on military mass — ships and planetary defenses. It does not block construction outright; going over capacity multiplies ship and defense '''build time'''. Capacity comes from your Shipyard and Defense Yard levels across colonies (with moon yards counting at a reduced weight). Long-term power is meant to grow from monuments and strategy more than from endless fleet size.

This page covers how capacity is calculated, what counts as used tonnage, over-capacity penalties, unit values, alliance bonuses, and related systems (Ship Graveyard, boss FCS, ally moon tests).

== Contents ==

* Why tonnage exists
* How it works
* Empire capacity
* Moon yard contribution (75%)
* Used tonnage
* Over-capacity penalties
* Ships
* Defenses
* Alliance effects
* Related systems
* When to plan around it
* Quick reference
* See also

== Why tonnage exists ==
End-game play centres on PvP, coordinated pirate-boss raids, and alliance warfare. Without a ceiling, fleets and turret walls would grow without bound. Tonnage:

* Caps how large an empire can grow in ships and defenses '''without hard-blocking''' builds
* Slows construction when over capacity instead of forbidding queues
* Pushes late-game power toward '''monuments''', class choices, and strategy rather than raw hull count

Most players hit a meaningful first ceiling after roughly 3–4 months; after that, expansion of military mass is deliberately slower.

== How it works ==
Every ship and defense unit has a catalog '''tonnage''' value. Your empire’s '''used tonnage''' is the sum of those values across hangars, active fleets, and planetary defenses. Your '''tonnage capacity''' is the sum of capacity from all Shipyards and Defense Yards (plus an optional Fortress doctrine bonus).
{| class="wikitable"
!Concept
!Meaning
|-
|'''Capacity'''
|Soft cap from yard levels (and alliance Fortress %)
|-
|'''Used'''
|Hangar ships + active fleets + planetary defenses
|-
|'''Headroom'''
|<code>max(0, capacity − used)</code> — room left under the cap
|-
|'''Penalty'''
|Build-time multiplier when used exceeds capacity
|}
'''Tonnage does not change combat stats''', fleet speed, hangar protection, resource production, or score directly. It only gates construction speed (and a few special systems listed below).

Ships and defenses share '''one combined empire pool'''. Building either type checks the same empire capacity vs the same empire used total.

== Empire capacity ==

=== Yard bases ===
{| class="wikitable"
!Building
!Base <code>tonnageCapacity</code>
!Growth
|-
|'''Shipyard'''
|'''45,000,000'''
|Power curve (below)
|-
|'''Defense Yard'''
|'''25,000,000'''
|Power curve (below)
|-
|'''Alliance Defense Yard'''
|'''2,000,000,000 per level'''
|'''Linear''' (separate system pool — see Alliance Defense Yard)
|}

=== Effective levels ===
Across every colony that has a Shipyard or Defense Yard:
<code>effectiveLevelContribution = isMoon ? level × moonFactor : level
effectiveLevelSum = Σ contributions (separately per building type)</code>
Default <code>moonFactor</code> is '''0.75''' (see Moon yard contribution).

=== Capacity formula (player yards) ===
<code>capacity = floor(baseTonnageCapacity × effectiveLevelSum^1.1)
combinedCapacity = shipyardCapacity + defenseYardCapacity</code>
Shipyard and Defense Yard are computed separately (each with its own base and effective level sum), then '''added'''.

==== Sample capacities (single yard type, planet levels only) ====
{| class="wikitable"
!Effective level
!Shipyard
!Defense Yard
!Combined
|-
|1
|45.0M
|25.0M
|70.0M
|-
|10
|566.5M
|314.7M
|881.2M
|-
|20
|1.21B
|674.6M
|1.89B
|-
|30
|1.90B
|1.05B
|2.95B
|-
|50
|3.33B
|1.85B
|5.18B
|-
|80
|5.58B
|3.10B
|8.68B
|-
|100
|7.13B
|3.96B
|11.09B
|}
Levels from different colonies '''sum''' before the curve. Two planet Shipyards at L15 count as effective level '''30''', not two separate L15 caps.

==== Worked example ====
Planet Shipyard L30 + moon Defense Yard L40:

* Shipyard effective levels: '''30''' → ≈ '''1.90B'''
* Defense Yard effective levels: '''40 × 0.75 = 30''' → ≈ '''1.05B'''
* Combined ≈ '''2.95B'''

== Moon yard contribution (75%) ==
Yards on '''moon''' colonies contribute only a fraction of their building level toward empire capacity:
{| class="wikitable"
!Config
!Default
|-
|<code>tonnage.moonYardCapacityFactor</code>
|'''0.75''' (75%)
|}
<code>moon contribution = buildingLevel × 0.75
planet contribution = buildingLevel × 1.0</code>
In practice this mainly affects '''Defense Yards''': Defense Yard may be built on moons and planets; Shipyard is planet-only under current building rules. The factor still applies to any moon yard that exists in data.

Moon yards are a useful place to add defense capacity — just remember each moon level is worth '''three-quarters''' of a planet level toward the empire cap.

== Used tonnage ==
<code>totalUsedTonnage = hangar ships + active fleets + planetary defenses</code>
{| class="wikitable"
!Component
!What counts
|-
|'''Hangar'''
|All docked ships on all colonies (<code>colony_ships</code>)
|-
|'''Active fleets'''
|Fleets with status <code>traveling</code>, <code>stationed</code>, <code>returning</code>, or <code>onMission</code>
|-
|'''Defenses'''
|All planetary defenses on all colonies
|}
Per unit: <code>catalog.stats.tonnage × quantity</code>.

'''Not counted:'''

* Ship Graveyard '''awaiting''' hull (not yet bought back)
* Permanently destroyed ships that became debris

'''Counted immediately on graveyard buyback:''' recovered ships are added to the colony hangar when purchased, so they consume tonnage '''before''' recovery finishes and they can launch.

== Over-capacity penalties ==
When used tonnage exceeds capacity, ship and defense '''build times''' are multiplied. Below 5% over, there is no penalty.
{| class="wikitable"
!Excess over capacity
!Penalty level
!Build-time multiplier
|-
|< 5%
|—
|'''1×''' (none)
|-
|≥ 5%
|1
|'''5×'''
|-
|≥ 10%
|2
|'''10×'''
|-
|≥ 15%
|3
|'''20×'''
|-
|≥ 20%
|4
|'''100×'''
|}
<code>excessRatio = (used − capacity) / capacity
finalBuildTimeMs = floor(baseBuildTimeMs × multiplier)</code>
The penalty applies to both Shipyard and Defense Yard queues against the '''same''' empire combined totals. Negative energy (a separate system) can pause production entirely; that is not a tonnage effect.

== Ships ==
Each ship type has a fixed catalog tonnage (design baseline: Light Interceptor / Kamikaze = '''1''').
{| class="wikitable"
!Ship
!Tonnage
!Ship
!Tonnage
|-
|Probe
|1
|Carrier
|69
|-
|Kamikaze
|1
|Orbital Refinery
|71
|-
|Cargo Ship
|1
|Destroyer
|81
|-
|Recycler
|3
|Heavy Cruiser
|94
|-
|Freighter
|5
|Science Vessel
|127
|-
|Colony Ship
|6
|Dreadnought
|133
|-
|Fighter
|9
|Planetary Harvester
|147
|-
|Advanced Recycler
|9
|Support Vessel
|165
|-
|Corvette
|20
|Megahauler
|65
|-
|Frigate
|27
|Battlecruiser
|975
|-
|Bomber
|33
|Titan
|1888
|-
|Cruiser
|36
|Colossus
|2829
|-
|Battleship
|45
|
|
|}
Capital hulls (Battlecruiser, Titan, Colossus) dominate late-game used tonnage. Utility ships such as Planetary Harvesters (147 each) also add up quickly if mass-produced.

== Defenses ==
{| class="wikitable"
!Defense
!Tonnage
!Defense
!Tonnage
|-
|Rocket Turret
|1
|EMP Emitter
|24
|-
|Laser Turret
|2
|Railgun Tower
|45
|-
|Flak Cannon
|4
|Plasma Cannon
|53
|-
|Ion Turret
|9
|Large Shield Dome
|57
|-
|Heavy Laser
|12
|Planetary Dome
|210
|-
|Missile Battery
|15
|Prism Tower
|220
|-
|Small Shield Dome
|22
|
|
|}
Defenses share the empire pool with ships. Heavy late-game turrets and domes are expensive in tonnage; stacking them without upgrading yards will push you into penalty bands.

== Alliance effects ==

=== Fortress doctrine (capacity %) ===
Connected '''Fortress''' nodes grant an alliance-wide '''percentage bonus''' to tonnage capacity:
<code>effective% = (tonnageCapPct × L) / (L + tonnageCurveK)
boostedCapacity = floor(baseCapacity × (1 + effective% / 100))</code>
{| class="wikitable"
!Config
!Default
|-
|Cap (<code>territory.tonnageCapPct</code>)
|'''5%'''
|-
|Curve K (<code>territory.tonnageCurveK</code>)
|'''25'''
|}
'''L''' is the sum of main-building levels on connected, active Fortress nodes (with signature building ≥ 1).
{| class="wikitable"
!Fortress levels (L)
!Effective bonus
|-
|25
| +2.50%
|-
|50
| +3.33%
|-
|100
| +4.00%
|-
|200
| +4.44%
|-
|400
| +4.71%
|}
The bonus applies to player empire capacity for members, and to alliance Defense Yard capacity on systems. Full doctrine rules: Alliance Territory.

=== Alliance Defense Yard ===
Alliance system defenses use a '''separate per-system''' pool:
<code>allianceCapacity = yardLevel × 2,000,000,000</code>
Max level 15 → '''30B''' before Fortress %. Penalty compares '''that colony’s defense tonnage''' to '''that system’s''' Alliance Defense Yard capacity — not the player empire pool.

Build speed on the Alliance Defense Yard is separate: '''−25% time per level''' (<code>0.75^level</code>), unrelated to the tonnage curve.

== Related systems ==

=== Ship Graveyard ===
Hull lost in PvP can enter the Ship Graveyard. Buyback is limited by '''tonnage headroom''' (<code>capacity − used</code>). Awaiting graveyard inventory does '''not''' count toward used tonnage until purchased; after buyback, ships count immediately even while recovering.

=== Boss FCS minimum fleet tonnage ===
Boss coordinated strikes require each participating fleet to meet a '''minimum fleet tonnage''' that scales with realm (whole fleet — attack, defense, and support ships all qualify):
{| class="wikitable"
!Realm
!Minimum fleet tonnage
|-
|1
|100,000
|-
|2
|1,000,000
|-
|3
|10,000,000
|-
|4
|1,000,000,000
|}
See Pirate Bosses.

=== Ally moon test attacks ===
Solo fleets attacking an ally’s moon are capped at '''1,000,000,000''' fleet tonnage. Group FCS attacks do not use this exemption path.

== When to plan around it ==
{| class="wikitable"
!Stage
!Guidance
|-
|Early realms
|Basic yard levels usually cover any ship tier you can unlock
|-
|Realm 4+
|Watch the tonnage bar, especially with capital ships
|-
|Approaching / over cap
|Upgrade yards, scrap older hulls, or stay under the limit before queuing more
|}
Actions that help when over capacity: raise Shipyard / Defense Yard levels (planet yards give full weight), scrap or lose obsolete hulls, use alliance Fortress investment for a few percent more capacity, or delay further builds until headroom returns.

== Quick reference ==
{| class="wikitable"
!Item
!Value / rule
|-
|Shipyard base capacity
|45,000,000 × L^1.1
|-
|Defense Yard base capacity
|25,000,000 × L^1.1
|-
|Moon yard level weight
|'''75%'''
|-
|Combined pool
|Ships + defenses vs SY + DY capacity
|-
|Penalty bands
|5%→5×, 10%→10×, 15%→20×, 20%→100×
|-
|Fortress tonnage bonus
|Up to +5%, K=25 diminishing return
|-
|Alliance Defense Yard
|2B × level (linear, per system)
|-
|Combat stats from tonnage?
|'''No'''
|}

== See also ==

* Alliance Territory — Fortress doctrine, tonnage % curve, projection
* Alliances — alliance overview and doctrines summary
* Pirate Bosses — FCS boss raids and minimum fleet tonnage
* Player Classes — monuments and long-term power growth
* In-game Quick Guide: '''Settings → Quick Guides → Tonnage'''

Territory Siege

Admin — Fri, 31 Jul 2026 11:39:22 GMT

Show changes

Alliance Territory

Admin — Fri, 31 Jul 2026 11:38:17 GMT

Created page with "= Bastions & Doctrines = Holding systems is only the first half of alliance territory. The second half is '''shape and specialisation''': which of your systems are ''connected'', what each one is ''for'', and how far from home you can plant a flag. Three ideas drive everything on this page: * '''Connection matters.''' A system only pays alliance-wide bonuses while it is linked back to your Headquarters or to one of your Bastions. Cut the corridor, cut the benefit. * ''..."

New page

= Bastions & Doctrines =
Holding systems is only the first half of alliance territory. The second half is '''shape and specialisation''': which of your systems are ''connected'', what each one is ''for'', and how far from home you can plant a flag.

Three ideas drive everything on this page:

* '''Connection matters.''' A system only pays alliance-wide bonuses while it is linked back to your Headquarters or to one of your Bastions. Cut the corridor, cut the benefit.
* '''Every node has a job.''' Each system carries exactly one '''Doctrine''' — production, shipbuilding, defence, logistics, or intel — and its main building level is the dial.
* '''Distance is buyable, not free.''' '''Bastions''' let you anchor territory far from home, but each archetype is capped, placement is restricted, and every Bastion is always conquerable.

<blockquote>Requires the '''Alliance Territory''' feature to be enabled. Staged sieges additionally require '''Territory Siege''' — see Territory Siege. Territory basics (conquest, harvest, vault, research) are in Alliances.</blockquote>

== Contents ==

* The three tiers
* Connected territory
* Doctrines
* Which doctrines a node may take
* Setting and switching a doctrine
* Territory effects
* Fortress projection
* Logistics Center & warp gates
* Anti-Intel & Sensor
* Bastions
* Founding a Bastion
* Child Divisions
* Embassy stun: when a treaty ends
* Abandoning a Bastion
* Caps & capacity
* Sieges against territory
* Bosses in owned space
* Where to see all of this
* Quick reference

== The three tiers ==
<code>HQ (1 per alliance, cannot be sieged, root of the main blob)
└── Division* (hex-adjacent chain, 1 doctrine each)

Bastion (standalone anchor, planted away from the blob — always conquerable)
├── Embassy Bastion — 1 system, max 5
├── War Bastion — root + 2 kids, max 3
└── Expansion Bastion — root + 5 kids, max 2
└── Division* (adjacent to the cluster, 1 doctrine each)</code>
{| class="wikitable"
!Tier
!Main building
!Slots
!Notes
|-
|'''Headquarters'''
|Alliance Headquarters
|100
|One per alliance. Cannot be Contested or taken. Only place for Research Lab, Vault, Diplomacy Office, Archive, Bazaar. Has '''no''' doctrine.
|-
|'''Division'''
|Division Center
|40
|Must border territory you already hold. Carries one doctrine.
|-
|'''Bastion'''
|Embassy / War / Expansion Bastion
|20 / 40 / 60
|Planted on a standalone system. Carries one doctrine '''and''' hosts child Divisions.
|}
A Bastion is deliberately just ''a Division with an archetype wrapper'': same buildings, same doctrine system, same siege primitive — plus placement rules, child capacity, and one extra siege stage.

'''A Bastion main is the system's main building.''' There is no Division Center on a Bastion system; the Bastion main replaces it. Division Centers are for HQ-blob systems and for a Bastion's child systems.

== Connected territory ==
Your territory is walked as a graph over '''hex adjacency''', from two kinds of root:

# '''The HQ blob''' — starts at your Headquarters and spreads through neighbouring systems that are not attached to a Bastion.
# '''Each Bastion cluster''' — starts at the Bastion root and spreads through the child Divisions attached to ''that'' Bastion, up to its child capacity.

Systems the walk reaches are '''connected''' (the UI calls them effective). Systems it cannot reach are owned but orphaned.
{| class="wikitable"
!Connected node
!Orphaned / stunned node
|-
|Feeds alliance-wide territory effects
|Feeds '''nothing'''
|-
|Projects and receives Fortress defence
|No projection either way
|-
|Can run alliance scans
|Cannot scan
|-
|Routes alliance warp hops
|Not part of the warp network
|-
|Keeps buildings, harvest, survey, missions
|Keeps buildings, harvest, survey, missions
|}
That last row is the important one: an orphaned system is not dead, it is just '''no longer contributing'''. This is what makes cutting a corridor — taking one system in the middle of a chain — a real strategic act rather than a rounding error.

== Doctrines ==
Every Division and Bastion carries exactly '''one''' Doctrine. The Headquarters has none.
{| class="wikitable"
!Doctrine
!What it does
!Signature building
!Alliance-wide effect
|-
|'''Production Hub'''
|Resource extraction hub
|Common '''or''' Rare Extractor
|'''Resource production'''
|-
|'''Shipyard Outpost'''
|Faster ship construction
|Shipyard Outpost
|'''Ship build-time reduction'''
|-
|'''Fortress'''
|Defence, and the only doctrine that '''projects''' defence to neighbours
|Defense Yard
|'''Tonnage capacity'''
|-
|'''Logistics Center'''
|Hosts an alliance Warp Gate for fleet hops
|Warp Gate
|— (utility)
|-
|'''Anti-Intel & Sensor'''
|Alliance scanning and counter-scouting
|Intelligence Center
|— (utility)
|}
'''The signature building is an activation gate, not a cost multiplier.''' The doctrine's effect stays at zero until that building exists at '''level ≥ 1'''; after that the ''size'' of the effect comes from the node's '''main building level''' (Division Center or Bastion main). You level one building per system, not two.

You do '''not''' need the signature building to pick the doctrine — the doctrine is what unlocks it. The order is always: pick doctrine → build signature building → effect switches on.

'''Defense Yard is legal on every doctrine.''' Any node can defend itself; Fortress's identity is ''projection plus tonnage'', not a monopoly on turrets. That also means switching away from Fortress never forces you to demolish a long-invested Defense Yard.

== Which doctrines a node may take ==
{| class="wikitable"
!Node
!Doctrines it may take
!Child Divisions
!Child doctrines
|-
|'''HQ'''
|none
|up to territory cap
|all five
|-
|'''HQ-blob Division'''
|all five
|—
|—
|-
|'''Embassy Bastion'''
|Production Hub, Logistics Center
|0
|—
|-
|'''War Bastion'''
|Fortress, Shipyard Outpost, Anti-Intel & Sensor
|2
|Fortress, Shipyard Outpost, Anti-Intel & Sensor
|-
|'''Expansion Bastion'''
|Production Hub, Logistics Center, Anti-Intel & Sensor
|5
|all five
|}
One consequence worth planning around: '''Fortress — and therefore tonnage capacity — is only reachable on HQ-blob Divisions, War Bastions, and Expansion children.''' Embassy and Expansion ''roots'' cannot take it.

== Setting and switching a doctrine ==
Doctrine is chosen on the system's main building (Division Center or Bastion main) by a '''Deputy or Leader'''. Opening an empty building slot on a node with no doctrine prompts you to choose one first, because the rest of the build list depends on it.

'''First pick is free.''' After that:
{| class="wikitable"
!Switching a doctrine
!
|-
|Cost
|The '''last upgrade cost''' of that node's main building
|-
|Cooldown
|'''72 hours''' per node
|-
|While a siege is open on that system
|'''Blocked'''
|-
|Buildings
|Signature buildings that are illegal under the new doctrine are '''demolished''' — you confirm first, nothing is wiped silently
|}
Only three buildings are doctrine-exclusive and can be demolished this way: '''Shipyard Outpost''', '''Intelligence Center''', and '''Warp Gate'''. Extractors and the Defense Yard are always kept.

The siege block exists for a specific exploit: without it, a defender would flip to Fortress the moment stage 1 opened and flip back afterwards, paying a cost that is trivial next to losing the system.

Note that the first pick also clears illegal exclusive buildings — a legacy system that somehow holds a Warp Gate cannot keep it by choosing Fortress.

== Territory effects ==
Three doctrines pay an alliance-wide bonus. Each uses the same diminishing-returns curve with a hard ceiling:
<code>effective% = cap × L / (L + K)

L = sum of main building levels across your connected, active nodes
that carry that doctrine AND have its signature building at level ≥ 1</code>
{| class="wikitable"
!Effect
!Doctrine
!Ceiling
!<code>K</code>
!Reference budget → value
|-
|'''Tonnage capacity'''
|Fortress
|'''+5%'''
|25
|100 levels → '''4.00%'''
|-
|'''Resource production'''
|Production Hub
|'''+10%'''
|50
|200 levels → '''8.00%'''
|-
|'''Ship build-time reduction'''
|Shipyard Outpost
|'''−25%'''
|60
|250 levels → '''20.16%'''
|}
{| class="wikitable"
!Invested levels
!Tonnage
!Production
!Ship time
|-
|Reference (100 / 200 / 250)
|4.00%
|8.00%
|20.16%
|-
|2× reference
|4.44%
|8.89%
|22.32%
|-
|4× reference
|4.71%
|9.41%
|23.58%
|}
'''Why a curve and not a flat rate.''' Early levels pay ''better'' than a linear rate, so a young alliance feels every upgrade; past the reference budget each level is worth progressively less but '''never zero''', so there are no dead levels and no runaway snowball from simply owning more space. The ceiling is the ceiling — alliance research may make the curve climb faster, but it can never raise the cap.

'''Who gets them:'''
{| class="wikitable"
!Effect
!Eligibility
|-
|Tonnage capacity
|'''Every member''' of the alliance
|-
|Resource production
|Members holding '''≥ 1 colony inside connected territory'''
|-
|Ship build-time reduction
|Members holding '''≥ 1 colony inside connected territory'''
|}
Any colony counts — it does not have to be your capital, and one colony gives the full bonus.

'''Logistics Center and Anti-Intel & Sensor pay no curve bonus.''' They are utility doctrines: their value is warp routing and intel, and a node running one contributes nothing to tonnage, production, or ship time.

== Fortress projection ==
Defence built on a Fortress node counts '''100% on its own system''', and '''50% on hex-adjacent systems your alliance owns'''.

* Only '''one''' Fortress projects onto any given system — the '''strongest''', not the sum.
* "Strongest" is measured in actual '''defence value held''', not building level: a modest Defense Yard sitting on a huge stockpile beats a high-level yard with nothing in it.
* The projecting node must be '''connected''', '''active''', and hold a '''Defense Yard (level ≥ 1)'''.
* Projected units are computed live at battle time, so they always reflect current stock.

'''Projected defence is borrowed, not spent.''' The projecting colony never loses units from a fight it did not host, and the defending colony can never lose more units than it actually owns. Losses and auto-repair are both capped at the defender's real stock.<blockquote>'''Why "strongest" instead of banning adjacent Fortresses.''' On a hex grid, neighbouring cells of a system are themselves partly adjacent, so the largest set of mutually non-adjacent neighbours is three. A no-adjacent-Fortresses rule would still allow 150% borrowed defence, while adding an annoying restriction inside your own territory. Capping at one Fortress caps it at 50% unconditionally, with no placement rule at all.</blockquote>

== Logistics Center & warp gates ==
The alliance '''Warp Gate''' can only be built on a Logistics Center node. Member fleets launching toward a distant target exit through the closest useful gate and fly the short remaining leg, after a warp readiness delay.

Once alliance territory is live, the alliance warp network only includes gates on '''Logistics Center nodes that are connected and active''' — an orphaned Logistics node stops routing until it reconnects. Gates built before territory went live keep working normally while the feature is off.

Fleet-hop mechanics (readiness timing, route selection) are covered in Patch Notes 1.3.6.

== Anti-Intel & Sensor ==
The '''Intelligence Center''' turns a node into both a scanner and a counter-intelligence bubble.

'''Scanning (offence).''' Any active member can trigger an alliance system scan from the node, revealing '''asteroid fields''' and '''pirate strongholds / outposts''' around it.
{| class="wikitable"
!Scan
!Value
|-
|Radius
|<code>ceil(√ main building level)</code> hexes, capped at '''8'''
|-
|Requires
|Anti-Intel doctrine · Intelligence Center ≥ 1 · main building ≥ 1 · node '''connected'''
|-
|Cost
|Gas, paid from the '''alliance vault'''
|-
|Cooldown
|'''10 minutes''' per node, with a live countdown
|}
The cooldown exists because the scan is billed to a shared vault — without it, one member could drain it. Results and cost mirror the personal Sensor Array scan.

'''Counter-intel (defence).''' Enemy scouts aimed at your systems '''within <code>ceil(level / 2)</code> hexes''' (capped at 8) of a qualifying Anti-Intel node face that node's main building level added to your side of the intel maths. Practically: '''higher detection chance''' for the scout, and '''shallower''' reports. The strongest covering node applies.

== Bastions ==
A Bastion is a secondary anchor you plant '''outside''' your main blob — the only way to hold territory that does not chain back to your Headquarters.
{| class="wikitable"
!Archetype
!Max instances
!Child Divisions
!Territory cap granted
!Building slots
!Footprint
|-
|'''Embassy'''
|5
|0
| +0
|20
|1 system
|-
|'''War'''
|3
|2
| +2
|40
|3 systems
|-
|'''Expansion'''
|2
|5
| +5
|60
|6 systems
|}
Both active and stunned Bastions count toward instance caps — they physically occupy a system. Fully built out, Bastions can hold '''26 systems''' outside your blob.

'''Every Bastion is always conquerable.''' There is no safe structure anywhere in this design, deliberately: a permanently protected node feeding alliance bonus ceilings would be the single strongest exploit in the system.

== Founding a Bastion ==

# '''Conquer a standalone system''' — one that is '''not hex-adjacent to any system your alliance already controls.''' If it ''is'' adjacent, it is a normal Division and you will be offered a Division Center instead.
# '''Place a Bastion main as its first alliance building''' (Deputy or Leader). The building you choose ''is'' the archetype, and the system locks to that archetype the moment construction starts.
# Until that build starts, the system counts as an ordinary Division for territory cap and protector difficulty. Cancelling the level-0 main returns it to a plain Division.

Placement rules, validated '''once''':
{| class="wikitable"
!Archetype
!Placement requirement
|-
|'''Embassy'''
|Hex-adjacent to the territory of an '''Ally or NAP''' alliance
|-
|'''War'''
|None beyond standalone + your HQ's galaxy
|-
|'''Expansion'''
|At least '''6 hexes''' from the territory of any alliance you are '''at war''' with
|}
All Bastions must sit in the '''same galaxy as your HQ'''.

"At war" means an active war state only — not NAP, not neutral, not merely un-allied. And because the check happens '''once, at construction''', borders may drift freely afterwards: a later war declaration never invalidates a standing Bastion, and parking a puppet alliance next to a rival's chosen site only delays when they can start building.<blockquote>'''Why the clearance is 6 hexes and not 15–20.''' Exclusion zones grow with the square of their radius. A 20-hex zone around a compact 40-system alliance spans roughly 1,685 of the galaxy's ~11,250 cells, so about '''seven well-spread alliances would saturate the entire map''' and no legal Bastion site would exist anywhere, ever. At 15 hexes it breaks around eleven alliances. Six hexes preserves the "don't plant a fort in someone's face" intent while degrading gracefully as the galaxy fills.</blockquote>

== Child Divisions ==
War and Expansion Bastions host child Divisions, which are ordinary Divisions with their own doctrine.

* A child must be '''hex-adjacent to the Bastion root or to another Division already attached to that same Bastion''', and the cluster must have a free slot.
* A Division Center completed next to one of your Bastions '''attaches automatically''' when the cluster has room; a Deputy can also attach an unparented Division manually.
* Attachment is per-cluster: a system cannot serve two Bastions, and joining one consumes one of that archetype's child slots.

Embassy Bastions have '''no''' child capacity — they are single-system diplomatic footholds.

== Embassy stun: when a treaty ends ==
An Embassy is placed on the strength of a treaty, so it is the one node whose founding condition can be pulled out from under it. If a NAP or Alliance ends — broken, or replaced by war — every Embassy of yours '''adjacent to that former partner's territory''' is '''stunned'''.
{| class="wikitable"
!While stunned ('''48 hours''')
!
|-
|Contributes to territory effects
|'''No'''
|-
|Projects Fortress defence · scans · routes warp
|'''No'''
|-
|Counts toward controlled systems and the Embassy cap
|'''Yes'''
|-
|Can be attacked
|'''Yes'''
|}
Before the timer expires a Deputy or Leader must '''convert it to a War Bastion'''. Conversion:

* requires a '''free War Bastion slot''' (max 3) — if you are at the cap, you must '''abandon''' a War Bastion first, inside the 48h;
* '''always''' requires choosing a new doctrine, because Embassy doctrines (Production Hub / Logistics Center) are never legal on a War Bastion;
* charges the standard doctrine-switch cost and demolishes buildings illegal under the new doctrine (with confirmation);
* '''ignores''' the 72h doctrine cooldown — this is a forced decision, not a strategic flip;
* replaces the Embassy main with a War Bastion main at the same level.

'''If it is not converted in time, the system is lost''' — it reverts to neutral. You are mailed on the treaty break, again at the halfway point, and again shortly before expiry, because a silent destructive deadline reads as a bug.

A stunned Embassy '''captured''' by another alliance arrives '''clean and active''': the stun was a consequence of the previous owner's diplomacy and does not bind the new one.

== Abandoning a Bastion ==
Bastion mains cannot be demolished, so '''abandon''' is the release valve that keeps an alliance at archetype cap from being stuck forever. A Deputy or Leader can abandon a Bastion, freeing that archetype slot immediately.

* '''It releases the entire cluster.''' The root ''and every attached child'' revert to neutral.
* '''Blocked while any siege is open anywhere in the cluster''', so a Bastion about to fall cannot be abandoned to deny the attacker their prize.
* '''168h cooldown per archetype''', so Bastions cannot be hot-swapped around the map.
* Requires an explicit typed confirmation — it is irreversible.

Releasing the children too is not a punishment, it is arithmetic: abandoning a root also removes its territory-cap grant (up to −5), so keeping the children would immediately push you over your own cap. It also keeps the action honest — abandoning is a genuine loss, not a trick for shedding a root while keeping the ground.

Abandon is load-bearing in two places: freeing a slot to '''capture''' another root of that type, and making room for a '''forced Embassy conversion'''.

== Caps & capacity ==
<code>max controlled systems = base (1)
+ 4 × Territorial Expansion research level
+ Σ (each Bastion's cap grant)</code>
Each archetype grants exactly the child capacity it provides ('''Embassy +0 · War +2 · Expansion +5'''), so '''a Bastion is capacity-neutral for your main blob''' — it pays for its own children and nothing more.

'''Archetype caps are enforced when a siege starts, not when it finishes.''' If you already hold 3 War Bastions you cannot ''Contest'' a fourth. Gating at the start is deliberate: nobody should discover the block after completing a three-stage siege. It only blocks the '''root''' — you can still besiege and take a capped cluster's '''child''' Divisions, which are ordinary Divisions consuming ordinary territory cap.

'''Capturing a cluster costs exactly one net slot.''' Because the cap grant matches child capacity, taking an Expansion cluster gains 6 systems and +5 cap; a War cluster gains 3 and +2; an Embassy gains 1 and +0. Every cluster capture nets '''+1''', the same as taking a lone Division — a depleted cluster is even cheaper.

One thing to plan for: '''system protectors scale with how many systems you already control''', so a wide alliance faces meaningfully tougher NPC garrisons on its next conquest than a small one does.

== Sieges against territory ==
Territory shape changes what a siege costs an attacker:
{| class="wikitable"
!Target
!Stages
!Scheduled waits
!Prize
|-
|Neutral system · Division · Bastion '''child'''
|2
|1
|That one system
|-
|Bastion '''root'''
|3
|2
|The '''whole cluster'''
|}
Capturing a root transfers the root and every attached child together, keeping archetype, doctrines, parent links, and buildings (minus the capture penalty). Capturing a child alone yields one unattached Division that may not even connect to anything you own — a clean risk/reward gradient between a long root siege and a quick child raid.

Open sieges elsewhere in the cluster are '''cancelled''' when the root changes hands or the cluster is abandoned.

Full siege rules — stage scheduling, the defence window, debris and Graveyard rates, the building penalty — are on the Territory Siege page.

== Bosses in owned space ==
Pirate boss loot is modified by who owns the system the boss sits in:
{| class="wikitable"
!Boss location
!Group loot modifier
|-
|System owned by a '''hostile''' alliance (raid)
|'''+10%'''
|-
|System owned by '''your own''' alliance (home)
|'''+5%'''
|-
|Neutral space, or an Ally / NAP holder
|none
|}
The modifier applies to the whole shared boss pool, so it is resolved from the alliance '''most participants belong to''' — arrival order and an unallied mercenary tagging along cannot change anyone's payout. See Pirate Bosses for how the pool itself is shared.

== Where to see all of this ==
{| class="wikitable"
!Surface
!What it shows
|-
|'''Alliance → Territories''' tab
|Every node as HQ / Bastion / Division, cluster nesting, connection flags, capacity, and your live territory effects
|-
|'''Galaxy map'''
|Doctrine tint on your own systems, alliance borders, siege borders
|-
|'''System main building modal'''
|Current doctrine, switch action and cooldown, doctrine guide
|-
|'''Tonnage summary'''
|The Fortress contribution to your empire tonnage capacity
|-
|'''Resource overlay'''
|The Production Hub contribution to a colony's output
|-
|'''Alliance → Admin → Settings'''
|Defence window start hour (Deputy+)
|}

== Quick reference ==
{| class="wikitable"
!Thing
!Value
|-
|Doctrines per node
|1 (HQ has none)
|-
|First doctrine pick
|Free
|-
|Doctrine switch cost
|Last upgrade cost of the node's main building
|-
|Doctrine switch cooldown
|72h per node · blocked during a siege on that system
|-
|Who sets doctrine / founds or abandons Bastions
|'''Deputy or Leader'''
|-
|Tonnage (Fortress)
| +5% ceiling, K 25 — all members
|-
|Resource production (Production Hub)
| +10% ceiling, K 50 — needs a colony in connected territory
|-
|Ship build time (Shipyard Outpost)
|−25% ceiling, K 60 — needs a colony in connected territory
|-
|Fortress projection
|50% of the '''strongest''' adjacent Fortress's defence value
|-
|Bastion instances
|Embassy 5 · War 3 · Expansion 2
|-
|Bastion children
|Embassy 0 · War 2 · Expansion 5
|-
|Bastion cap grant
|Embassy +0 · War +2 · Expansion +5
|-
|Bastion slots
|Embassy 20 · War 40 · Expansion 60
|-
|Expansion clearance
|6 hexes from at-war territory
|-
|Embassy placement
|Hex-adjacent to Ally / NAP territory
|-
|Embassy stun
|48h to convert to a War Bastion, or the system is lost
|-
|Abandon cooldown
|168h per archetype · releases the whole cluster
|-
|Territory cap
|1 + 4 per Territorial Expansion level + Bastion grants
|-
|Max Bastion footprint outside the blob
|26 systems
|-
|Alliance scan
|radius <code>ceil(√level)</code> capped 8 · vault-paid · 10 min cooldown
|-
|Counter-intel radius
|<code>ceil(level / 2)</code> capped 8
|-
|Boss loot
| +10% hostile-owned · +5% own · none neutral/friendly
|-
|Feature flags
|<code>allianceTerritory</code> (territory, doctrines, Bastions) · <code>systemSiege</code> (staged sieges)
|}

== Related ==

* [[Alliances]] — vault, research, buildings, diplomacy, harvest
* [[Territory Siege]] — staged conquest, defence windows, capture penalties
* [[Pirate Bosses]] — coordinated boss raids and loot sharing
* [[Player Classes]] — class bonuses on harvest, survey, and FCS
* In-game: '''Settings → Quick Guides → Alliance Territorial Control'''

Version 1.3.6

Admin — Thu, 30 Jul 2026 08:31:22 GMT

← Older revision		Revision as of 08:31, 30 July 2026
Line 39:		Line 39:
	* '''Negative energy''' on a colony now '''pauses ship and defense production''' until energy recovers (same pause/resume pattern as vacation). Resource mines can still be throttled via Production Rate to claw energy back.		* '''Negative energy''' on a colony now '''pauses ship and defense production''' until energy recovers (same pause/resume pattern as vacation). Resource mines can still be throttled via Production Rate to claw energy back.
	* While energy is negative, you can still upgrade '''energy providers''' (Solar Plant, Fusion Reactor, Elerium Reactor). Other queued building upgrades on that colony are cancelled so recovery isn’t blocked.		* While energy is negative, you can still upgrade '''energy providers''' (Solar Plant, Fusion Reactor, Elerium Reactor). Other queued building upgrades on that colony are cancelled so recovery isn’t blocked.
	* '''Moon ~~shipyards~~''' contribute '''75%''' of their level toward empire tonnage capacity (configurable), so moon yards still help — but less than planet yards.		* '''Moon defense yards''' contribute '''75%''' of their level toward empire tonnage capacity (configurable), so moon yards still help — but less than planet yards.
	* Trade offer UI and fleet overlays call out hop routes, readiness, and energy-stressed colonies more clearly.		* Trade offer UI and fleet overlays call out hop routes, readiness, and energy-stressed colonies more clearly.

Patch Notes

Admin — Thu, 30 Jul 2026 07:44:15 GMT

← Older revision		Revision as of 07:44, 30 July 2026
Line 1:		Line 1:

			[[Version 1.3.6]]

	[[Version 1.3.5]]		[[Version 1.3.5]]

Version 1.3.6

Admin — Thu, 30 Jul 2026 07:43:55 GMT

Created page with "A territory-and-travel release: system conquest becomes a '''two-phase Territory Siege''', alliances can stitch space together with '''Warp Gate hops''', and '''Support Vessels''' finally repair hull mid-fight — plus smarter energy recovery when a colony goes dark, tougher (and clearer) pirate bosses, and richer pirate scout intel.<blockquote>New to sieges? See the full Territory Siege guide, or open '''Settings → Quick Guides''' in-game. Alliance territory basics ar..."

New page

A territory-and-travel release: system conquest becomes a '''two-phase Territory Siege''', alliances can stitch space together with '''Warp Gate hops''', and '''Support Vessels''' finally repair hull mid-fight — plus smarter energy recovery when a colony goes dark, tougher (and clearer) pirate bosses, and richer pirate scout intel.<blockquote>New to sieges? See the full Territory Siege guide, or open '''Settings → Quick Guides''' in-game. Alliance territory basics are in Alliances. Boss fights are covered in Pirate Bosses.</blockquote>

== New Features ==

=== Territory Siege (Being tested) ===

* Capturing a Division is no longer a single FCS snap. Attackers must '''Contest''' first, wait a '''random Contested timer''', then win a '''Takeover''' inside a short '''Vulnerable''' window before ownership changes.
* '''Contest''' (Phase 1): win an FCS at the system center → system becomes Contested. Ownership does '''not''' transfer; NPC garrison and alliance buildings stay.
* '''Contested timer:''' random '''20–28 hours''' (nobody picks it — no defender “Defense Hour”).
* '''Vulnerable''' (Phase 2): exactly '''2 hours'''. Only the '''contester''' alliance can finish Takeover with a second FCS win. Fail, miss the window, or hit a gate → defenders keep it + cooldown.
* '''Headquarters cannot be sieged.'''
* While Contested or Vulnerable, that system’s '''daily pool''', '''Harvest''', and '''Survey''' yields are cut to '''×0.5'''.
* Siege ship losses use the '''Ship Graveyard''' with softer debris: Contest ~'''85%''' buyback / ~'''15%''' debris; Takeover ~'''70%''' / ~'''30%'''.
* PvP Takeover of a held Division applies a '''−3 level''' building penalty (buildings drop below level 4 are removed). Retaking a system you held within '''7 days''' waives the penalty.
* Caps: '''5''' open Contests per alliance; '''24h''' re-contest cooldown after fail / expire / cancel. NAP / Ally blocks Contest; a mid-siege protective treaty '''cancels''' the siege.
* Map and Alliance UI show Contested (amber) / Vulnerable (red) borders, live countdowns, and threat badges. Siege mails fire for Contest, Vulnerable, defended, expired, and cancelled outcomes.

=== Alliance Warp Gates & fleet hops ===

* Alliances can build a '''Warp Gate''' on controlled system centers. Member fleets launch from a personal '''moon Warp Gate''', exit through the best available own or alliance gate, then fly the short remaining leg.
* Fleet send can '''Use nearest warp gate'''; ETA includes a '''warp readiness''' delay ('''180s''' at Warp Technology 8, '''−8s''' per level above that, floor '''60s''') plus the short hop flight.
* Gates only help when the exit is meaningfully closer than a direct flight; stale routes refresh before send.

=== Support Vessel field repairs ===

* Surviving '''Support Vessels''' restore combat ships '''each round''' after damage — field-repair capacity scales with vessel count, research, and monuments.
* Repair efficiency ramps from '''80%''' early in the fight to '''100%''' on the final round; restored losses are capped per round (also '''80→100%''').
* Battle reports, the combat simulator, and unit stats show '''field repair''' and ships repaired for both sides.
* The '''Halo Ring''' Core monument now grants '''<code>shipRepairSpeedPct</code> (+15%)''' toward support-vessel repair capacity (stacks with Fleet Preservation and related boosts).

=== Pirate boss combat research ===

* Mid-Bosses and Bosses now fight with a full '''combat-research profile''' (weapons, shields, defense doctrines, and more), applied consistently in battle and on scout reports.
* '''Faction flavor:''' Raider / Fortress / Tech bosses get '''+2''' on their signature techs above the shared base (currently base level '''1''' for both tiers — tuned for gradual rollout).
* Scout reports on pirate strongholds and outposts now include '''strength''', '''faction''', and '''boss tier''' intel when applicable.

== Improvements ==

* '''Negative energy''' on a colony now '''pauses ship and defense production''' until energy recovers (same pause/resume pattern as vacation). Resource mines can still be throttled via Production Rate to claw energy back.
* While energy is negative, you can still upgrade '''energy providers''' (Solar Plant, Fusion Reactor, Elerium Reactor). Other queued building upgrades on that colony are cancelled so recovery isn’t blocked.
* '''Moon shipyards''' contribute '''75%''' of their level toward empire tonnage capacity (configurable), so moon yards still help — but less than planet yards.
* Trade offer UI and fleet overlays call out hop routes, readiness, and energy-stressed colonies more clearly.

== Balance ==

* Pirate boss combat research landed soft (base '''1''', faction '''+2''') after higher initial drafts — bosses are stronger than a naked stronghold, without jumping straight to late-game research walls.
* Support Vessel repair math favors bringing them to long FCS fights (bosses, sieges, prolonged PvP) rather than pure alpha fleets.

== Bug Fixes ==

* Fixed ship/defense queues that could stick paused or lose completion timers after negative-energy pause/resume.
* Energy-provider upgrades no longer get wiped from the queue just because the colony is already in energy debt.
* Warp hop selection rejects mismatched or obsolete exit gates instead of launching on a bad route.
* Various siege mail, scout pirate-intel, and battle-report repair display edge cases cleaned up alongside the features above.

Alliances

Admin — Tue, 28 Jul 2026 13:44:52 GMT

← 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

Territory Siege

Admin — Tue, 28 Jul 2026 13:42:33 GMT

Created page with "'''Territory Siege''' turns system conquest into a '''two-phase campaign''' instead of a single raid. An alliance must '''Contest''' a system, wait through a random timer, then win a '''Takeover''' fight in a short Vulnerable window before ownership changes hands.<blockquote>Requires the '''Territory Siege''' feature to be enabled. Classic instant conquest still applies when the feature is off. You must also have '''System Conquering''' and use '''FCS''' (Fleet Coordinat..."

New page

'''Territory Siege''' turns system conquest into a '''two-phase campaign''' instead of a single raid. An alliance must '''Contest''' a system, wait through a random timer, then win a '''Takeover''' fight in a short Vulnerable window before ownership changes hands.<blockquote>Requires the '''Territory Siege''' feature to be enabled. Classic instant conquest still applies when the feature is off. You must also have '''System Conquering''' and use '''FCS''' (Fleet Coordination System) for system-center assaults. See Alliances → Territorial control.</blockquote>

== Contents ==

* Why sieges exist
* The flow
* Timers
* Contest (Phase 1)
* Vulnerable window (Phase 2)
* Takeover success
* Defending
* Economy while Contested
* Ship losses & Ship Graveyard
* Building penalty
* Limits & cooldowns
* Map & UI signals
* Diplomacy
* Quick reference

== Why sieges exist ==
Under instant conquest, one FCS win could flip a Division while defenders were offline, and full permanent capital losses made serious territory wars feel suicidal.

Sieges keep wars meaningful while:

* Giving both sides '''notice''' before ownership changes
* Using a '''random''' Contested timer (no defender-picked “Defense Hour”) so alliances cannot permanently timezone-tank each other
* Softening hull loss through the '''Ship Graveyard''' with phase-specific debris rates

== The flow ==
<code>Neutral or Held Division
│
│ FCS Contest win
▼
Contested ──(random 20–28h)──► Vulnerable (2h)
│ │
│ ├─ Contester FCS win → ownership flips
│ ├─ Contester loses / blocked → defenders keep it
│ └─ Window ends with no Takeover → defenders keep it
│
└── Headquarters cannot be sieged</code>
Ownership '''never''' changes on Contest — only on a successful '''Takeover''' inside the Vulnerable window.

== Timers ==
{| class="wikitable"
!Phase
!Duration
!Who chooses it?
|-
|'''Contested'''
|Random '''20–28 hours''' after Contest
|Nobody — rolled when Contest succeeds
|-
|'''Vulnerable'''
|Exactly '''2 hours'''
|Starts when Contested ends
|}
Attackers may land the Takeover FCS '''anytime''' in those 2 hours. You do '''not''' need to sit and DPS for two hours — Regna resolves one battle when the fleet arrives.

== Contest (Phase 1) ==

# Scout the system center / rival Division center.
# Launch a '''coordinated FCS''' attack on the system center.
# On victory (and if gates pass), the system becomes '''Contested'''.

'''Contest does not:'''

* Transfer <code>controlling</code> ownership
* Wipe remaining NPC garrison beyond battle losses
* Raze alliance buildings

'''Gates (high level):''' active alliance, System Conquering + Territory Siege enabled, not your own system, not an HQ, not NAP/Ally with the holder, under territory hold cap, system not already sieged / not in re-contest cooldown, and your alliance has fewer than '''5''' open Contests.

Only the alliance that Contested the system may later finish the Takeover.

== Vulnerable window (Phase 2) ==
When Contested ends, the system becomes '''Vulnerable''' for '''2 hours'''.

* The '''contester''' must win another FCS fight at the system center during that window to take ownership.
* If they lose, hit a gate failure (e.g. territory cap), or never show up, the siege resolves as '''defended''' / '''expired''' and the holder keeps the system (with cooldown).

Station Guardians and alliance defenses matter most here — the battle is a snapshot of whoever is stationed (plus garrison and turrets) when the attackers arrive.

== Takeover success ==
On a successful Takeover:

* Ownership transfers to the contester (same HQ / Division rules as before).
* Center military and resources are cleared as on conquest.
* For a '''PvP''' take of a held Division: buildings take a '''level penalty''' (see below) instead of a full raze when Territory Siege is on.
* The usual '''2-day''' grace to build Headquarters / Division Center still applies after a real conquest.
* Harvest / survey / pool income returns to normal once the siege is resolved.

== Defending ==
{| class="wikitable"
!Layer
!Role
|-
|'''Station Guardians'''
|Park fleets on the system center before the Vulnerable window; they fight in the Takeover battle and earn harvest security cuts in peacetime
|-
|'''Defense Yard turrets'''
|Cheap regenerating layer; participate in combat and partially auto-repair
|-
|'''Alliance research'''
|Armor / shields / weapons / garrison capacity strengthen defenses
|}
When Contested mail arrives: form Guardians, refresh station durations, and watch the countdown on the galaxy map, system details, Alliance Systems list, and HQ/Division building modal.

== Economy while Contested ==
While a system is '''Contested''' or '''Vulnerable''':

* That system’s contribution to the alliance '''daily pool''' is reduced ('''×0.5''')
* '''Harvest''' and '''Survey''' mission yields from that system are reduced ('''×0.5''')

Contesting hurts the holder’s economy without giving the attacker free ownership.

== Ship losses & Ship Graveyard ==
Winner of each fight is still decided by the normal battle simulation — not by who lost more ships.

Destroyed '''player''' hull (attackers and stationed Guardians) uses the '''Ship Graveyard''' pipeline with siege debris overrides:
{| class="wikitable"
!Phase
!Debris (gone / salvage field)
!Graveyard buyback
|-
|Contest
|'''~15%'''
|'''~85%'''
|-
|Takeover
|'''~30%'''
|'''~70%'''
|}
NPC protector ships do not enter the Graveyard. Planetary defenses use normal damage + auto-repair (no Graveyard).

== Building penalty ==
When Territory Siege is on and you successfully Take over a '''held''' Division:

* Each alliance building on the center loses '''3 levels'''
* If the new level is '''below 4''', the building is '''removed'''
* If '''your''' alliance lost this system recently and retakes it within '''7 days''', the −3 pass is '''waived''' (you keep buildings as they currently are)

Neutral first takes have no player buildings to penalize. When Territory Siege is '''off''', rival takeovers still use the older full building wipe.

== Limits & cooldowns ==
{| class="wikitable"
!Rule
!Value
|-
|Max open Contests per alliance (Contested + Vulnerable)
|'''5'''
|-
|Re-contest cooldown after fail / expire / cancel
|'''24 hours''' on that system
|-
|Headquarters
|'''Cannot''' be Contested or Taken
|-
|Who can Takeover
|Only the '''Contester'''
|}

== Map & UI signals ==
{| class="wikitable"
!Signal
!Meaning
|-
|'''Amber / warning''' system border
|Contested
|-
|'''Red / danger''' system border
|Vulnerable
|-
|Alliance Systems list flags + countdown
|Per-Division siege status
|-
|HQ / Division Center building modal
|Live countdown + defend hints
|-
|Alliance bottom-nav red border + <code>!</code>
|Alliance system under inbound threat and/or under siege
|-
|System details popup
|Contested / Vulnerable status with live timer
|}
Long-press the Alliance button to open the Alliance Systems selector.

== Diplomacy ==

* You cannot Contest a system held by an alliance you have a '''NAP''' or '''Ally''' treaty with.
* If a protective treaty is formed '''mid-siege''' between contester and defender, the open siege is '''cancelled''' and the holder keeps the system.

== Quick reference ==
{| class="wikitable"
!Thing
!Value
|-
|Contested duration
|Random 20–28h
|-
|Vulnerable window
|2h
|-
|Max open Contests
|5 per alliance
|-
|Failed siege cooldown
|24h
|-
|Contested income factor
|×0.5 (pool + harvest + survey)
|-
|Contest debris / Graveyard
|~15% / ~85%
|-
|Takeover debris / Graveyard
|~30% / ~70%
|-
|Building penalty
|−3 levels; remove if < 4
|-
|Previous-owner waiver
|7 days
|}

== Related ==

* [[Alliances]] — territory, HQ/Divisions, harvest, diplomacy
* [[Player Classes]] — FCS and harvest/survey class bonuses
* [[Resource Protection]] — general PvP loot context
* In-game: '''Settings → Quick Guides → Alliance Territorial Control'''

Version 1.3.5

Admin — Tue, 28 Jul 2026 09:20:19 GMT

Ship Graveyard (beta will be tested internally, will be released later in the week)

← Older revision		Revision as of 09:20, 28 July 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	A class-and-coordination release: your Core monument now defines a full '''player class''' with empire-wide tradeoffs, weekly events gain a '''Daily Race''', allies can trade in private and join each other's FCS rallies, and the scoreboard finally splits into Research / Fleet / Defense — plus deeper expedition rewards, stronger ~~system~~ yields, and a stricter vacation mode.<blockquote>New to classes? See the full Player Classes guide, or open '''Settings → Quick Guides''' in-game. Alliance play is covered in Alliances.</blockquote>		A class-and-coordination release: your Core monument now defines a full '''player class''' with empire-wide tradeoffs, weekly events gain a '''Daily Race''', allies can trade in private and join each other's FCS rallies, and the scoreboard finally splits into Research / Fleet / Defense — plus a '''Ship Graveyard''' for PvP losses, '''early-warning''' attack alerts, deeper expedition rewards, stronger harvest yields, and a stricter vacation mode.<blockquote>New to classes? See the full Player Classes guide, or open '''Settings → Quick Guides''' in-game. Alliance play is covered in Alliances. Resource protection and Titan loot are covered in Resource Protection.</blockquote>

	== New Features ==		== New Features ==
Line 10:		Line 10:
	* Alliance system missions scale with class: '''Industrialist ~4× System Harvest''', '''Explorer ~4× System Survey'''.		* Alliance system missions scale with class: '''Industrialist ~4× System Harvest''', '''Explorer ~4× System Survey'''.
	* '''Industrialist''' Planetary Harvesters use a hybrid log+√ curve soft-capped near '''+250%''' (~20M harvesters), so late-game collector investment stays worthwhile.		* '''Industrialist''' Planetary Harvesters use a hybrid log+√ curve soft-capped near '''+250%''' (~20M harvesters), so late-game collector investment stays worthwhile.
	* Full effect tables, FCS rules, and monument pairings are in [[Player Classes]].		* Full effect tables, FCS rules, and monument pairings are in Player Classes.

	=== Class effects on FCS ===		=== Class effects on FCS ===
Line 19:		Line 19:
	* After loot is split by contribution, personal FCS shares are '''Warlord ×1.2''', '''Guardian / Explorer ×1.1''', '''Industrialist ×1.0'''.		* After loot is split by contribution, personal FCS shares are '''Warlord ×1.2''', '''Guardian / Explorer ×1.1''', '''Industrialist ×1.0'''.
	* An '''Explorer''' in a pirate FCS fight raises the chance of special drops (tech/nano boosts, relic and monument pieces). Battle reports show class loot, coordination, and synergy lines.		* An '''Explorer''' in a pirate FCS fight raises the chance of special drops (tech/nano boosts, relic and monument pieces). Battle reports show class loot, coordination, and synergy lines.

			=== Ship Graveyard (beta will be tested internally, will be released later in the week) ===

			* Hull destroyed in '''player combat''' now goes to a per-colony '''Ship Graveyard''' (open from the Shipyard).
			* Buy back what your '''tonnage headroom''' allows at 9'''0%''' of ship build cost; purchased ships recover gradually up to 7 days depending on the size of te recovery. Min recovery time is 2 days.
			* Unpurchased hull expires after '''14 days''' (expiry refreshes when new losses deposit). Remaining inventory stays until you buy it or it expires.

			=== Early Warning Alerts ===

			* Incoming '''attack''' push alerts no longer fire at launch. Defenders are warned when the fleet is '''10–30 minutes''' from arrival.
			* Base window is '''20 minutes'''. Each '''Radar Station''' level on moons orbiting the target adds '''+1 minute''' (highest moon radar is used).
			* Attackers can shorten the window with '''Frigates''': every '''5%''' of other ships matched by Frigates cuts '''1 minute''', up to '''−20 minutes'''. Short flights already inside the window notify immediately.
			* '''Scout''' pushes still fire at launch only when the probe flies at '''30%+''' speed — slower scouts stay quiet.

	=== Daily Race ===		=== Daily Race ===
Line 34:		Line 47:

	* When opening a coordinated attack, you can '''Allow inter-alliance participation''' so allied alliances can see and join the rally.		* When opening a coordinated attack, you can '''Allow inter-alliance participation''' so allied alliances can see and join the rally.
	* ~~Inter~~-alliance ~~strikes gain~~ '''+20% ~~boss loot~~''' ~~and~~ '''+10% ~~debris~~'''.		* Multi-alliance groups no longer receive extra loot or debris bonuses for spanning alliances — participation stays; the old inter-alliance reward bump is gone.

			=== Titan-Class Mech — PvP loot ===

			* The '''Titan-Class Mech''' (Warlord Core) now grants '''<code>pvpLootPct</code>''': '''+3%''' PvP loot rate at level 1, scaling like other percent monument boosts, hard-capped at '''+30%'''.
			* In FCS attacks, the '''highest''' Titan loot bonus among attackers is used.

			=== Explorer finding auto-share ===

			* When an '''Explorer''' expedition finds pirate bosses, scout reports are saved to mail. By default they are also '''shared to alliance chat'''.
			* Toggle under '''Settings → Expedition → Auto-share boss scout reports'''.

	=== Granular leaderboard ===		=== Granular leaderboard ===
Line 48:		Line 71:
	* Expedition '''depths 6–10''' now have proper earning multipliers (continuing the climb past depth 5 instead of falling back), matching Legendary Expeditions + Orrery unlocks.		* Expedition '''depths 6–10''' now have proper earning multipliers (continuing the climb past depth 5 instead of falling back), matching Legendary Expeditions + Orrery unlocks.
	* Event and trade UIs were refreshed for Daily Race sorting, ally-offer badges, and clearer accept-offer flows.		* Event and trade UIs were refreshed for Daily Race sorting, ally-offer badges, and clearer accept-offer flows.
			* Ship and defense '''build-time floors''' are now tiered by ship realm and player realm (with class specialty floors for Planetary Harvester / Explorer / Advanced Recycler), so early-realm queues stay paced while Realm IV+ can still sprint.
			* Early-realm research timing uses each tech's '''<code>buildTimeMultiplier</code>''' instead of a flat ×2 per level.

	== Balance ==		== Balance ==

	* '''System Harvest''' yields were raised substantially: active cycle output is about '''6×''' higher per production unit, and passive per-system common/rare income about '''3.5×'''.		* '''System Harvest''' yields were raised substantially: active cycle output is about '''6×''' higher per production unit, and passive per-system common/rare income about '''3.5×'''. Hauls now use per-resource abundance rates, and the mission runner's cut gets a '''2.5×''' cargo bonus (without taking from the pool).
			* '''Nebula gas harvest''' now converts zone gas to cargo at '''3×''' (same pattern as asteroid ore refining), so gas runs keep pace with other harvest missions.
	* '''Realm 4 catch-up:''' trailing Realm 4 commanders (by total score) receive stronger expedition '''nano-boost''' grants with a '''ship-biased''' category roll, so late-realm fleets can close the gap faster.		* '''Realm 4 catch-up:''' trailing Realm 4 commanders (by total score) receive stronger expedition '''nano-boost''' grants with a '''ship-biased''' category roll, so late-realm fleets can close the gap faster.

Line 57:		Line 83:

	* Fixed monument inventory spare / upgrade-eligibility mismatches when the best owned copy was deployed.		* Fixed monument inventory spare / upgrade-eligibility mismatches when the best owned copy was deployed.
			* '''FCS''' fights now count as a '''single raid''' toward immunity (not one per participant), so coordinated attacks no longer trip protection unfairly.
			* '''Hull / armor research''' now correctly reduces ships destroyed in combat, not only the numbers shown on reports.
			* Alliance chat messages keep stable timestamps when they arrive live.
			* Battle simulation performance improved for large fleets.
	* Various class-effect, FCS loot, and vacation production edge cases cleaned up alongside the features above.		* Various class-effect, FCS loot, and vacation production edge cases cleaned up alongside the features above.
	* ~~Production side effect to player base has been diagnosed and fixed, required some minor resource rollback.~~
			*

Patch Notes

Admin — Thu, 23 Jul 2026 14:31:54 GMT

← Older revision		Revision as of 14:31, 23 July 2026
Line 1:		Line 1:

			[[Version 1.3.5]]

	[[Version 1.3.4]]		[[Version 1.3.4]]

Version 1.3.5

Admin — Thu, 23 Jul 2026 14:31:29 GMT

Created page with "A class-and-coordination release: your Core monument now defines a full '''player class''' with empire-wide tradeoffs, weekly events gain a '''Daily Race''', allies can trade in private and join each other's FCS rallies, and the scoreboard finally splits into Research / Fleet / Defense — plus deeper expedition rewards, stronger system yields, and a stricter vacation mode.<blockquote>New to classes? See the full Player Classes guide, or open '''Settings → Quick Guides..."

New page

A class-and-coordination release: your Core monument now defines a full '''player class''' with empire-wide tradeoffs, weekly events gain a '''Daily Race''', allies can trade in private and join each other's FCS rallies, and the scoreboard finally splits into Research / Fleet / Defense — plus deeper expedition rewards, stronger system yields, and a stricter vacation mode.<blockquote>New to classes? See the full Player Classes guide, or open '''Settings → Quick Guides''' in-game. Alliance play is covered in Alliances.</blockquote>

== New Features ==

=== Player Classes ===

* Deploying a '''Core monument''' on your capital now sets your primary class: '''Warlord''', '''Guardian''', '''Explorer''', or '''Industrialist'''.
* Each class applies empire-wide '''bonuses and penalties''' — fleet speed and attack, defenses, expedition success and loot, harvest and convoy speed, trade fees, and more. Your live numbers show on your '''profile under Class Effects'''.
* '''Support''' monuments still add Sub Class tags and their own boosts; they do '''not''' change the Core class effect table.
* Alliance system missions scale with class: '''Industrialist ~4× System Harvest''', '''Explorer ~4× System Survey'''.
* '''Industrialist''' Planetary Harvesters use a hybrid log+√ curve soft-capped near '''+250%''' (~20M harvesters), so late-game collector investment stays worthwhile.
* Full effect tables, FCS rules, and monument pairings are in [[Player Classes]].

=== Class effects on FCS ===

* Coordinated attacks (including pirate bosses and system conquest) now respect class combat bonuses '''per participant's own ships'''.
* Class '''hostile fleet speed''' is solo-attack only — joining as Industrialist or Guardian will '''not''' slow an FCS rally.
* Mixed-class groups earn a loot synergy bonus: '''+5% / +7.5% / +10%''' for '''2 / 3 / 4''' distinct classes in the group.
* After loot is split by contribution, personal FCS shares are '''Warlord ×1.2''', '''Guardian / Explorer ×1.1''', '''Industrialist ×1.0'''.
* An '''Explorer''' in a pirate FCS fight raises the chance of special drops (tech/nano boosts, relic and monument pieces). Battle reports show class loot, coordination, and synergy lines.

=== Daily Race ===

* Weekly events now include a '''Daily Race''': today's score has its own rank, reset timer, and reward floor.
* Top finishers of the day earn smaller bonus rewards (Champion / Runner-up / Contender tiers), separate from the weekly payout.
* Event leaderboards can toggle between '''Weekly''' and '''Daily''' views; results also arrive by mail.

=== Ally Offers ===

* Trade offers can be marked '''Ally Offer''': visible only to your alliance and '''allied''' alliances (not the public market).
* Ally offers allow up to '''5×''' the normal Trading Center resource batch limit — useful for large allied transfers.

=== Inter-alliance FCS ===

* When opening a coordinated attack, you can '''Allow inter-alliance participation''' so allied alliances can see and join the rally.
* Inter-alliance strikes gain '''+20% boss loot''' and '''+10% debris'''.

=== Granular leaderboard ===

* The player scoreboard can now be sorted by '''Total''', '''Research''', '''Fleet''', or '''Defense''' — so specialists can climb their own ladder, not only overall score.

== Improvements ==

* '''Fleet Templates''' can be edited from Settings (same composition controls as the send screen, without launching a fleet).
* Sensor scans can '''scroll to load farther systems''' instead of stopping at the first page of results.
* '''Vacation Mode''' now pauses '''resource, ship, and defense production''' while active. Activation also requires ship/defense builds to finish, and is blocked while a hostile fleet is inbound.
* Monument upgrade '''spare counting''' now matches the real upgrade target — including when that best copy is already '''deployed''' — so the inventory no longer claims an upgrade you can't afford.
* Expedition '''depths 6–10''' now have proper earning multipliers (continuing the climb past depth 5 instead of falling back), matching Legendary Expeditions + Orrery unlocks.
* Event and trade UIs were refreshed for Daily Race sorting, ally-offer badges, and clearer accept-offer flows.

== Balance ==

* '''System Harvest''' yields were raised substantially: active cycle output is about '''6×''' higher per production unit, and passive per-system common/rare income about '''3.5×'''.
* '''Realm 4 catch-up:''' trailing Realm 4 commanders (by total score) receive stronger expedition '''nano-boost''' grants with a '''ship-biased''' category roll, so late-realm fleets can close the gap faster.

== Bug Fixes ==

* Fixed monument inventory spare / upgrade-eligibility mismatches when the best owned copy was deployed.
* Various class-effect, FCS loot, and vacation production edge cases cleaned up alongside the features above.
* Production side effect to player base has been diagnosed and fixed, required some minor resource rollback.

Player Classes

Admin — Thu, 23 Jul 2026 14:22:12 GMT

Show changes