No sound in older versions on native launcher, despite working in the Java launcher

The old launcher no longer restores sound now to the Alpha versions (This was generated from using the older launcher for c0.30_01c), haven't tried Betas yet.

Mar 25, 2018 2:58:37 AM net.minecraft.launchwrapper.LogWrapper log
INFO: Using tweak class name net.minecraft.launchwrapper.AlphaVanillaTweaker
Mar 25, 2018 2:58:37 AM net.minecraft.launchwrapper.LogWrapper log
INFO: Launching wrapped minecraft
AlphaVanillaTweakInjector.class.getClassLoader() = sun.misc.Launcher$AppClassLoader@1909752
Found likely Minecraft candidate: private com.mojang.minecraft.l com.mojang.minecraft.MinecraftApplet.minecraft
Client asked for parameter: fullscreen
Client asked for parameter: mppass
Client asked for parameter: haspaid
Client asked for parameter: loadmap_user
Client asked for parameter: server
Loading current icons for window from: C:\Users\Aaron\AppData\Roaming\.minecraft\assets\virtual\legacy\icons\icon_16x16.png and C:\Users\Aaron\AppData\Roaming\.minecraft\assets\virtual\legacy\icons\icon_32x32.png
Mar 25, 2018 2:58:38 AM net.java.games.input.DefaultControllerEnvironment getControllers
WARNING: Found unknown Windows version: Windows 10
Mar 25, 2018 2:58:38 AM net.java.games.input.DefaultControllerEnvironment getControllers
INFO: Attempting to use default windows plug-in.
Mar 25, 2018 2:58:38 AM net.java.games.input.DefaultControllerEnvironment getControllers
INFO: Loading: net.java.games.input.DirectAndRawInputEnvironmentPlugin
java.lang.ArrayIndexOutOfBoundsException: 1
	at com.mojang.minecraft.c.run(Unknown Source)
java.lang.ArrayIndexOutOfBoundsException: 1
	at com.mojang.minecraft.c.run(Unknown Source)
java.lang.ArrayIndexOutOfBoundsException: 1
	at com.mojang.minecraft.c.run(Unknown Source)
java.lang.ArrayIndexOutOfBoundsException: 1
	at com.mojang.minecraft.c.run(Unknown Source)
java.lang.ArrayIndexOutOfBoundsException: 1
	at com.mojang.minecraft.c.run(Unknown Source)
java.lang.ArrayIndexOutOfBoundsException: 1
	at com.mojang.minecraft.c.run(Unknown Source)
java.lang.ArrayIndexOutOfBoundsException: 1
	at com.mojang.minecraft.c.run(Unknown Source)

I have been experiencing the same issue on version 1.2.5 with Java 8. From the looks of it, it looks like the S3 server the resources are saved to have been made forbidden for accessing by the general public, as the log kicks out a bunch of 403 errors. If the launcher is supposed to be having all older versions use the legacy assets, it doesn't seem to be doing that either as there is no sound in-game, even after waiting for all 403s to subside.

This is just one IOException kicked out by the game. All errors are exactly the same, just with t
the file name changed.

java.io.IOException: Server returned HTTP response code: 403 for URL: http://s3.amazonaws.com/MinecraftResources/streaming/cat.mus
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
	at java.net.URL.openStream(Unknown Source)
	at ck.a(SourceFile:104)
	at ck.a(SourceFile:93)
	at ck.run(SourceFile:42)

+1 to Parker's issue. I can no longer get sound on legacy versions. It looks like they might have set the S3 bucket permissions to private, or something.

That issue is probably WEB-1004 actually. What's weird is that the index works (and lists everything), so it seems like it's not intentionally decommissioned.

That is funny that the index works. You're right, this does look more like that other issue.

I don't have sound for 1.2.5

This thing happens to me too on 1.2.5. I think that fix will be to find those assets and rename them to filenames(that weird name > hurt1.ogg for example) and put them into resources folder. Or even downloading whole resources folder from somewhere.

That doesn't work well, I tried. The problem is actually the server hosted by amazon that now denies access to the files. Please mojang, fix it there.

So, I see this as two issues:

1. The new launcher is not creating the virtual assets folder - this affects some 'newer' versions like 1.6.2. This should be fixed in the next version of the launcher.

2. No asset indexes or assets exist for very old versions at all. Basically, with the disappearance of the s3 bucket in WEB-1004, those versions have nothing to pull sounds from, and the launcher doesn't have anything correct to give them either. This will be fixed in the future, likely both in metadata (it doesn't exist and the sound files need to be pulled from old archived versions and the s3 bucket) and the launcher (to make it behave as the old versions did, and not destroy/affect modded resources).

Issue 1 should be now partially fixed in intdev.

I don't think that you can redirect Minecraft to look for new resources, without actually modifying the game's code. From my understanding the resource URL http://s3.amazonaws.com/MinecraftResources/ is hardcoded into the game's class files (at least in older versions). I would like game's code to remain intact, so that it is the same as it was when it was released, so that it can be seen as a museum of old versions. To alter that game's code would put a blemish on the originalness of these old versions. It would be like an artist trying to fix a famous painting by painting details into it that they thought the original artist should have put in. That would destroy the originalness of the artwork. And yes, Minecraft is artwork. I believe the best fix is to simply reactivate all the files pointed to by the URLs in the resource index http://s3.amazonaws.com/MinecraftResources/

They already modify the game slightly through LaunchWrapper, which is needed for the games to even launch. Though in comparison to your analogy, it's more like changing the frame on a painting than anything else... which in this case should be enough. Though reactivating the bucket in the meantime seems reasonable.

Interesting that the LaunchWrapper could supposedly fix this. I thought that the URL for downloading resources for the game was hardcoded in the Java class files in the game. This means that the game itself makes a direct connection to minecraft.net rather than telling the launcher to make this connection.

As far as I know, there's no way for the launchwrapper (or any other Java application) to be able to intercept such a direct connection and redirect it to any other location.

Some of you can tell me how I can use the launcher wrapper to run old versions of minecraft.

I try to run 1.5.2 Minecraft version with the old java launcher and there is no sound at all in the game, no music, no sound, nothing.

I'm using the Arch-based latest Manjaro Linux.

So now even the old launcher can't download the files. In the log all are get a HTTP 403 error.

So it seems the servers won't let them download, or something like that, because the 403 error.

Yep Gofri. That is correct. It doesn't work at all. No launcher works now with the sound. The reason is the game itself looks in .minecraft\resources, while the actual resources get downloaded to .minecraft\assets\virtual\legacy which is not where the game is looking for them. Also the folder structure that the game is expecting is slightly different than the one provided in the virtual\legacy folder. Also some of the sound files have been renamed (new versions of some files using an underscore, while the old versions of the same files used a space, in their filename). I only wish that whoever is in charge of running the Minecraft resources server took more interest in fixing this.

Solution:

1. Create a new folder called "resources" in the ".minecraft" folder (If it doesn't exist)

2. Copy ALL of the folders from "assets" into "resources".

3. Open Minecraft

4. The sounds work, but there might be no BGM. (It might play.  I only played that version for about 2 minutes.)

Thanks Karen, your solution has worked so far for me in 1.5.2 which had no sound and so far (about 2 minutes) has sound.

It's a workaround - not a solution, they should fix it.

who tagged this as resolved? because it's not, this bug is still affecting from 1.5.2 backwards, i ran, 1.6.1 and 1.5.1 and both 1.5.2 and 1.5.1 shows this error message.

@unknown What version of the launcher are you using?