FleetCoordinationSystem(FCS) - Revision history

Admin: Local CI auto-sync from FleetCoordinationSystem.wikitext

2026-10-12T04:15:31Z

Local CI auto-sync from FleetCoordinationSystem.wikitext

← Older revision		Revision as of 04:15, 12 October 2026
Line 100:		Line 100:

	* '''Lock''' — no new allies can join. Existing participants are unaffected. Does not change group ETA or start the battle early.		* '''Lock''' — no new allies can join. Existing participants are unaffected. Does not change group ETA or start the battle early.
	* '''Unlock''' — reopen the rally to ~~new~~ joiners (while still traveling and not yet fought).		* '''Lock slow joiners''' — allies can still join, but only if their fleet arrives by the current group ETA. A fleet that would push the ETA later is rejected. The ETA is frozen from that point, whatever the max delay setting allows.
			* '''Unlock''' — remove either lock and reopen the rally to all joiners (while still traveling and not yet fought).

	Use lock when you are happy with the current lineup and want to stop late joiners.		Use lock when you are happy with the current lineup and want to stop late joiners. Use lock slow joiners when you still want more fleets but don't want the strike delayed any further.
	----		----

Line 375:		Line 376:
	\|-		\|-
	\|Join window		\|Join window
	\|While lead is traveling and participation is not locked		\|While lead is traveling and participation is not locked (with slow joiners locked, only fleets arriving by the current ETA)
	\|-		\|-
	\|Max delay presets		\|Max delay presets
Line 416:		Line 417:
	\|While traveling & unlocked, rally not full		\|While traveling & unlocked, rally not full
	\|-		\|-
	\|Lock / unlock rally		\|Lock / lock slow joiners / unlock rally
	\|Leader		\|Leader
	\|While traveling		\|While traveling
Line 449:		Line 450:
	\|Lock rally		\|Lock rally
	\|Leader closes the rally to new participants		\|Leader closes the rally to new participants
			\|-
			\|Lock slow joiners
			\|Leader only accepts new participants that arrive by the current group ETA
	\|-		\|-
	\|Inter-alliance participation		\|Inter-alliance participation

Admin: Local CI auto-sync from FleetCoordinationSystem.wikitext

2026-10-06T10:09:59Z

Local CI auto-sync from FleetCoordinationSystem.wikitext

← Older revision		Revision as of 10:09, 6 October 2026
Line 58:		Line 58:
	\|-		\|-
	\|Rally not full		\|Rally not full
	\|Default max: '''2''' allies (server-configurable). Pirate boss rallies use higher caps — see [[Pirate Bosses]]		\|Default max: '''2''' allies (server-configurable). Pirate boss rallies use higher caps — see [[Pirate Bosses]]. Full or locked rallies show no '''Participate''' button
	\|-		\|-
	\|Boss tonnage (boss targets only)		\|Boss tonnage (boss targets only)
Line 414:		Line 414:
	\|Join rally		\|Join rally
	\|Ally (or allied alliance if allowed)		\|Ally (or allied alliance if allowed)
	\|While traveling & unlocked		\|While traveling & unlocked, rally not full
	\|-		\|-
	\|Lock / unlock rally		\|Lock / unlock rally

Admin: Local CI auto-sync from FleetCoordinationSystem.wikitext

2026-10-05T10:00:15Z

Local CI auto-sync from FleetCoordinationSystem.wikitext

← Older revision		Revision as of 10:00, 5 October 2026
Line 252:		Line 252:
	* Each participant’s ships fight together as separate attacker entries in the same battle.		* Each participant’s ships fight together as separate attacker entries in the same battle.
	* Defender ships, stationed fleets, colony defenses, and hangar protection apply as in a normal attack.		* Defender ships, stationed fleets, colony defenses, and hangar protection apply as in a normal attack.
	* [[Support Vessel\|Support Vessels]] repair across the group: ~~80% of~~ each participant's ~~vessels repair their~~ own losses first, 20% repair other participants' losses ~~first~~, ~~and idle vessels help~~ the ~~other group~~.		* [[Support Vessel\|Support Vessels]] repair across the group: each participant's own losses come first (up to 80% of their vessels, with their full repair capacity), the other 20% repair other participants with the capacity left, and nothing is wasted: no own losses means everything repairs allies, no allied losses means everything repairs the owner.
	* War fatigue on loot is calculated from the lead attacker’s protection status against the defender.		* War fatigue on loot is calculated from the lead attacker’s protection status against the defender.
	* If any participant cannot legally attack the target (e.g. protection rules), all fleets in the group are recalled and no battle is fought.		* If any participant cannot legally attack the target (e.g. protection rules), all fleets in the group are recalled and no battle is fought.

Admin: Local CI auto-sync from FleetCoordinationSystem.wikitext

2026-10-04T06:16:42Z

Local CI auto-sync from FleetCoordinationSystem.wikitext

← Older revision		Revision as of 06:16, 4 October 2026
Line 252:		Line 252:
	* Each participant’s ships fight together as separate attacker entries in the same battle.		* Each participant’s ships fight together as separate attacker entries in the same battle.
	* Defender ships, stationed fleets, colony defenses, and hangar protection apply as in a normal attack.		* Defender ships, stationed fleets, colony defenses, and hangar protection apply as in a normal attack.
			* [[Support Vessel\|Support Vessels]] repair across the group: 80% of each participant's vessels repair their own losses first, 20% repair other participants' losses first, and idle vessels help the other group.
	* War fatigue on loot is calculated from the lead attacker’s protection status against the defender.		* War fatigue on loot is calculated from the lead attacker’s protection status against the defender.
	* If any participant cannot legally attack the target (e.g. protection rules), all fleets in the group are recalled and no battle is fought.		* If any participant cannot legally attack the target (e.g. protection rules), all fleets in the group are recalled and no battle is fought.

Admin: Local CI auto-sync from FleetCoordinationSystem.wikitext

2026-09-28T14:39:28Z

Local CI auto-sync from FleetCoordinationSystem.wikitext

@@ Line 219: / Line 219: @@
 * Group ETA is recalculated for remaining members.
 * The rally continues if the leader and other participants remain.
 ----

Admin: Local CI auto-sync from FleetCoordinationSystem.wikitext

2026-09-14T12:21:13Z

Local CI auto-sync from FleetCoordinationSystem.wikitext

@@ Line 169: / Line 169: @@
 # They are detached from the group.
-# Group ETA is recalculated from remaining members’ natural travel times.
+# Whether the group ETA is recalculated depends on '''what you are attacking''' (see below).
-# The ETA can move earlier if the slowest fleet left.
 === Battle start timing ===

Admin: Local CI auto-sync from FleetCoordinationSystem.wikitext

2026-09-13T07:12:25Z

Local CI auto-sync from FleetCoordinationSystem.wikitext

Show changes

Admin: Created page with "== Overview == Fleet Coordination System (FCS) lets an attack leader open an outgoing attack to alliance members. Allies can attach their own fleets to the same target before the group arrives. When every fleet in the group has reached the target, they fight one combined battle against the defender. In the fleet UI this appears as: * Solo attack — standard attack, no allies can join * Open to alliance — coordinated attack rally FCS is only available for attack mis..."

2026-06-10T10:50:42Z

Created page with "== Overview == Fleet Coordination System (FCS) lets an attack leader open an outgoing attack to alliance members. Allies can attach their own fleets to the same target before the group arrives. When every fleet in the group has reached the target, they fight one combined battle against the defender. In the fleet UI this appears as: * Solo attack — standard attack, no allies can join * Open to alliance — coordinated attack rally FCS is only available for attack mis..."

New page

== Overview ==
Fleet Coordination System (FCS) lets an attack leader open an outgoing attack to alliance members. Allies can attach their own fleets to the same target before the group arrives. When every fleet in the group has reached the target, they fight one combined battle against the defender.

In the fleet UI this appears as:

* Solo attack — standard attack, no allies can join
* Open to alliance — coordinated attack rally

FCS is only available for attack missions and can be participated only by alliance member or members of an ally alliance
----

== Starting a Coordinated Attack ==
When launching an attack, the leader can:

# Toggle Open to alliance to make the fleet participatable.
# Set Max delay if allies join late (see ETA & Delay Logic).

If no allies join before arrival, the attack resolves as a normal solo attack — FCS grouping only affects combat when at least one ally participates.

=== Defender notification ===
The target is notified when the leader launches, using the leader’s original ETA. Ally fleets joining later do not send additional incoming-attack notifications.

Alliance members receive a rally notification when a coordinated attack is created.
----

== Joining a Rally (Participation) ==
Alliance members can join an open rally from the fleet list (FCS filter) while the lead fleet is still traveling.

=== Requirements to participate ===
{| class="wikitable"
!Requirement
!Details
|-
|FCS enabled
|Feature must be active for the joining player
|-
|Same alliance
|Active membership in the leader’s alliance
|-
|Same realm
|Same realm level as the attack leader
|-
|Attack still open
|Lead fleet must be <code>traveling</code>, mission type <code>attack</code>, participation not locked
|-
|Not the leader
|You cannot join your own rally
|-
|One fleet per player
|Only one fleet per player per rally
|-
|Rally not full
|Default max: 2 allies (server config: <code>fcs.maxParticipantSlots</code>)
|-
|ETA rules
|Your fleet must be able to join without breaking the leader’s max-delay setting
|}

=== What happens when you join ===

# Your fleet participates in the initiator attack fleet
# Alliance members are notified that someone joined.

----

== Locking Participation ==
Only the attack leader can lock the rally.

* Available while the lead fleet is still traveling.
* Once locked, no new allies can join.
* Existing participants are unaffected.
* Locking does not change the group ETA or force the battle to start early.

Use this when you are happy with the current lineup and want to stop late joiners.
----

== ETA & Delay Logic ==
FCS synchronizes every fleet in the group to a single group arrival time. All members share the same ETA shown on fleet cards.

=== Key concepts ===
{| class="wikitable"
!Term
!Meaning
|-
|Initial lead arrival
|The leader’s original ETA at launch. Stored permanently and used as the delay baseline.
|-
|Current group arrival
|The synchronized ETA for the whole group. Can move later, never earlier than the current group ETA when someone joins.
|-
|Natural travel time
|How long each fleet would take to reach the target on its own, from departure. Stored per fleet.
|}

=== When an ally joins ===
new group arrival = max(current group arrival, ally's natural arrival from now)

* A faster ally does not make the group arrive sooner.
* A slower ally pushes the group ETA later so everyone arrives together.

=== Max delay settings ===
Set by the leader at launch:
{| class="wikitable"
!Setting
!Behavior
|-
|0 min
|No delay allowed. If an ally cannot arrive by the current group ETA, join is rejected.
|-
|5 / 10 / 15 min
|Group arrival cannot be later than initial lead arrival + that many minutes.
|-
|Unlimited
|No cap on how late the rally can be pushed by slow allies.
|}

=== Examples ===
Example A — faster ally joins

* Group ETA: 12:10
* Ally would arrive at 12:05
* Result: Group stays at 12:10

Example B — slower ally joins

* Group ETA: 12:00
* Ally would arrive at 12:10
* Result: Group moves to 12:10

Example C — max delay exceeded

* Initial lead arrival: 12:00
* Max delay: 5 min (cap at 12:05)
* Ally join would push group to 12:10
* Result: Join rejected

=== When a participant recalls ===
If an ally recalls while traveling:

# They are detached from the group.
# Group ETA is recalculated from remaining members’ natural travel times.
# The ETA can move earlier if the slowest fleet left.

=== Battle start timing ===
The battle does not start when the first fleet arrives. It starts only when:

* Every fleet in the group has reached its synchronized arrival time, and
* All members are in <code>traveling</code> or <code>onMission</code> status.

Fleets that have arrived early wait until the full group is ready.
----

== Recalling Fleets ==

=== Leader recalls ===

* All participant fleets are automatically recalled (cascade recall).
* The rally is cancelled.
* Alliance is notified.

=== Participant recalls ===

* Only that player’s fleet returns.
* Group ETA is recalculated for remaining members.
* The rally continues if the leader and other participants remain.

----

== Combat Resolution ==
When the full group is ready, all attacker fleets are combined into one battle simulation.

=== Combined attack ===

* Each participant’s ships fight together as separate attacker entries in the same battle.
* Defender ships, stationed fleets, colony defenses, and hangar protection apply as in a normal attack.
* War fatigue on loot is calculated from the lead attacker’s protection status against the defender.
* If any participant cannot legally attack the target (e.g. protection rules), all fleets in the group are recalled and no battle is fought.

=== Attack protection & war fatigue ===

* Loot reduction from war fatigue uses the leader’s fatigue multiplier.
* If the defender suffers significant losses (5%+ ships/defenses or any loot taken), each participant may have the attack recorded against them for war-fatigue purposes individually.

----

== Loot Distribution ==
On victory, total loot is calculated from the defender’s colony (subject to war fatigue and available resources), then split among participants.

=== Contribution score ===
Each fleet earns a contribution weight:

contribution = fleet power sent + damage done + cargo capacity

Where:
{| class="wikitable"
!Factor
!How it’s calculated
|-
|Fleet power sent
|Sum of <code>(attack + defense) × ship count</code> for each ship type in that fleet
|-
|Damage done
|Share of total attacker damage, proportional to that fleet’s fleet power
|-
|Cargo capacity
|That player’s fleet cargo capacity (ships + bonuses)
|}

=== Share formula ===
your loot share % = your contribution / sum of all contributions

Each resource type is allocated with <code>floor()</code> (rounded down). Small remainders may be left unassigned due to rounding.

=== Practical implications ===

* Bigger, stronger fleets earn more loot.
* Fleets that deal more damage earn more loot.
* Fleets with more cargo capacity earn a larger share (even before cargo limits are applied on return).
* On defeat, participants keep their original cargo (no loot gained).
* If a fleet is destroyed in combat, its loot share is lost with the fleet.

----

== Ship Loss Distribution ==
Attacker ship losses from the combined battle are split back to each fleet by ship type, proportional to how many of that ship type each fleet sent.

your losses of ship X = round(total losses of X × your count of X / total count of X)

Losses are capped so a fleet cannot lose more ships than it sent.

Each participant receives:

* Their own battle report
* Their own return fleet with remaining ships and their loot share
* A push notification for victory or defeat

The defender sees one combined battle report with all attacker fleets merged.
----

== Debris & Moons ==

* Debris is generated from the combined battle as a single field (attributed to the lead fleet for harvest purposes).
* Moon creation checks run on the defender’s planet as in a normal attack.

----

== Limitations Summary ==
{| class="wikitable"
!Topic
!Limit
|-
|Mission types
|Attack only
|-
|Allies per rally
|Default 2 (server-configurable)
|-
|Fleets per player per rally
|1
|-
|Who can join
|Same alliance, same realm, not the leader
|-
|Join window
|While lead is traveling and participation is not locked
|-
|ETA
|Synchronized across group; joining can delay, never hasten
|-
|Solo open rally
|If nobody joins, behaves like a normal solo attack
|-
|Notifications
|Defender notified once (on leader launch)
|-
|Pirate targets
|Supported; FCS battle flow applies
|}
----

== Quick Reference: Player Actions ==
{| class="wikitable"
!Action
!Who
!When
|-
|Open rally
|Leader
|At attack launch
|-
|Set max delay
|Leader
|At attack launch
|-
|Join rally
|Ally
|While traveling & unlocked
|-
|Lock rally
|Leader
|While traveling
|-
|Recall (cascade)
|Leader
|Recalls everyone
|-
|Recall (solo)
|Participant
|Leaves rally, others continue
|}
----

== Glossary ==
{| class="wikitable"
!Term
!Definition
|-
|Lead fleet
|The initiator’s attack fleet (<code>isParticipatable = true</code>)
|-
|Participant fleet
|An ally fleet linked via <code>parentFleetId</code>
|-
|Group arrival time
|Shared ETA for the entire coordinated attack
|-
|Rally
|A coordinated attack with the alliance join option enabled
|-
|Lock rally
|Leader closes the rally to new participants
|}