Custom intersections

Most of the power is here. Common slices (one keep, team ranged rallies, one player’s series) get asked a lot because lots of people want them. The night you actually fought is usually an intersection that will never have a button.

If you can say the pile in comms, try it. If the Analyst cannot form it, it should say so or ask. That is still the system working.

Focus

Examples of piles that are first-class even when they do not come with denser reporting on the way in:

Combine naming a subset. Path B in the loop is this family.

Custom ask on a named focus — Analyst clarifies the pile, then runs the analysis
Say the pile in plain language. The Analyst clarifies, then works that intersection — no special button required. Click to enlarge.

Why this used to be impossible by hand

There is no folder in the mailbox named “main vs siege.” Creating it by hand is a filter pass over every report. People do not do a filter pass. They do the fights they remember.

Questions (any wording)

Once you have the custom pile — any of the step-4 shapes:

The questions are ordinary. The pile is what you could not build before.

What a good answer looks like

A post-focus summary that matches the criteria you said (count, side, names). Then the analysis you asked for. No apology that this is not an official report.

Common miss

Waiting until you find denser reporting that is “close enough,” then analyzing the wrong pile. Close enough is how you teach the team the wrong lesson.

The night you fought usually has no button — name the pile anyway.

Main vs incoming siege, late solos, joins that were already dust: those intersections never ship as a folder in the mailbox. Import the battlefield, say the cut in chat, take the post-focus summary, then ask ordinary questions on that pile — not the nearest denser default view.

Ask this on your own battlefield How to name a subset

New customers can start with a 7-day trial. Plans start at $14.99/month with full feature access.