Fleet Combat - Revision history

Admin: Local CI auto-sync from FleetCombat.wikitext

2026-10-10T13:28:03Z

Local CI auto-sync from FleetCombat.wikitext

@@ Line 101: / Line 101: @@
 |-
 |Event grouping
-|Strikes within '''1 hour''' of the event start count as '''one''' event
+|Strikes within '''2 hours''' of the event's first strike count as '''one''' event (the window is not extended by later strikes)
 |-
 |Scouting
@@ Line 111: / Line 114: @@
 Inactive / vacation / immunity paths are unchanged by this rule.
 === Repeat-raid war fatigue (loot rate) ===
@@ Line 160: / Line 165: @@
 Tonnage-gap fatigue can continue until loot is wiped ('''0%'''). '''Repeat fatigue × tonnage-gap fatigue stack''' (multiply together).
 === Raid immunity trigger ===
 If an '''active''' defender takes '''3''' distinct raid events within '''6 hours''', they gain a '''24-hour''' immunity shield (attack and scout blocked). One FCS battle counts as '''one''' raid for this counter. Inactive players never gain this shield.
 === Hangar protection (not an attack ban) ===
@@ Line 223: / Line 275: @@
 |'''Defenses'''
 |No graveyard. ~'''50%''' of destroyed defense value becomes debris; '''50%''' of destroyed defenses '''auto-restore''' after battle (raised by [[Defensive Logistics]]).
 |}
@@ Line 285: / Line 340: @@
 |-
 |'''Score-bully limits'''
-|High fleet-tonnage farmers capped at 1/week and 2/month vs much weaker actives (3× fleet tonnage) — see [[#score bully limits anti farm|above]]
+|High fleet-tonnage farmers capped at 1/week and 2/month vs much weaker actives (3× fleet tonnage); strikes within 2 hours of the first count as the same attack; no caps for 24 hours after winning a fair fight — see [[#score bully limits anti farm|above]]
 |-
 |'''New colony alone'''

Admin: Local CI auto-sync from FleetCombat.wikitext

2026-10-06T10:09:59Z

Local CI auto-sync from FleetCombat.wikitext

← Older revision		Revision as of 10:09, 6 October 2026
Line 201:		Line 201:
	\|}		\|}

	'''[[Engines]]''' stored in the target's Colony Stores are loot too (Realm 4+): the same loot rate and protection apply, engines beyond warehouse capacity are fully exposed, and engines share the cargo with resources in proportion (whole engines). ~~Running~~ engines and engines still being forged are safe; pirates and NPCs never take engines.		'''[[Engines]]''' stored in the target's Colony Stores are loot too (Realm 4+): the same loot rate and protection apply, engines beyond warehouse capacity are fully exposed, and engines share the cargo with resources in proportion (whole engines). Each '''installed''' engine (not overcharged) also rolls once: a 25% chance to be stolen (if the raiders have free cargo for it) and a 15% chance to be destroyed, both scaled by war fatigue. Joint (FCS) attacks take no engines: no stored ones, and installed ones can only be destroyed. Overcharged engines and engines still being forged are safe; pirates and NPCs never take engines.

	You never wipe a well-warehoused active economy in one hit; overflow and low protection are what make raids fat.		You never wipe a well-warehoused active economy in one hit; overflow and low protection are what make raids fat.
Line 233:		Line 233:
	Example: an attacker with high Salvage converts more of the defender's destroyed hull into the debris field (less defender graveyard). The attacker's own lost ships use the defender's Salvage rate instead.		Example: an attacker with high Salvage converts more of the defender's destroyed hull into the debris field (less defender graveyard). The attacker's own lost ships use the defender's Salvage rate instead.

	A '''Graveyard Reconstruction Engine''' in the Shipyard's Engine Bay speeds up recovery of every batch on that planet (~~×1.5~~ / ×2 / ×3 for ~~24h,~~ never below 12h per batch). See [[Engines]].		A '''Graveyard Reconstruction Engine''' in the Shipyard's Engine Bay speeds up recovery of every batch on that planet (+15 / 25 / 35% passive, or +50 / 100 / 200% for 7 days when overcharged; never below 12h per batch). See [[Engines]].

	Moon losses map to the parent planet’s graveyard UI. Territory Siege phases can override the debris / graveyard split — see [[Territory Siege]].		Moon losses map to the parent planet’s graveyard UI. Territory Siege phases can override the debris / graveyard split — see [[Territory Siege]].

Admin: Local CI auto-sync from FleetCombat.wikitext

2026-10-05T15:05:01Z

Local CI auto-sync from FleetCombat.wikitext

← Older revision		Revision as of 15:05, 5 October 2026
Line 200:		Line 200:
	\|Mixed-class synergy raises group loot access; personal class multipliers reallocate shares — see [[Player Classes#fcs coordinated attacks\|Player Classes → FCS]]		\|Mixed-class synergy raises group loot access; personal class multipliers reallocate shares — see [[Player Classes#fcs coordinated attacks\|Player Classes → FCS]]
	\|}		\|}

			'''[[Engines]]''' stored in the target's Colony Stores are loot too (Realm 4+): the same loot rate and protection apply, engines beyond warehouse capacity are fully exposed, and engines share the cargo with resources in proportion (whole engines). Running engines and engines still being forged are safe; pirates and NPCs never take engines.

	You never wipe a well-warehoused active economy in one hit; overflow and low protection are what make raids fat.		You never wipe a well-warehoused active economy in one hit; overflow and low protection are what make raids fat.
Line 230:		Line 232:

	Example: an attacker with high Salvage converts more of the defender's destroyed hull into the debris field (less defender graveyard). The attacker's own lost ships use the defender's Salvage rate instead.		Example: an attacker with high Salvage converts more of the defender's destroyed hull into the debris field (less defender graveyard). The attacker's own lost ships use the defender's Salvage rate instead.

			A '''Graveyard Reconstruction Engine''' in the Shipyard's Engine Bay speeds up recovery of every batch on that planet (×1.5 / ×2 / ×3 for 24h, never below 12h per batch). See [[Engines]].

	Moon losses map to the parent planet’s graveyard UI. Territory Siege phases can override the debris / graveyard split — see [[Territory Siege]].		Moon losses map to the parent planet’s graveyard UI. Territory Siege phases can override the debris / graveyard split — see [[Territory Siege]].

Admin: Local CI auto-sync from FleetCombat.wikitext

2026-10-01T14:52:27Z

Local CI auto-sync from FleetCombat.wikitext

← Older revision		Revision as of 14:52, 1 October 2026
Line 220:		Line 220:
	\|-		\|-
	\|'''Defenses'''		\|'''Defenses'''
	\|No graveyard. ~'''50%''' of destroyed defense value becomes debris; ~~about~~ '''70%''' of destroyed defenses ~~can~~ '''auto-restore''' after battle.		\|No graveyard. ~'''50%''' of destroyed defense value becomes debris; '''50%''' of destroyed defenses '''auto-restore''' after battle (raised by [[Defensive Logistics]]).
	\|}		\|}

Admin: Local CI auto-sync from FleetCombat.wikitext

2026-09-22T10:40:50Z

Local CI auto-sync from FleetCombat.wikitext

← Older revision		Revision as of 10:40, 22 September 2026
Line 80:		Line 80:
	* '''Active-player PvP lock''' — attacks against '''active''' players are blocked in the listed realms, but '''pirate''' and '''inactive''' targets remain attackable.		* '''Active-player PvP lock''' — attacks against '''active''' players are blocked in the listed realms, but '''pirate''' and '''inactive''' targets remain attackable.

	When a lock is active, the ~~game shows a maintenance message; if an end~~ time is set~~, the~~ message ~~also shows when combat is expected~~ to ~~resume~~. Fleets already in flight are not cancelled.		When a lock is active, returning commanders in an affected realm see a brief launch warning (at most once per day) with the expected resume time when one is set. The same maintenance message appears if you try to launch a blocked attack. New commanders on first access do not see the launch warning. Fleets already in flight are not cancelled.

	----		----

Admin: Local CI auto-sync from FleetCombat.wikitext

2026-09-20T10:59:37Z

Local CI auto-sync from FleetCombat.wikitext

← Older revision		Revision as of 10:59, 20 September 2026
Line 75:		Line 75:
	'''Attacker immunity:''' launching a PvP attack against an '''active''' defender is allowed while you still have an immunity shield — completing that attack '''removes''' your immunity. Attacking inactive / vacation / banned targets does not strip it.		'''Attacker immunity:''' launching a PvP attack against an '''active''' defender is allowed while you still have an immunity shield — completing that attack '''removes''' your immunity. Attacking inactive / vacation / banned targets does not strip it.

	'''Realm restrictions:''' ~~some~~ realms ~~may disallow~~ PvP ~~via <code>~~combat.~~noAttackRealms</code>~~.		'''Realm restrictions (maintenance):''' operators may temporarily lock combat per realm in two modes:

			* '''Full attack lock''' — no new attack missions from or into the listed realms. Potentially a battle mechanics update in place or a change on ship&defense battle stats.
			* '''Active-player PvP lock''' — attacks against '''active''' players are blocked in the listed realms, but '''pirate''' and '''inactive''' targets remain attackable.

			When a lock is active, the game shows a maintenance message; if an end time is set, the message also shows when combat is expected to resume. Fleets already in flight are not cancelled.

	----		----

Admin: Local CI auto-sync from FleetCombat.wikitext

2026-09-17T21:36:24Z

Local CI auto-sync from FleetCombat.wikitext

← Older revision		Revision as of 21:36, 17 September 2026
Line 247:		Line 247:
	\|-		\|-
	\|'''Attacker (PvP)'''		\|'''Attacker (PvP)'''
	\|No hangar stun from the battle itself; losses go to debris / graveyard. Returning attack fleets can enter a '''PvP retaliation window''' (~'''2–24 hours''' by return tonnage) where surviving hull docks '''outside''' hangar protection and is scoutable/attackable — ~~see~~ [[Fleet Stun]].		\|No hangar stun from the battle itself; losses go to debris / graveyard. Returning attack fleets can enter a '''PvP retaliation window''' (~'''2–24 hours''' by return tonnage) where surviving hull docks '''outside''' hangar protection and is scoutable/attackable — except after attacks on '''inactive''' players (or Pirate / Riftwake NPCs), which skip the window. See [[Fleet Stun]].
	\|-		\|-
	\|'''Expeditions / Nebula'''		\|'''Expeditions / Nebula'''
Line 319:		Line 319:
	# Each side aims fire by '''[[Targeting and Priority\|target priority]]''' (front screens before mid combat before rear logistics). Planetary turrets use the same ship tiers; colony ships + turrets merge into '''one''' priority pass against the attacker.		# Each side aims fire by '''[[Targeting and Priority\|target priority]]''' (front screens before mid combat before rear logistics). Planetary turrets use the same ship tiers; colony ships + turrets merge into '''one''' priority pass against the attacker.
	# Incoming fire at defenses uses '''dome-first''' soak (domes before armed turrets), with barrier/absorption reductions while domes live — see [[Damage and Shields]].		# Incoming fire at defenses uses '''dome-first''' soak (domes before armed turrets), with barrier/absorption reductions while domes live — see [[Damage and Shields]].
	# Weapons resolve as '''shots''' ([[Rapid Fire]]): RF adds expected extra shots against preferred types; '''overkill does not splash'''.		# Weapons resolve as '''shots''' ([[Rapid Fire]]): RF adds expected extra shots against preferred types; '''overkill does not splash'''. Realm 4 capitals use high anti-fodder RF (see [[Rapid Fire]]) so soft screens do not erase capital value.
	# Each side’s '''shield pool''' absorbs first (ships and turrets share one pool when firing at the attacker); excess damages '''hull'''.		# Each side’s '''shield pool''' absorbs first (ships and turrets share one pool when firing at the attacker); excess damages '''hull'''.
	# Destroyed ships leave combat and feed debris / graveyard splits; destroyed defenses follow repair / debris rules.		# Destroyed ships leave combat and feed debris / graveyard splits; destroyed defenses follow repair / debris rules.

Admin: Local CI auto-sync from FleetCombat.wikitext

2026-09-16T13:06:23Z

Local CI auto-sync from FleetCombat.wikitext

← Older revision		Revision as of 13:06, 16 September 2026
Line 209:		Line 209:
	\|-		\|-
	\|'''Debris field'''		\|'''Debris field'''
	\|A share of lost hull becomes recyclable materials at the battle location (Recyclers collect). ~~Default~~ ship debris rate ~~is about~~ '''30%''' ~~of losses (~~realm ~~/ Salvage research can~~ adjust).		\|A share of lost hull becomes recyclable materials at the battle location (Recyclers collect). Base ship debris rate comes from combat config (often around '''30–50%'''); [[Salvage Operations]] and realm adjust it.
	\|-		\|-
	\|'''Ship Graveyard'''		\|'''Ship Graveyard'''
	\|The rest of lost hull deposits at the colony Shipyard as recoverable ships (feature-flagged). Buy back at '''90%''' build cost within '''tonnage headroom'''; unpurchased hull expires in '''14 days'''; after buyback, ships recover over '''~2–7 days''' before they can launch.		\|The rest of lost hull deposits at the colony Shipyard as recoverable ships (feature-flagged). Buy back at '''90%''' build cost within '''tonnage headroom'''; unpurchased hull expires in '''14 days'''; after buyback, ships recover over '''~2–7 days''' before they can launch. If your empire is near the tonnage cap, less than the debris-rate remainder may deposit — the battle report '''Graveyard rate''' is the share of your losses that actually entered the graveyard after that limit.
	\|-		\|-
	\|'''Defenses'''		\|'''Defenses'''
	\|No graveyard. ~'''50%''' of destroyed defense value becomes debris; about '''70%''' of destroyed defenses can '''auto-restore''' after battle.		\|No graveyard. ~'''50%''' of destroyed defense value becomes debris; about '''70%''' of destroyed defenses can '''auto-restore''' after battle.
	\|}		\|}

			'''Who decides the rate (PvP):''' Salvage is '''cross-side''' so researching it improves scrap from the enemy, not your own losses.

			* The '''attacker''''s Salvage sets debris (vs graveyard) for '''defender''' ships and defenses.
			* The '''defender''''s Salvage sets debris (vs graveyard) for the '''attacking fleet''''s losses.
			* Realm scaling uses the battle realm (attacker) for both sides.

			Example: an attacker with high Salvage converts more of the defender's destroyed hull into the debris field (less defender graveyard). The attacker's own lost ships use the defender's Salvage rate instead.

	Moon losses map to the parent planet’s graveyard UI. Territory Siege phases can override the debris / graveyard split — see [[Territory Siege]].		Moon losses map to the parent planet’s graveyard UI. Territory Siege phases can override the debris / graveyard split — see [[Territory Siege]].

	Pirate fights use ~~pirate debris rules~~ (no player graveyard for pirate hull).		Pirate fights use a single '''Debris rate''' (attacker Salvage) for both sides — the same fraction drives scrap resources. No player graveyard for pirate hull.

	----		----

Admin: Local CI auto-sync from FleetCombat.wikitext

2026-09-14T12:21:13Z

Local CI auto-sync from FleetCombat.wikitext

← Older revision		Revision as of 12:21, 14 September 2026
Line 1:		Line 1:
	= Fleet Combat =		= Fleet Combat =

	Fleet combat in Regna happens when fleets engage pirates, other empires, or planetary defenses. Battles resolve automatically over multiple rounds: ships pick targets, fire, shields absorb, hull takes the rest, and destroyed units leave the fight.		Fleet combat in Per Regna happens when fleets engage pirates, other empires, or planetary defenses. Battles resolve automatically over multiple rounds: ships pick targets, fire, shields absorb, hull takes the rest, and destroyed units leave the fight.

	This page answers the practical questions commanders ask before and after a strike. For loot math in depth, see [[Resource Protection]] and [[~~Battle Looting.wikitext\|~~Battle Looting]]. For hangar / stun recovery, see [[~~Fleet Stun.wikitext\|~~Fleet Stun]]. For hull buyback limits, see [[Tonnage#ship graveyard\|Tonnage → Ship Graveyard]].		This page answers the practical questions commanders ask before and after a strike. For loot math in depth, see [[Resource Protection]] and [[Battle Looting]]. For hangar / stun recovery, see [[Fleet Stun]]. For hull buyback limits, see [[Tonnage#ship graveyard\|Tonnage → Ship Graveyard]].

	== Contents ==		== Contents ==
Line 162:		Line 162:
	=== Hangar protection (not an attack ban) ===		=== Hangar protection (not an attack ban) ===

	Fleets in a '''protected Fleet Hangar''' do not enter the fight until exposed. If you are over hangar capacity, only a '''proportional share''' of each ship type is protected — the rest fights and can be destroyed (see [[~~Fleet Stun.wikitext\|~~Fleet Stun]]). Switching protected ↔ exposed takes '''10 minutes''' each way. You cannot change hangar mode while stunned. Protected ships still matter for [[#is there stun\|stun]] after a lost or drawn defense. '''Stationary''' hull (planetary collectors, etc.) never uses hangar capacity.		Fleets in a '''protected Fleet Hangar''' do not enter the fight until exposed. If you are over hangar capacity, only a '''proportional share''' of each ship type is protected — the rest fights and can be destroyed (see [[Fleet Stun]]). Switching protected ↔ exposed takes '''10 minutes''' each way. You cannot change hangar mode while stunned. Protected ships still matter for [[#is there stun\|stun]] after a lost or drawn defense. '''Stationary''' hull (planetary collectors, etc.) never uses hangar capacity.

	----		----
Line 181:		Line 181:
	\|-		\|-
	\|'''Active PvP'''		\|'''Active PvP'''
	\|Exposed × loot rate × fatigue, then cargo. Full formulas: [[Resource Protection]] · [[~~Battle Looting.wikitext\|~~Battle Looting]]		\|Exposed × loot rate × fatigue, then cargo. Full formulas: [[Resource Protection]] · [[Battle Looting]]
	\|-		\|-
	\|'''Inactive colony'''		\|'''Inactive colony'''
Line 233:		Line 233:
	\|-		\|-
	\|'''Defender''' (attacker win or draw)		\|'''Defender''' (attacker win or draw)
	\|Protected hangar ships and stationed defender fleets can be '''stunned''': cannot move / attack until recovery. Base around '''1 hour''', can scale with losses up toward '''24 hours''', reduced by hangar research / monuments. Hull returns in quarters over the stun window ('''25% → 50% → 75% → 100%'''). Full guide: [[~~Fleet Stun.wikitext\|~~Fleet Stun]].		\|Protected hangar ships and stationed defender fleets can be '''stunned''': cannot move / attack until recovery. Base around '''1 hour''', can scale with losses up toward '''24 hours''', reduced by hangar research / monuments. Hull returns in quarters over the stun window ('''25% → 50% → 75% → 100%'''). Full guide: [[Fleet Stun]].
	\|-		\|-
	\|'''Defender wins'''		\|'''Defender wins'''
Line 239:		Line 239:
	\|-		\|-
	\|'''Attacker (PvP)'''		\|'''Attacker (PvP)'''
	\|No hangar stun from the battle itself; losses go to debris / graveyard. Returning attack fleets can enter a '''PvP retaliation window''' (~'''2–24 hours''' by return tonnage) where surviving hull docks '''outside''' hangar protection and is scoutable/attackable — see [[~~Fleet Stun.wikitext\|~~Fleet Stun]].		\|No hangar stun from the battle itself; losses go to debris / graveyard. Returning attack fleets can enter a '''PvP retaliation window''' (~'''2–24 hours''' by return tonnage) where surviving hull docks '''outside''' hangar protection and is scoutable/attackable — see [[Fleet Stun]].
	\|-		\|-
	\|'''Expeditions / Nebula'''		\|'''Expeditions / Nebula'''
Line 309:		Line 309:
	== How a battle runs ==		== How a battle runs ==

	# Each side aims fire by '''[[Targeting ~~And~~ Priority~~.wikitext~~\|target priority]]''' (front screens before mid combat before rear logistics). Planetary turrets use the same ship tiers; colony ships + turrets merge into '''one''' priority pass against the attacker.		# Each side aims fire by '''[[Targeting and Priority\|target priority]]''' (front screens before mid combat before rear logistics). Planetary turrets use the same ship tiers; colony ships + turrets merge into '''one''' priority pass against the attacker.
	# Incoming fire at defenses uses '''dome-first''' soak (domes before armed turrets), with barrier/absorption reductions while domes live — see [[~~Damage And Shields.wikitext\|~~Damage and Shields]].		# Incoming fire at defenses uses '''dome-first''' soak (domes before armed turrets), with barrier/absorption reductions while domes live — see [[Damage and Shields]].
	# Weapons resolve as '''shots''' ([[~~Rapid Fire.wikitext\|~~Rapid Fire]]): RF adds expected extra shots against preferred types; '''overkill does not splash'''.		# Weapons resolve as '''shots''' ([[Rapid Fire]]): RF adds expected extra shots against preferred types; '''overkill does not splash'''.
	# Each side’s '''shield pool''' absorbs first (ships and turrets share one pool when firing at the attacker); excess damages '''hull'''.		# Each side’s '''shield pool''' absorbs first (ships and turrets share one pool when firing at the attacker); excess damages '''hull'''.
	# Destroyed ships leave combat and feed debris / graveyard splits; destroyed defenses follow repair / debris rules.		# Destroyed ships leave combat and feed debris / graveyard splits; destroyed defenses follow repair / debris rules.

Admin: Local CI auto-sync from FleetCombat.md

2026-09-13T11:14:56Z

Local CI auto-sync from FleetCombat.md

← Older revision		Revision as of 11:14, 13 September 2026
Line 309:		Line 309:
	== How a battle runs ==		== How a battle runs ==

	# ~~Ships select targets~~ by '''target priority''' (combat ~~hull~~ before logistics).		# Each side aims fire by '''[[Targeting And Priority.wikitext\|target priority]]''' (front screens before mid combat before rear logistics). Planetary turrets use the same ship tiers; colony ships + turrets merge into '''one''' priority pass against the attacker.
	# Weapons ~~fire;~~ '''~~Rapid Fire~~''' ~~may allow~~ extra shots ~~when a~~ preferred ~~target type dies~~.		# Incoming fire at defenses uses '''dome-first''' soak (domes before armed turrets), with barrier/absorption reductions while domes live — see [[Damage And Shields.wikitext\|Damage and Shields]].
	# '''~~Shields~~''' ~~absorb~~ first; excess damages '''hull'''.		# Weapons resolve as '''shots''' ([[Rapid Fire.wikitext\|Rapid Fire]]): RF adds expected extra shots against preferred types; '''overkill does not splash'''.
	# Destroyed ships leave combat and feed debris / graveyard splits.		# Each side’s '''shield pool''' absorbs first (ships and turrets share one pool when firing at the attacker); excess damages '''hull'''.
			# Destroyed ships leave combat and feed debris / graveyard splits; destroyed defenses follow repair / debris rules.
	# Fight ends when one side is gone, retreats, or the round cap is hit.		# Fight ends when one side is gone, retreats, or the round cap is hit.