Battle Reports are now underway
KillSync now has the first version of a Battle Report Creator. You can start a report from a pasted killmail URL, killmail ID, system, or time window. The creator normalises pasted URLs, cleans up the inputs, finds candidate kills, and builds a preview of the fight cluster before saving.
Once saved, Battle Reports have public pages with:
- Total kills and total ISK destroyed
- Pilots, corps, and alliances seen on grid
- Side candidates and fight signals
- Peak ISK minute and largest loss
- Timeline preview
- Top hull losses and hulls seen on grid
- Full killmail feed with links into character, corp, alliance, ship, market, fitting, and killmail pages
That last part is the long-term goal: not just what happened, but who was involved, what they brought, where it happened, and what the rest of KillSync can tell you about it.
Combat Hotspots
While testing Battle Reports, an obvious workflow gap appeared: finding a good seed killmail for a report meant scanning recent killmails manually. So KillSync now has a Combat Hotspots page.
The page lists active systems across four time windows — 1 hour, 3 hours, 6 hours, and 24 hours — in two modes: Hot Systems and Battle Candidates.
Each hotspot shows:
- Kill count and ISK destroyed
- Largest kill, pilots seen, corps and alliances seen
- Top hulls and latest kill
- Hotspot and battle score
Each entry includes actions to create a Battle Report directly, seed from a killmail, view the map, view filtered killmails, or open system presence and intel pages.
This creates a cleaner end-to-end flow: Hotspots → Battle Report Creator → Saved Battle Report → System / Corp / Alliance / Market / Fit Intel.
Roadmap updated
A new Battle Reports & Fight Replay section has been added to the roadmap, covering:
- Battle Report Creator
- Automatic fight clustering
- Timeline fight playback
- Fleet composition breakdown
- ISK and kill momentum charts
- Shareable BR pages and embeds
- Connected fight intel
Several of those are already marked partial now that the creator, saved pages, timeline preview, fleet and hull summaries, and connected intel links are in place.
Polish and fixes
- Pasted killmail URLs now normalise cleanly regardless of format
- Player-facing dev copy removed from Battle Report pages
- Battle Report helper files no longer auto-create tables — schema is provided separately for manual DB setup
- Battle Report page spacing tightened
- Hotspots page spacing and KPI card layout adjusted
- Hotspots has a planned home under Intel → Killmails in the header menu
Why this matters
KillSync is not trying to be a battle report site. The goal is bigger: battle reports become one entry point into the wider KillSync intelligence system.
A fight should lead naturally into system activity, region context, involved corps and alliances, relationship intel, recent joins and departures, ship and doctrine patterns, fitting pages, market depth, SRP workflows, Discord and forum sharing, and eventually campaign tracking.
Battle Reports are the start of a new layer — not a separate tool bolted onto the side.
What comes next
The next major milestone is side detection and editable side assignment — letting reports separate entities into Side A, Side B, and third parties. Once that is in place, KillSync can build proper side-vs-side stats, ISK efficiency breakdowns, fleet composition comparisons, timeline momentum, and cleaner Discord and forum summaries.
Today's work gives KillSync the foundation: find the fight, seed the report, save the report, connect it into the rest of the platform.
As always, feedback via the Feedback tab on any page, or evemail me in game, or the discord.
— The KillSync Team