Docs → Chest Tracking → Missing chests

Your clan earned chests, but the portal never counted them. Somebody is short on their cycle score through no fault of their own, the totals look too low, and nothing on the scanning side reports an error.

There is one cause, and this article is about it: somebody collected the chests from inside the game before the portal could read them. Once a chest has been collected it is gone from the game's list, and no amount of scanning brings it back.

How a chest gets counted

Chests are earned by playing. Clearing a crypt, killing a monster, and the other activities that reward the clan all put a gift in your clan's gift list inside Total Battle. The game does not hand any of it to the portal.

Your Chest Grabber — the game account your clan set aside for counting — opens that list on a schedule and reads what is in it. Whatever it finds is sent to the portal, scored against your chest catalog, and appears on the dashboards.

The important part is what the list is: a queue that empties. A gift sits there until it is claimed, and claiming is what takes it out. A chest can only be counted while it is still in the list.

How the portal knows chests are missing

The game numbers the gifts it hands out, one after another, with no numbers skipped. That numbering is what makes this measurable at all.

Suppose the portal receives gifts numbered 100 to 150, and then the next scan brings back 180 onwards. The twenty-nine in between were issued — the game counted them — but they never arrived. The only way that happens is that somebody collected them before the Chest Grabber got there.

Who collected them

It can only be somebody signed in as the Chest Grabber account, claiming from the clan gift list while they are in there. In practice it is one of two things:

• Somebody is playing on that account, or logging into it. Perhaps a clan admin uses it as a second account, perhaps it is being checked in on. Whoever opens the gift list while signed in as the Chest Grabber claims what is sitting there.
• A previous chest counter still has access. Someone who used to run the tracking, has since stepped back, and can still sign in.

They cannot be recovered

This is the part people ask about first, so it is worth being blunt: there is nothing to recover.

The chests were gone from the game's list before we ever read it. Their contents were never available to the portal at any point — not stored somewhere and lost, but never received in the first place. There is no backup to restore from, no rescan that reaches back, and no way to reconstruct what those chests contained.

Only chests collected from this point on can be counted. That is why the useful response is to stop the cause rather than to look for the data.

Pauses and scanning errors do not lose chests

You may see two extra lines under the finding, one for chests missing while your Chest Grabber was paused and one for chests missing during a scanning error on our side. Neither of those is a cause.

A pause does not lose chests, and neither does an error of ours. The gifts stay in the clan's list until somebody collects them, so a pause or an error only tells you when we were not reading — not why anything disappeared. Chests missing from those periods were still collected by somebody. The two lines are shown separately so the numbers add up, and neither of them raises the warning.

Where you see this

If neither is there, nothing has gone missing in the last seven days that we can attribute to this.

How to tell it has stopped

Inside the box there is a green line: Nothing has gone missing for the last …. It counts back from now to the end of the most recent gap.

That line is the one to watch. The seven-day window still contains gaps from earlier in the week, so the red box does not disappear the moment you fix the cause — but the green line starts growing from the moment you do, and it is the honest answer to "did what I changed work?". Once the last gap falls out of the seven-day window, the box goes away on its own.

The line only counts periods in which the Chest Grabber was actually scanning. If scanning stops, the run stops with it — a grabber that is not reading cannot honestly report that nothing has gone missing.

What the seven days actually cover

The window only counts time we have genuinely measured. A clan that started scanning three days ago has three days of measurement, not seven, and the box says Measured since with that date so the number is not read as covering more than it does.

Grabber accounts less than a day old are left out altogether. A first scan reads whatever happens to be sitting in the gift list at that moment, and that list is a backlog stretching back before the account existed — most of it long since collected. Reporting that as missing chests would be blaming a clan for something that happened before it started tracking.

Common questions