Executor metadata & analytics
Read client-reported executor labels without confusing them with verified users.
Detection and limits#
The client attempts identifyexecutor, with getexecutorname as a protected fallback, once per script run. Unsupported, empty or invalid results stay Unknown. It does not infer names from branding, scan processes or collect an HWID.
Reported names are bounded to 64 printable characters and versions to 32. This metadata can be spoofed by the caller. It is diagnostic information, not authentication or a rule for selecting transports.
Transmission#
executorName/executorVersion accompany the existing presence payloads over WebSocket or HTTPS. Linked telemetry can report executor.name/executor.version. This adds fields rather than introducing new request loops.
Owner distribution chart#
The updated admin chart groups recorded launches in the selected period. Unknown or missing executor labels are excluded from the chart and percentage denominator. Tables can still explicitly show Unknown when no name was reported.
The legend includes every identified group in that period and scrolls when it exceeds the visible area. The newer chart replaces the earlier top-ten presentation in the original document. Selecting All means retained history, not an unlimited archive.
Privacy boundary#
These aggregate executor details are owner-authorized analytics. They are not exposed as a public user directory or as executor details in bot presence counts.