Earlier quoted context omitted.
Hello, fellow 40-45(?) year old. I feel like anyone preferring Warcraft III is in their 30s. Grew up with the Warcraft II Battle Chest and it was a vibe .
Hey, lots of us 39 year olds who played Warcraft 2!
Warcraft III Peon Voice Notifications for Claude Code
201–210 of 311 posts
Re: Warcraft III Peon Voice Notifications for Claude Code
#202Re: Warcraft III Peon Voice Notifications for Claude Code
#203Earlier quoted context omitted.
For those like me who are not into Star Trek lore deep enough to recognize the name, she voiced the Star Trek computer in basically all the series .
Thanks. I wasn’t sure what she voiced. I thought “computers sounding like they always should have” might mean GladOS from portal.
Hello "This is a triumph!"
Re: Warcraft III Peon Voice Notifications for Claude Code
#204I love this idea, but I really wish it were Warcraft II voices.
Red Alert II for me would be great. A plea to the various lab engineering teams: please create a json format or whatever that lets me configure this with voices locally. I am a happy user as of late of the Codex app by Open AI. It would be great if I could just give it some JSON somehow and it just works. I suppose skills can do this and I will try that later on. But I think this stuff matters, and it would be nice t…
Re: Warcraft III Peon Voice Notifications for Claude Code
#205I was kinda watching it unfold on X, I think this user was a couple days before https://x.com/delba_oliveira/status/2020515010985005255?s=46 and simpler/less-invasive instructions --- Also, I'd love to use these sound effects, but I am an rts player and love aoe and wc franchise, these noises just trigger me to want to play too much. --- Also, also, if you haven't seen AgentCraft, you are missing out -> https://x.com…
Re: Warcraft III Peon Voice Notifications for Claude Code
#206It was trickier than I expected, to get it working well: FFMpeg pipe streaming for low-latency playback, a three-hook injection strategy because the agent forgets instructions mid-turn, mkdir-based locks to queue concurrent voice updates from multiple sessions, and /tmp sentinel files to manage async playback state and prevent infinite loops.
[1] Pocket-TTS: https://github.com/kyutai-labs/pocket-tts
[2] Claude-code voice plugin: https://pchalasani.github.io/claude-code-tools/plugins-detai...
Re: Warcraft III Peon Voice Notifications for Claude Code
#207Re: Warcraft III Peon Voice Notifications for Claude Code
#208Reminded me of Warcraft (the first), where, if you kept clicking on the same unit they would respond in more annoyed ways. The best IMHO was the human soldier[1], which would end with "Why do you keep touching me?". First game that I knew of which had such fun details like that. [1]: https://www.youtube.com/watch?v=jaZyZZtwdzQ
I think I prefer the extra quotes from Warcraft II and Starcraft. The latter has some fun references to the Alien franchise and even a callback to Diablo (Protoss probe)
Re: Warcraft III Peon Voice Notifications for Claude Code
#209This is cool. I was tempted to try it until I saw the curl | bash pipe, then no. This workflow is getting really old. I guess that I also don't want to pollute old good memories by associating them with work/Claude
Totally agree, it's the main reason I'll never recommend Linux to anyone, because you can't expect normal people to understand these things. But it's kinda funny to me that you just said "I was going to run this code on my system, until I saw some other code in the same repo, and now I refuse to run it" :D It's all the same repo, you're willing to try part of the code, but not another part of it. Completely arbitrary…
Re: Warcraft III Peon Voice Notifications for Claude Code
#210Earlier quoted context omitted.
Yes; it could be a README, a folder with subfolders of sounds, 1 or 2 files with functions totalling less than 200 loc for unix, maybe 700 total to have windows support and some extra features. I get how they got here ; its how claude and codex approach projects, but what does the rest achieve? Your maintenance rituals shouldn't exceed your usecase at this scale.
Okay, but the install script is around 200 LOC and the peon.sh is just under 500 LOC ... So by your own numbers, it'd be expected loc size? What's exactly over engineered here? The fact he added config files to let people create their own package?