Reading the status board like an operator
What each state on the live board means in practice and why no status ranks worse than undetected. How the board matches the Downloads badge, and how to decide whether to buy today.
Short answer
Each card on the status board is one build, with the state the team published for it and the publication date. Anything other than undetected needs attention, and no status does not mean clear; an unreadable feed shows no state instead of green.
On this page9
- What does the status board show?
- What each status means and what to do
- Why each build has its own card
- What the four summary numbers mean
- Why is a board with no bad rows a warning sign?
- What an empty result and an unreadable feed mean
- How the board matches the Downloads badge
- How to decide whether to buy today
- Common status board questions
What does the status board show?
The board is a published record: for each build the store sells, it shows the state the team published and its date, or no status if nothing has been published yet. It is not telemetry from your machine, not a measurement of your account, and not a prediction. The labels themselves are explained in the guide to reading status. A shopper reads only the word. An experienced user reads the word, the date beside it, the publisher's patch date and the number of flagged rows. Together those four show whether the record is current, and a word on its own does not.
What each status means and what to do
Every state listed is one the board can publish. There is no green default, so a build the feed said nothing usable about gets no status rather than undetected.
| State | What it means operationally | What you should do |
|---|---|---|
| Detected | The anti-cheat catches this build. Published as caught, not suspected | Do not run it. Wait for a new published state; running it anyway is your account, not the store's |
| At own risk | An explicit caution has been published for this specific build | Read the note that goes with it, then treat it as a risk you are choosing. Yesterday's result is not evidence |
| Testing | Validation is in progress and there is no verdict yet | Wait if you can. If you launch, you are part of the test and should report what you see |
| Updating | An update is in progress and the build is offline | Wait. There is nothing to launch and nothing to fix on your side |
| Maintenance | Scheduled maintenance planned by the team, not a reaction to a patch | Wait, then re-check. The board is re-read every minute so you do not need to ask |
| No status | Nothing usable was published for this build. It ranks worse than undetected in the severity order for exactly that reason | Treat it as unknown. Ask in Discord with the build name before you launch or buy |
| Undetected | No detection has been published for this build on the date shown. Not a guarantee and not a safety rating | You may proceed at your own risk, but read the date as well as the word |
The board sorts by severity in this order: detected, at own risk, testing, updating, maintenance, no status, undetected. Anything other than undetected counts as needing attention.
Why each build has its own card
Expecting one card per product is what makes people read the wrong row. A product with several builds gets one card per build, and each card shows that build's own state and date. There is no combined row for the whole product, so nothing can quietly look safer than the rows underneath it. It also means a firmware row tells you nothing about a game build. In the same way, a permanent spoofer row does not cover the temporary one, and the slotted variant does not cover the public one. Use the filters to narrow by kind, search for the build by name, and read the card whose name matches what you will launch.
What the four summary numbers mean
The panel above the grid gives the quickest overview of the whole board, but two of its four numbers are about coverage, not safety.
- Builds listed
- How many build rows exist, and across how many products
- Published clear
- How many of those rows are undetected, with the count of flagged rows beside it
- Builds with a status
- How many rows have any published state at all. The gap is the rows nobody has spoken about
- Feed read
- How recently the page polled. It is explicitly not the age of the data, and it is set in small type for that reason
Warning
Why is a board with no bad rows a warning sign?
Anti-cheat vendors ship changes constantly, so in a live catalogue some builds are always being validated or updated. A board where every row reads undetected is therefore making one of two claims. Either the team has just cleared everything, which shows up as fresh dates across the grid, or nobody has published anything for a while. The second case shows up as old dates and a flagged count of zero next to recent publisher patch dates. It is the dangerous one, because it looks like good news. A board that is willing to print detected on its own products is evidence that the record is being maintained. A permanently perfect board proves nothing.
What an empty result and an unreadable feed mean
If a search or filter returns nothing, the board says so and explains what that means. The board lists every build the store sells, so a missing game is one the store has no build for. If the feed itself cannot be read, the board deliberately shows no state for any build and says so, rather than defaulting to green. An all-clear that nobody can verify is worse than no answer. Learn to tell the two panels apart. One means the store does not sell that, and the other means nothing on the screen can be trusted right now.
Info
How the board matches the Downloads badge
The board and the Downloads badge share one set of labels. When you verify a licence key, each delivery item carries a run status from the same list, plus two values the board does not need. One is a neutral label for items where detection status does not apply at all. The other is the unknown case, which is treated as a caution rather than as fine. Anything other than undetected asks you to acknowledge it before the delivery route opens. So a disagreement between the badge and the board is worth a ticket with your order reference. The reason is not that one of them is wrong, but that they are read at different moments, and the gap is information in itself.
How to decide whether to buy today
Run these seven checks in this order. They take about two minutes and are the cheapest due diligence available in this market.
- Find the row for the exact build you intend to buy, not the product family
- Read its state and its publication date together
- Compare that date with the publisher's patch date on the same card, because a fresh patch under an old status means the row is stale
- Check the flagged count in the summary panel, because zero flagged rows plus old dates is a coverage problem, not good news
- Check the builds-with-a-status figure, because a large gap means the record is thin, whatever the visible rows say
- Check when the feed was last read, and remember that this is the poll time, not the age of the data
- If the row you need is updating, testing, detected or blank, wait, because a build you cannot run today is not a purchase to make today
Common status board questions
Does undetected mean I will not be banned?
No. It means no detection has been published for that build on the date shown, which is a report about the past, not a promise about your session. Nothing in this category is undetectable, and no honest seller will tell you otherwise.
Why is no status worse than undetected?
Because no status is an absence of information, and the board ranks it accordingly in its severity order. An unpublished row has never been assessed, so treating it as clear is guessing with your own account.
Why are bundles, hardware and game accounts missing from the board?
They have no detection state to report, so they are left off rather than shown as green. Older inventory flags, such as an in-stock value, are not detection states either and are never displayed as one.
How often does the board update?
The feed is re-read every minute and the page refreshes itself at that interval, with dates shown in UTC as published. The poll time is displayed separately from the publication dates, so the two are not confused.
The board and my Downloads badge disagree. Which do I follow?
Follow the more cautious of the two and open a ticket with your order reference. Both read the same published labels, so a persistent disagreement is something a person should look at.
Sources
No outside sources are used. It describes the store's own status board, its states, and how they line up with Downloads.
Read next
Still stuck? Open a ticket on Discord
All guides