discordApiGamesDetectableExclusions

Seen 6 time(s) in 4 run(s).

What it sent and what came back (the newest 3 from our runs)

Read from each run's own recording (rule 73), secrets and signed link tokens taken out. Kept in ~/.logCli/rea/clientFacts.json, so it stays after the run is pruned.

runs/inspect/20261030T222341_sourcedandsoldtothehighestbidder, step 2: snapshot: 200, 52 ms

Sent:

null

Answered:

{
  "executables": [
    "brocrashreporter.exe",
    "config.exe",
    "crashreportclient.exe",
    "crosshairx.exe",
    "dxsetup.exe",
    "eaanticheat.gameservicelauncher.exe",
    "… 19 more"
  ],
  "patterns": [
    "vcredist.*\\.exe$"
  ]
}

runs/inspect/20261028T074137_sourcedandsoldtothehighestbidder, step 1: goto /login: 200, 85 ms

Sent:

null

Answered:

{
  "executables": [
    "brocrashreporter.exe",
    "config.exe",
    "crashreportclient.exe",
    "crosshairx.exe",
    "dxsetup.exe",
    "eaanticheat.gameservicelauncher.exe",
    "… 19 more"
  ],
  "patterns": [
    "vcredist.*\\.exe$"
  ]
}

runs/inspect/20261028T065202_sourcedandsoldtothehighestbidder, step 1: goto /channels/@me/<id>: 200, 59 ms

Sent:

null

Answered:

{
  "executables": [
    "brocrashreporter.exe",
    "config.exe",
    "crashreportclient.exe",
    "crosshairx.exe",
    "dxsetup.exe",
    "eaanticheat.gameservicelauncher.exe",
    "… 19 more"
  ],
  "patterns": [
    "vcredist.*\\.exe$"
  ]
}

What it does

Lists games the desktop client should not detect; the web client loads it too.

What our machine does with it

Nothing in log-cli waits for it or reads it. It is part of what Discord's client loads around the page; a watch or a send never depends on it.

What can go wrong

The account carries on whatever it answers; a failure here changes nothing for our steps.