add mod-list snapshot telemetry (LAZ-701) - #23924
Merged
Merged
Conversation
Collect a per-game mod-list snapshot on the client and POST it to the Nexus v3 ingest endpoint, authenticated the same way as the generated v3 client (OAuth bearer, else api key). The payload carries user_id, the app instance id, numeric game_id, vortex_version, and one entry per installed mod (source, mod_id, file_id, version, enabled) across all sources - mod_id and file_id are null for non-Nexus mods. Gated on analytics consent and login. Emitted on game launch (StarterInfo) and after a deploy (mod_management). The v3 ingest path is provisional; the backend endpoint is still pending. Once that's done, we need to update the V3 client. part of LAZ-701
Emit a per-game mod-list snapshot to the internal v3 telemetry ingest endpoint (POST /v3/telemetry/mod-lists) on game launch and on deploy, gated on analytics consent and being logged in. The snapshot is a flat payload: instance_id, game_id, captured_at, vortex_version, and one entry per installed mod (source, mod_id, file_id, version, enabled). mod_id/file_id are Nexus UIDs, null for non-Nexus mods. The server reads the account id from the auth token, so no user_id is sent. Request types are generated from a vendored internal OpenAPI fragment (nexus-api-v3/schema/internal/telemetry.yaml) via a second codegen output, so the payload is checked against the endpoint schema at build time. A typed internal v3 client (createNexusV3InternalClient / submitModLists) carries the request and shares auth and transport with the public client. closes LAZ-701
erri120
reviewed
Aug 11, 2026
Member
There was a problem hiding this comment.
This isn't exposed on the normal openapi.yaml file?
Contributor
Author
There was a problem hiding this comment.
Nope, backend decided to keep it internal and share the spec fragment. More info here if interested.
insomnious
approved these changes
Aug 12, 2026
insomnious
left a comment
insomnious
left a comment
Contributor
There was a problem hiding this comment.
Checked end to end, my mod lists are showing up in Clickhouse
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Emit a per-game mod-list snapshot to the internal v3 telemetry ingest endpoint (POST /v3/telemetry/mod-lists) on game launch and on deploy, gated on analytics consent and being logged in.
The snapshot is a flat payload: instance_id, game_id, captured_at, vortex_version, and one entry per installed mod (source, mod_id, file_id, version, enabled). mod_id/file_id are Nexus UIDs, null for non-Nexus mods. The server reads the account id from the auth token, so no user_id is sent.
Request types are generated from a vendored internal OpenAPI fragment (nexus-api-v3/schema/internal/telemetry.yaml) via a second codegen output, so the payload is checked against the endpoint schema at build time. A typed internal v3 client (createNexusV3InternalClient / submitModLists) carries the request and shares auth and transport with the public client.
closes LAZ-701