How our status board is maintained

A status board is the easiest page on a store to fake. Paint every row green, leave it alone, and it will never contradict a sale. Ours is the page people read before risking an account on a build. So here is how it is actually maintained. This post covers what each state asserts, who moves it, and what the page does when it cannot read its own feed. It also covers what it costs to publish a row that says do not run this.

One row per build, not one per product

The board draws a card for every build we publish, not one card per catalogue product. A product offered through three providers has three rows, and they are allowed to disagree. A single merged row would hide the case where one provider's build is fine and another is not. Each row carries its own state and its own date. The filters split them by kind: external, DMA, spoofers and firmware. Those are different hardware, different money and different questions.

The seven states

The same seven states appear against each delivery item on the Downloads page, so a key and the board cannot tell you two different things.

Who moves a row

People do. Each row is a value a member of staff publishes for a specific build. The public page only ever reads. Nothing on this site infers a state from telemetry, from a heuristic, or from how long a build has been quiet. None of those things know whether a build is caught. The trade-off is stated rather than hidden. The board is exactly as current as the last time somebody looked. That is why every card prints its own date instead of a vague live badge.

Two dates, because one is not enough

Our publication date answers when we last looked. It does not answer whether the answer is still true. So each card also carries the game's own last patch date, read from the publisher. That is Steam, Riot or Epic, depending on the title. Where that signal is weaker than a plain build date, the card says so rather than implying certainty it does not have. A build marked undetected in April, sitting beside a patch that shipped in August, tells you something neither date tells you alone. It does that without a word of copy.

Why a board with no bad rows is worthless

The value of a green row is borrowed entirely from the credibility of the red ones. If a board has never shown a detection, one of two things is true. Either nothing it lists has ever been caught, which in this field is not credible. Or the board is decoration. A reader cannot tell those apart from outside. So the only useful evidence is a board that visibly moves — downwards included, and on the day it costs a sale.

That is the commitment involved. Publishing Detected against a build takes it off the shelf. It tells everyone holding a licence for it to stop. It also invites the obvious follow-up: how long was the row wrong before it changed? The alternative is worse in every direction, commercially included. A customer who was told to stop and lost nothing stays. A customer banned while a page showed green does not.

The board refreshes itself while you have it open. The figure at the top of the page is the age of the longest-standing undetected row. It is derived from that row's own date on every render, rather than typed by anyone. That is a deliberately small claim. It says one row has stood for that long. It says nothing whatsoever about the next one.