Since the stray, wither skeleton and husk got new sounds, they have no subtitles.
Linked issues
is duplicated by 5
MC-103307
Polar Bear Sounds Not Showing up on subtitles
Resolved
MC-103358
Husk/Stray sounds not on subtitles
Resolved
MC-103465
The sound of the new mobs do not appear in the subtitles! MC 1.10
Resolved
MC-103636
In 1.10, Strays, Husks, Wither Skeletons, and Polar Bears do not have subtitles.
Resolved
MC-104729
Strays, Husks, Polar bears, and Wither skeletons "still" doesn't have subtitles
Resolved
Attachments
Comments 13
I was just about to make submit a report about this. I can confirm that Polar bears, Strays, Husks, and Wither Skeletons are missing their subtitles.
Like I said, mojang can fix some things through the launcher, that are related to sounds, languages, and alike.
The video you provided was from 12 Juli, and I've recently seen the launcher update some files, try again now.
So these can be updated without changing the game version?!?
...
GAAAH. Support nightmare to have two different user-facing programs with the same identify.
Confirmed fixed on an unmodded 1.10.2 install.
Mojang can update most assets from the launcher since they're downloaded by the launcher. Notably, the main exceptions to this are textures and en-US.lang, since they're inside of the version jar. That said, those subtitles were inside of en-US.lang all along, so it doesn't matter; it's the sounds index where they're stored.
What could have caused this is a missing entry in the sounds.json asset file (which is downloaded by the launcher along with the sounds themselves). But I'm not sure if that's actually what happened here.
Oddly, when trying to read the sounds for these mobs with Burger it claims that they have no sounds (and no subtitles), both now and when I ran it when 1.10 first came out. But it works in-game...
Oh, that's very weird. Turns out burger was still using the 1.9 asset index. Switching it to the 1.10 asset index leads to it downloading a sounds.json that has polar bear and wither skeleton sounds. I'm guessing that the 1.9 index had empty ones for them because the 1.9 index was used for the 1.10 snapshots.
Even still, if you're using forge, it should have loaded the appropriate index for 1.10 (though it might have been out of date at that time). If it didn't, that's a launcher bug (since it's incorrectly handling a version JSON in a way that the version JSONs were indented to be used). If you can still reproduce this bug, then something weird is happening.
Erik Broes
This impacts 1.10 release as well. I have a video demonstrating it.