Top Lords Custom Events and Vanguard Marshal

Custom events keep results in the event and period where they belong. Choose the model before recording data so cumulative readings, weekly scores and separate runs are not mixed.

1. Create the event

1. Open Events → Create event.
2. For Vanguard Marshal, select Use Vanguard Marshal preset. It fills the event name, Total Damage, run-based type and MVP recording.
3. For a custom event, set Event name, Value label, Type and Display. Configure a requirement if needed.
4. Select Save event.

A comparison display supports separate named metrics. A flag display records Yes / No. A weekly event uses the selected period start; a cumulative reading stays cumulative.

2. Add a run

For Vanguard Marshal or another run-based event, add a run with its title and date. Each run represents a separate occurrence. Select the intended run before entering results or comparing it with the previous run.

Do not add two occurrences into one Total Damage result just because they happened in the same week.

3. Enter or import results

Record results manually in the event view, or use its CSV preview. For screenshots, open Import, select the event-results type, then choose Target event and Target run.

For Vanguard Marshal Total Damage, upload the rewards mail with its MVP card and the ranked list. The reader combines readable duplicate MVP rows. Screenshot import explains the shared review controls.

4. Review identities and MVP

1. Check the run and observation date.
2. Match every imported row to an existing Lord and verify its Total Damage value.
3. Check the MVP flag against the result screen. Record one MVP for the run.
4. Skip unverifiable rows and apply only resolved readings.

Missing results stay unknown; they do not prove a Lord dealt zero damage. Auto-sync does not read these event results.

5. Read the event history

Open the saved run to inspect results, requirements and MVP. Compare recorded runs when the event view offers the comparison. For events mapped to power, kills or squad history, check that both before and after readings exist before treating a delta as known.

The event tracker explains the available result models.