Per-system time windows
Each system carries its own from/to UTC window so a global range can't import cross-fight noise like NPC kills or unrelated ganks.
Tool guide · Capsuleers.app
Battle Report
Multi-team tactical report for alliances and corporations
The battle report aggregates killmails for a fight by entity (alliances + corps) instead of by individual pilot. Start from the list of teams involved, the systems where the fight happened, and a UTC time window up to a month wide; the tool returns a tactical report with multiple teams, side-attributed killmails and Involved / Summary / Timeline / Damage / Composition tabs.
Preview
Schematic mockup — the real tool is interactive
How it works
1
Add systems
Add each system as a card with its own UTC window
2
Build teams
Assign alliances and corps to colored team cards
3
Auto-detect
Or let co-attack and opposition matrices infer sides
4
Compute & view
Generate a saved read-only report with five tabs
Features in detail
Team builder
Colored team cards (8-color palette) hold any mix of alliances and corporations, added via eve-kill entity autocomplete search.
Auto-detect teams
Co-attack and opposition matrices seed sides from the highest co-attack pair and expand greedily, leaving unassigned entities for you to place.
Five-tab read-only view
The saved report opens with Involved, Summary, Timeline, Damage and Composition tabs, always recomputed from the input config, never client data.
Damage to structures
Per-team damage against deployables, starbases and Upwell structures is tracked, and pilot-less losses are heuristically attributed to the closest in-corp loss.
Refresh and fork
A throttled refresh re-runs the compute against the saved filters, and a fork button reopens the form pre-filled to spin off a variant report.
Key benefits
1
Multi-team support (N teams)
Configure as many teams as you need: two for the classic case, three or more for multi-side brawls. Every team carries a color + name + list of alliances and/or corps. Pilots that don't fall into any team land in a separate "Involved" pool.
2
Team auto-detect
The algorithm reads co-attack and opposition patterns across the killmail set to suggest teams. You can always refine the suggestion manually by moving entities between teams or spinning up new ones.
3
Mandatory system filter
At least one system must be selected. This keeps the dataset bounded even on long windows and produces reports focused on a single geographic engagement (system + adjacent).
4
Share + Fork
Every report has a unique URL. The Fork button opens the form pre-filled with the report's current teams + systems + window: editing the config yields a new URL (the config is immutable per share). Refresh updates ONLY the data on the same URL.
Frequently asked questions
How is this different from the Fleet Report?
The fleet report starts from a pilot list (typically a fleet's roster). The battle report starts from the entities (alliances + corps) and the systems of the fight. The battle report fits the post-mortem of strategic fights (sov, alliance wars); the fleet report fits the operational post-mortem of a specific fleet.
Can I edit a saved report?
No, reports are config-immutable. You can however use Fork to spin up a new report pre-filled with the same config, edit it and save it to a fresh URL. Refresh instead updates the data on the same URL (useful when eve-kill ingests late killmails).
Is there a cap on entities per team or on the number of teams?
No cap. Performance starts degrading with hundreds of total alliances + corps, but even a fight with 200+ entities stays manageable. Refresh is throttled to 1 per 5 minutes per report to avoid hammering eve-kill.