BOTLOBBIESRead Bot Lobby Stats Correctly: Connections, Searches and Matches
A useful bot lobby statistic needs a defined event, a time period and a trustworthy source. Connections, assignments, searches and matches measure different things. Combining them can make a panel look more certain than its evidence allows. Read the label and the observation time before using a number to decide whether a bot is working or a trial produced the result you expected.
Assigned capacity is not the connected population
Capacity describes how many slots a node can accept under its configuration. Assigned executions describe work allocated to it. Neither is the same as bots currently confirmed online. A reserved or starting execution can occupy capacity before Fortnite is connected.
Check whether a connection count comes from a recent observation. If some bots have unconfirmed states, keep them separate instead of adding them to online or offline totals. A panel can accurately report that work is assigned while also stating that the live connection has not yet been confirmed. Those statements are compatible.
Do not count every search as a completed match
Pressing Ready, requesting a matchmaking ticket and entering a match are separate events. A cancelled search belongs to the search history; it does not become a completed match because the command that initiated it was accepted. A successful cosmetic or party command is not evidence of a bot lobby either.
Look for the counter's documented meaning. A match count should rely on a confirmed observation of the event it claims to count and should avoid counting the same event twice. If the available data only confirms an attempt, use that narrower description when comparing activity between bots.
Unknown and zero answer different questions
Zero says the measured event count is known and none were recorded within the stated scope. Unknown says that evidence is unavailable or insufficient. A missing counter, incomplete history or stale observation should not silently become zero.
The same distinction applies to trials and payments. Starting a checkout does not confirm a paid conversion. A reservation or pending payment must remain separate from a confirmed payment record. If the panel cannot establish the outcome, an unknown conversion state is more accurate than either a guessed purchase or a guessed failure.
- Read the time window before comparing totals.
- Keep pending, failed and confirmed events separate.
- Check for partial history or missing observations.
- Do not infer payment from a checkout being opened.
Compare observations that cover the same period
A current connection snapshot and a historical activity total answer different questions. Compare the same reporting period, and note when each source was updated. An event may be observed by the bot before the server receives it; receipt time alone does not identify the exact moment the player saw the result.
When reporting a discrepancy, name the specific counter and its period, then describe the event you believe is missing or duplicated. Remove private identifiers from any public screenshot. Support can investigate a defined mismatch more effectively than a claim that all statistics are wrong. No counter guarantees the outcome of the next search or match.