Skip to content

[PL-81] - Fix achievement progress updates never reaching the Twitch announcer and silently skipping an achievement's first progress tick - #70

Merged
kzryzstof merged 1 commit into
mainfrom
features/PL-81-fix-progress-announcement-not-firing
Sep 19, 2026
Merged

kzryzstof merged 1 commit into
mainfrom
features/PL-81-fix-progress-announcement-not-firing

Conversation

@kzryzstof

@kzryzstof kzryzstof commented Aug 8, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

The progress-announcement feature added for PL-81 never actually posted to Twitch chat: Xbox's in-progress achievement updates never reached the announcer's diff logic, and even once they did, an achievement's very first progress tick had no prior recorded value to compare against and was silently skipped.

Changes

  • monitoring_service.c: fire notify_achievements_changed() from the "still in progress" branch of on_xbox_achievements_progressed(), not just the unlock branch, so the Twitch announcer's diff handler actually runs on progress ticks
  • achievement_announcer.c: treat a missing prior measured_progress value the same as a changed one, so an achievement's first progress update after baseline is announced instead of silently dropped

Related


Generated by describe-pr skill v1.1.0

on_xbox_achievements_progressed() only signaled achievements-changed on the
unlock branch, so the Twitch announcer's diff handler never ran for in-progress
updates. Separately, the diff itself required a prior recorded progress value,
silently skipping an achievement's very first progress tick.
@kzryzstof kzryzstof changed the title [PL-81] Placeholder [PL-81] - Fix achievement progress updates never reaching the Twitch announcer and silently skipping an achievement's first progress tick Aug 8, 2026
@kzryzstof
kzryzstof merged commit 369478b into main Sep 19, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant