Fortnite Chest Tracker: Count Saved Matches with Clear Limits

Understand Burnaviour’s replay-based Fortnite chest tracker, missing-history limits, manual alternatives and a practical way to validate your own count.

What a chest tracker can establish

Abstract outlined cubes on a warm geometric background

Replay-based tracking

Burnaviour’s README describes reading finished Fortnite replays. A completed-match count and a live in-match counter are different expectations; allow the replay to finish before comparing results.

Flowing line illustration suggesting movement and rhythm

Coverage starts with available evidence

Old replay files may be missing. An initial scan is a count of accessible history, not proof of every chest ever opened on the account or on another platform.

Black starburst illustration on a pale peach background

Independent from Epic progress

Keep a personal tally separate from a quest stage or reward prediction. Matching numbers in one session do not establish that the tracker is an Epic service or an authoritative lifetime record.

Three useful tracking situations

Colorful printed posters arranged as a creative mood board

Validate a single match

Original example: manually note nine openings and compare the parser’s result afterward. If it reports eight, investigate the unmatched event before publishing a precise total.

Illustrated scene of two people sitting together

Start a new season ledger

Choose a clear tracking start date and record gaps. A complete two-week record is more interpretable than an impressive number containing an undocumented starting balance.

Scrapbook collage of friends photographed together

Make an honest stream caption

Use a label such as “tracked completed matches since my start date.” If you show a counter over footage, explain when it updates and what period its number covers.

Build a count you can explain

Creator planning a project on a laptop

Read the original documentation

Check the repository’s platform and replay requirements. Its descriptions of local processing and non-injection are the author’s claims; this page has not performed a security audit or compatibility test.

Person wearing headphones while working at a laptop

Compare one known recording

Finish a match, retain its replay and write your own opening tally. Compare the same match in the tracker, documenting any difference instead of modifying a total to make the numbers agree.

Person holding a tablet displaying illustrated music artwork

Maintain scope and gaps

Save dates and notes for missing sessions. Revisit documentation when Fortnite changes, and use Epic sources for reward terms rather than treating software estimates as guaranteed outcomes.

Frequently Asked Questions

What complete prompt or practical brief can I copy?

Chest-tracking brief. Define the metric as chests personally opened in recorded completed matches, and choose a start date. Record your platform and whether local replay files are available. Burnaviour documents its tracker for 64-bit Windows 10 or 11 and says it reads completed local replays. Before using any executable, inspect its original repository and release information; this guide has not audited or run it. Begin with one complete match whose chest openings you record manually. Compare that match after its replay becomes readable. Keep a small ledger with match date, manual tally, parsed tally, difference and explanation. Mark earlier missing history as unknown instead of entering a guessed lifetime total. Keep Epic quest progress in a separate column. Recheck Epic announcements before interpreting reward estimates. If you share a demonstration, label the period covered and hide personal file paths. Optional editing can make your owned match footage easier to follow, but cannot repair missing replay evidence.

What checklist should I use before tracking Fortnite chests?

Copy this setup checklist: define “chest opened” and the start date; record platform, local replay availability and the exact tracker release you are considering; read the author’s repository and release notes; retain one completed match for comparison. During that match, make a manual list of chest openings without assuming another player’s action belongs in your total. Compare the list with the parsed result only after the replay is finished. Log the match date, both counts, any difference and a short explanation. Mark missing earlier sessions as unknown. Keep quest progress separate from your personal count and keep reward odds separate from both. Before sharing, remove identifying file paths and label the reporting period. If you want a short demonstration, optional CapCut editing can combine your owned footage and explanatory captions after the count is checked.

Which Fortnite chest tracker is documented, and does it work on console?

The original Burnaviour Chest Tracker repository describes a Windows 10 or 11, 64-bit application that reads completed local replay files. The author says console and cloud players lack the required PC replay access. This identifies the documented scope, not a personal test or endorsement of a download. A console player can still keep a manual session tally, with a start date and gaps recorded. Do not assume a similarly named website or executable is the same project. Check the repository identity and current release notes before deciding whether its requirements suit your setup.

Why is my count low, zero or different from my quest progress?

Start with coverage: did the relevant session create a usable replay, did the match finish, and is that replay in the folder being read? The tool’s documentation says an initial scan covers existing files and that older history may already be gone. A quest display can measure a different period or stage, so disagreement does not by itself diagnose a broken parser. Test one known completed match before changing a starting balance. A manual correction should have a recorded reason and source; otherwise it converts an evidence-based tally into an estimate. This guide has not inspected your files or verified a current Fortnite update’s parser compatibility.

Can opening enough chests guarantee Pirate Shop Access?

A chest total records activity; it does not prove a future random reward is due. If a tool shows cumulative odds, check the assumed per-chest rate, event window and which openings it included. An estimate can become stale when an event changes. Do not interpret a percentage as a progress bar promising a reward at a particular count. For your own record, keep an “observed reward” column separate from a “model estimate” column. If an estimate cannot be reproduced from current official terms, leave it unverified. A clear count of what happened remains useful even when no reliable prediction can be made.

Edit a chest-tracking walkthrough

Optionally turn your own checked match footage and scope labels into a short explanation.