Three records · no pooled capacity
Chaos Zero Nightmare Team Save Data Tracker
Keep three character states on one screen while preserving their separate caps, counts, diagnostics, and evidence. The overview sum is explicitly non-transferable.
Compare three independent Save Data budgets
Each character keeps a separate displayed cap and final-state count. The sums are a workload overview only; unused room on one character cannot be transferred to another.
Current reference: February 4, 2026 Season 2 overhaul.
Record current in-game screens or official update context.
Valid character caps (sum only)
300
Valid character used (sum only)
0
Character A
Use a privacy-safe label.
Read the current on-screen limit.
Count retained Neutral cards.
Count retained Forbidden cards.
Count Common-grade Monster cards.
Count Rare-grade Monster cards.
Count Legendary-grade Monster cards.
Count retained Divine Epiphanies.
Count starting cards removed or transformed.
Count all retained removal records; maximum five.
Count retained Refinement or God's Hammer effects.
Count retained duplicates; maximum four.
Used
0
Remaining
100
Over cap
0
Fits
Yes
Character B
Use a privacy-safe label.
Read the current on-screen limit.
Count retained Neutral cards.
Count retained Forbidden cards.
Count Common-grade Monster cards.
Count Rare-grade Monster cards.
Count Legendary-grade Monster cards.
Count retained Divine Epiphanies.
Count starting cards removed or transformed.
Count all retained removal records; maximum five.
Count retained Refinement or God's Hammer effects.
Count retained duplicates; maximum four.
Used
0
Remaining
100
Over cap
0
Fits
Yes
Character C
Use a privacy-safe label.
Read the current on-screen limit.
Count retained Neutral cards.
Count retained Forbidden cards.
Count Common-grade Monster cards.
Count Rare-grade Monster cards.
Count Legendary-grade Monster cards.
Count retained Divine Epiphanies.
Count starting cards removed or transformed.
Count all retained removal records; maximum five.
Count retained Refinement or God's Hammer effects.
Count retained duplicates; maximum four.
Used
0
Remaining
100
Over cap
0
Fits
Yes
Why three independent ledgers
A team view is useful for checking preparation, but Save Data capacity belongs to each character record. Combining 30 unused points on one character with an over-cap state on another would create a fictional shared budget. The tracker calculates each panel first and adds totals only as an overview.
Use the same evidence standard per panel
For Character A, B, and C, record the current cap shown by the game, final card grades, Divine effects, starting-card changes, total removals, current refinement effects, and duplicate actions. A valid panel must independently fit the reference and action limits.
Do not copy a tier across runs automatically
The former tracker hardcoded tiers 1–13 and a +10 mode toggle. The current page asks for the displayed cap because Season 2 added tiers and special modes can change context. If all three states genuinely show the same cap, enter the same number three times and preserve the evidence.
Reconciliation workflow
- Check the official update list and in-game rule screen.
- Capture each character's displayed cap and final saved state.
- Enter counts independently and resolve any diagnostic.
- Copy the comparison link with privacy-safe labels.
- After a new run or patch, preserve the old record and create a new scenario.
Source boundary
The current numeric reference comes from the public Season 2 summary and Save Data guide. These are secondary references, so a contradiction with the live game should be documented and treated as a blocker, not silently normalized.
Empty team-log schema
Use timestamp_utc,version,character_label,displayed_cap,used,remaining,over_cap,source_note,shared_scenario,verified_by. Keep character labels non-identifying when the record will be public.
Frequently asked questions
Is the team cap shared?
No. Each character has an independent Save Data cap. The sum shown by the tracker is only a comparison total and cannot transfer unused room.
Why does every character have its own cap input?
Different runs or modes may display different caps. Enter the observed cap for each saved state instead of assuming all three share one tier.
Can one character's duplicate actions affect another?
No. Every retained duplicate count belongs to that character's Save Data record. Keep the three panels independent.
What should I save with the link?
Keep the rule version, current in-game evidence, character-safe labels, and the date each final state was checked.