Skip to content

fix: music autoplay and robust rune usage#32

Merged
JesseRWeigel merged 1 commit intomainfrom
fix/music-autoplay-and-rune-feedback
Mar 16, 2026
Merged

fix: music autoplay and robust rune usage#32
JesseRWeigel merged 1 commit intomainfrom
fix/music-autoplay-and-rune-feedback

Conversation

@JesseRWeigel
Copy link
Owner

Summary

  • Music: Start ambient on first user interaction (click/touch/key) to work around browser autoplay policy
  • Runes: Read stat type and bonus from item.stats object instead of only parsing name strings, fixing old/non-standard runes

Test plan

  • 215 tests pass
  • Manual: music starts after first click on mobile
  • Manual: old runes with non-standard names can be used

🤖 Generated with Claude Code

Music:
- Listen for click/touch/keydown to start ambient music, working
  around browser autoplay policy that blocks audio before user
  interaction
- Keep the setTimeout fallback for browsers that allow autoplay

Runes:
- Use item.stats object for stat type/value instead of only parsing
  name strings — fixes runes from old saves or non-standard formats
- Fall back to random stat as last resort instead of silently failing

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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