Docs → Clan Administration → The Chest Cycles page
🗓️ The Chest Cycles page
Every control on the Crypt Cycles page explained: the table columns, the four ways to create a cycle, the row actions, and the warnings the page raises.
You are on Clan Management → Chest Cycles and you want to know what a button does before you press it. This article is the map of that page — every column, every action, every warning it can raise.
Reading the table
Cycles are listed newest first. The page's own note sums up the only structural rule: cycles cannot overlap, but they can be adjacent — and adjacent is what you want.
| Column | What it tells you |
|---|---|
| Start Date / End Date | The window, to the minute. All times on this page are UTC. |
| Mode | Legacy — one target for everybody. G-Level — a target per Guardsmen level. Might — a target per named Might bracket. This is fixed when the cycle is created and cannot be changed afterwards. |
| Min Points | The single point target, on Legacy cycles only. On the other two it shows — and the note See requirements, because there is no single number to show. |
| Chests | How many chests are filed against this cycle. |
| Cycle State | Where the clock is: Future, Active or Completed. Worked out from the dates alone. |
| Status | What you have done about it: Open or Closed. |
Creating a cycle
Add Crypt Cycle opens a form in two parts. The Dates section is labelled All times are in UTC and comes pre-filled to continue your rhythm: Start Date & Time defaults to the end of your newest cycle, and End Date & Time to the same length as that cycle. Accept both and the new cycle chains onto the old one with no gap, which is what you want in nearly every case.
Then How do you want to set up requirements? offers four routes:
| Option | What it produces |
|---|---|
| 📊 Legacy Mode | One Minimum Chest Points for everybody, plus an optional Minimum Chest Count. |
| 📋 G-Level Template | Copies your clan's saved G-level targets onto the new cycle. Greyed out until you have some. |
| 💪 Might Bracket Template | The same, from your saved Might-bracket targets. |
| 📑 Copy from Previous Cycle | Copies every requirement and override from your newest cycle, including its mode. Greyed out if that cycle is Legacy. |
The last three tell you exactly how many requirements they are about to copy before you commit, and they show a Combination Logic choice: OR — Meet points OR chests target or AND — Meet BOTH points AND chests target. It defaults to whatever your previous cycle used.
Templates and brackets are edited elsewhere, and the page links to both: Requirement Templates and Might Brackets sit in the header, and the same two links appear inside the create form. Might brackets are also editable from Clan Management → Clan Settings under 💪 Might Level Brackets.
The form refuses a range that overlaps an existing cycle, and refuses an end that is not after the start.
Requirements and overrides
On a G-Level or Might cycle the row action reads Edit Requirements while the cycle is open and View Requirements once it is closed. Inside are two blocks.
Primary Requirements — one row per G-level or per named bracket, each with Points, Chests and a Penalty toggle. Rows cannot be added or removed here; the set comes from the mode. The Penalty toggle is the useful one: it lets a group have a target that is measured but not punished.
Override Rules — extra rules that beat the primary ones. Add Override Rule, pick G-Level or Might Bracket as the type, tick as many levels or brackets as the rule should cover, and give it its own points, chests and penalty setting. A player matching any override takes that override's target instead of their primary one. Overrides are checked first, and the first match wins.
The row actions
| Action | Shown when | What it does |
|---|---|---|
| Edit Requirements / View Requirements | Not a Legacy cycle | Opens the requirements block above. Read-only once the cycle is closed. |
| ⚠️ Mismatches (n) / No Mismatches | Not Legacy, and the cycle is running | Lists members whose G-level or Might bracket has changed since their first chest in this cycle. Their target is held at the value they had then; Update All Snapshots moves everyone to their current value. |
| Edit | Cycle is open | Changes the dates, and the point and chest targets on a Legacy cycle. Warns you if the cycle already holds chests. |
| Close | Cycle is open | Ends the cycle and applies its penalties. See below. |
| Re-open | Cycle is closed | Rolls back only the automatic penalties this close created. Event penalties are left alone. |
| Recalculate Points | Cycle holds chests | Rewrites the point value of every non-penalty chest in the cycle from your current chest catalogue. Runs in the background. |
| Delete | Always | Removes the cycle. Its chests are released and reappear as unassigned. |
What Close shows you first
Close does not act immediately. It opens a full preview: the period, the mode and its logic, how many players and chests are involved, the total points, and which cycle the penalties will land in. Then one table per penalty type — Crypt Point Penalties with each player's target, achieved and shortfall, Login Penalties and No User Penalties — plus lists of players who are exempt and players who joined after the cycle ended.
Every row has a Skip tick box. Ticking it excludes that player from this close only, without changing anything about their exemption. The confirm button counts what you are about to do: Close Cycle & Apply 12 Penalties.
Warnings the page raises
Three things appear above the table when they apply, and each one is worth acting on.
- ⚠️ Cycle Date Issues Detected — your cycles do not meet cleanly. Each entry is labelled GAP or OVERLAP with the size of it. A chest collected inside a gap belongs to no cycle and counts towards nothing, which is the single most common reason a member's points look lower than their chest list. Fix it with Edit on one of the two cycles.
- 🔴 Unassigned Chests — chests with no cycle. Each row suggests the cycle its date falls in, and Bulk Auto-Assign All files every one of them in the background. The row-by-row list only appears while there are 200 unassigned chests or fewer. Above that the table is replaced by ⚠️ Too many unassigned chests to display individually and no rows are shown at all — the bulk action is then the only way through, and it is not limited.
- Automatic Cycle Creation — an explanatory note, not a problem. If a chest arrives dated past your newest cycle, the portal creates the following cycles for you, copying that cycle's length and settings, so nothing is lost. Creating cycles in advance keeps the schedule yours rather than the portal's.
The Danger Zone
At the bottom, collapsed, sits a red panel headed DANGER ZONE with two bulk actions. Both require you to type a confirmation phrase exactly before the button becomes usable.
| Action | Type to confirm | Effect |
|---|---|---|
| Recalculate All Points | RUN RECALCULATE ALL | Re-prices every chest in every cycle from your current catalogue. Slow, and it changes historic totals. |
| Delete All Cycles | RUN DELETE ALL | Deletes every cycle in the clan. All their chests become unassigned. |
Where to go next
The full procedure for running cycles — prerequisites, choosing a start time, chaining, closing, and what to do when the numbers do not add up — is in Setting up chest tracking cycles. Everything a penalty can be, where it lands and how to remove one is in Understand the penalty system. For what a member sees from their side, point them at What a crypt cycle is.
Common questions
Can I change a cycle from Legacy to G-Level after creating it?
No. The mode is set when the cycle is created and there is no control to change it afterwards — a Legacy cycle has no requirements block at all, so there is nowhere to put per-level targets.
If the cycle has not started yet, delete it and create a replacement from a template. If it is already running, leave it and set the next one up correctly: create your targets under Requirement Templates first, then choose 📋 G-Level Template when you add the cycle.
What does Re-open actually undo?
Only the automatic penalties that this cycle's close created — the crypt-point, login and no-user penalties you saw in the close preview. Event penalties are deliberately left alone, because they belong to an event rather than to the cycle.
Those penalties live in the following cycle, so re-opening changes that cycle's figures too. Both are recalculated in the background afterwards, so give the dashboards a moment to catch up.
I deleted a cycle. Did I lose the chests?
No. Deleting a cycle releases its chests rather than deleting them — they reappear immediately in the 🔴 Unassigned Chests panel on this page, with the cycle their date falls in suggested beside each one.
Create a replacement cycle covering the same window, then use Bulk Auto-Assign All to file them all back in one go.
What are snapshot mismatches, and should I update them?
A member's target is fixed at the level or bracket they were on when they collected their first chest of the cycle. If they level up mid-cycle, the target does not follow — it stays at the value it started from, which is normally what you want, because moving the goalposts halfway through is unfair.
Update All Snapshots re-reads everyone's current level and rebuilds their figures against it. Use it when the starting value was wrong — for example the portal had not learned their G-level yet and recorded a zero — and leave it alone when somebody has genuinely levelled up during the cycle.
Related