EVE FLEET COMMAND

FLEET OPS

Manage your live fleet through ESI APIs and design reusable wing/squad configurations.

EVE Online Fleet Ops

EVE Online fleet ops tool for the fleet commander: a live board with doctrine compliance and the waitlist, reusable wing structures, access lists, fleet tracker and reports.

The Fleet Ops tool on Capsuleers.app is the fleet manager that helps the EVE Online fleet commander run the current fleet via the `esi-fleets.read_fleet.v1` and `esi-fleets.write_fleet.v1` scopes. Sign in with EVE Online, take boss in game, and the Live fleet tab shows the wing and squad structure with every member's ship, system and role, the doctrine you are flying and who is off it, the waitlist queue and the fleet MOTD on one board.

Structures save a complete wing and squad layout and apply it to the active fleet after a preview of every change. Doctrines define the slots a fleet needs, access lists decide who can join, and the waitlist is shared through a link, with eligibility snapshotted when a pilot queues.

The fleet tracker records the fleet over time and produces a report with kills, losses and participation, opened in a drawer without leaving the tool. It is built for FCs running NPSI fleets, corp doctrines or alliance ops. Linked characters that lack a fleet scope stay visible, with a link to enable it.

One board for the live fleet

The Live fleet tab reads the fleet you are boss of and lays it out as wings and squads, with each pilot's ship and system and the ones away from the boss marked. Move or kick a pilot from the member menu, edit the MOTD, and see the fleet by ship class or by hull.

Choose the doctrine you are flying and the board counts every role against it and flags the pilots flying something else. If the boss is another of your characters, the board offers to switch to it instead of showing an empty fleet.

The waitlist feeds the squads

A shareable link people join from, without needing an account on anything beyond their EVE character. Each joiner's eligibility is evaluated when they queue rather than when you accept them, so a pilot cannot pass the check in one hull and then swap.

Requests appear in the board's side rail, and each proposes a destination squad from the pilot's hull and role. Accepting invites the pilot straight into that wing and squad. The access list decides who may queue at all: rules name a pilot, a corporation or an alliance, and the most specific one wins.

Structures you apply with a preview

Save the wing and squad layout of a doctrine once, from scratch or from the live fleet, and reuse it on every fleet that flies it. Applying it is not blind: a preview first lists the wings that will be created, where each pilot will land, the placements that will be skipped and whether the MOTD changes.

The preview follows what the server actually does, so what you read is what happens in game.

Reports and analysis across every operation

Start the tracker with a fleet type and it records, every minute, who was in fleet and in which hull; stop it and the report is saved. If the fleet disappears first, the tracker closes itself. Reports open in a side drawer, so reviewing last night's fleet does not take you away from tonight's.

The Analysis tab answers the longer question — who actually turns up — by aggregating every report of a fleet type across the months you select, with kills deduplicated at the main character.

Frequently asked questions

What permissions does the tracker need?

Read access to the fleet for the character who is fleet boss, granted through CCP's official sign-on. Only the boss can read a fleet's membership, which is a rule of the game's API rather than ours, so a tracker only works while your character holds boss.

Can fleet members see the participation data?

Members can, outsiders cannot. Visibility follows the fleet's access list where one is set, and otherwise falls back to being visible to the people who were in the fleet or who share the boss's corporation or alliance.

Do people need an account to join the waitlist?

They need to have connected an EVE character, since the eligibility check reads their hull and their assets. They do not need anything else, and the link is all you have to share.

What happens if the tracker is running when I lose boss?

The tracker closes itself after two missed reads, because the game's API no longer serves fleet membership to that character. What was recorded up to that point is kept and becomes a report.

Why does one of my characters show a lock?

It is missing one of the two fleet scopes. Choosing it shows which one, and the button opens your profile on that character with the service to enable highlighted; once it is enabled the character works like the others.