-
Notifications
You must be signed in to change notification settings - Fork 0
Correct the misspelled achievement telemetry event schema #52
Copy link
Copy link
Open
Labels
P4Low: minor issue, maintenance work, or non-runtime improvementLow: minor issue, maintenance work, or non-runtime improvementarea:telemetryTelemetry, diagnostics, privacy, or error reportingTelemetry, diagnostics, privacy, or error reportingloader:commonShared Common implementation or assetsShared Common implementation or assetsstatus:backlogValid work that is not currently scheduledValid work that is not currently scheduledtype:bugA defect or incorrect behaviorA defect or incorrect behavior
Description
Metadata
Metadata
Assignees
Labels
P4Low: minor issue, maintenance work, or non-runtime improvementLow: minor issue, maintenance work, or non-runtime improvementarea:telemetryTelemetry, diagnostics, privacy, or error reportingTelemetry, diagnostics, privacy, or error reportingloader:commonShared Common implementation or assetsShared Common implementation or assetsstatus:backlogValid work that is not currently scheduledValid work that is not currently scheduledtype:bugA defect or incorrect behaviorA defect or incorrect behavior
Summary
All Minecraft loaders emit the progression event name achevement_earned instead of achievement_earned.
Evidence
Impact
Progression telemetry is stored under an unexpected event name, and a simple rename later can split historical and new data unless migration/alias behavior is deliberate.
Reproduction / verification
Proposed direction
Adopt achievement_earned as the canonical schema and document a migration, alias, or dashboard transition for historical achevement_earned data.
Acceptance criteria
Audit provenance
Candidate #31 from the read-only repository audit performed on 2026-07-20. This is separate from existing issues #3, #4, #25, and #27 unless explicitly linked later.