> For the complete documentation index, see [llms.txt](https://swu-forge.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://swu-forge.gitbook.io/docs/teams/team-battle-log/team-stats-periods.md).

# Team Stats Periods (Metas)

A **stats period** — a "meta" — lets a team reset its statistics at the start of a new competitive era, typically when a new set drops and the metagame shifts. It's a **non-destructive reset**: no games, replays, or decks are ever deleted. A period simply marks the date from which the team's aggregate stats start counting.

## The idea

Every team-stats surface — the dashboard, [Team Battle Log](/docs/teams/team-battle-log.md), [Activity](/docs/teams/team-battle-log/team-activity.md), [Matchups](/docs/teams/team-battle-log/team-matchups.md), Pilots, Teammate matchups, **and a team deck's own battle log** — is filtered to the **selected period's window**. A period runs from its start date up to the start of the next period; the most recent period runs to "now." An **All time** option is always available and applies no filter.

So "starting a new meta on May 1" means: from then on, the team's default stats reflect only games played on or after May 1. The older games are still there — they're just attributed to the previous meta, which you can switch back to at any time.

## Switching periods

Every team page has a **Stats period** selector in the left rail (it appears once a team has defined at least one period). Pick a meta to scope all the stats to it, or pick **All time** to see the team's complete history. The selection rides in the page URL (`?period=…`), so it's shareable and survives navigation between team pages. With no selection, pages default to the **current** (latest) meta.

Any member can switch periods and browse past ones — it's a read-only view control.

## Managing periods (admins)

Owners and admins manage periods under **Settings → Stats periods (metas)**:

* **Start a new meta** — give it a name (e.g. "Set 5 Meta") and a start date. The date picker defaults to now, but you can **backdate** it to a set's actual release day. Creating one is the "reset."
* **Edit** — rename a meta or move its start date.
* **Delete** — removes that cutpoint. The adjacent periods simply re-merge; the underlying games are untouched.

Two periods can't share the exact same start time.

## What counts in a period

The same team-scope and **mirror-exclusion** rules as the rest of the team feature (see [Recording Scope](/docs/battle-log/battle-log/recording-scope.md)) — narrowed to the period's date window. A best-of-three that straddles a cutoff only counts the games actually played inside the window.

The win/loss-over-time chart's date ranges (7d / 30d / 90d / all) stay coherent inside a meta: for a past period they read against the period's own span rather than against today.

## Team decks vs personal decks

A **team deck** (one that lives in a team folder) is team data, so its own battle log on the deck page honors the active meta too — it gets the same **Stats period** dropdown (defaulting to the current meta, switchable to All time or a past meta). Reset the meta and a team deck's battle log starts fresh alongside the rest of the team's stats.

A **personal deck** is never touched by any team period — its battle log always shows your full, all-time history.

Game recording is unaffected either way: new games keep landing normally and fall into whichever period their played-at date belongs to. And nothing is ever deleted — switching to **All time** brings every game back instantly.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://swu-forge.gitbook.io/docs/teams/team-battle-log/team-stats-periods.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.