Peter Markley

I'm afraid I can't test this anymore, this should be passed to another user.

Thank you!

You just named 2 scenarios where it "works fine" for you. This is the first I've ever heard of it working for anyone. I believe it failed for me in your 1st success scenario ("without using SHA-1").

When I first reported the bug, I genuinely wondered if the feature was even implemented yet as advertised. It was very mystifying.

I don't know if this is relevant, but I did notice something weird while originally exploring this feature.

If you have a resource pack called 'resources.zip' inside a level in your singleplayer .minecraft/saves folder, and this level folder (on the file system) is called the same thing as the level folder on the server, then it will automatically load the resource pack from your singleplayer world when you connect to the server.

This happens totally regardless of the following:

1. level name inside level.dat file

2. contents of server.properties file

3. server resource pack setting in client (i.e. "Disabled," "Prompt," or "Enabled").

It's pretty much like it just thinks you're connecting to your singleplayer world, because the folder name on the system matches.

Yes.

I have updated the resource pack Dropbox URL (due to a recent change in Dropbox's service), and tested on Minecraft 1.12.2. Still no discernible acknowledgment whatsoever of 'resource-pack' lines in server.properties file.

(I'm not sure where I could get a development snapshot of the server jar file.)

I've seen a lot of people describe symptoms that I didn't see (like the client acknowledging the resource pack, and attempting to download it, but hanging or crashing; or claiming to succeed but showing default textures, etc).

I don't know if these should be considered the same bug or not. Mod input welcome.

But my symptoms are always and exclusively as though no resource pack was set by server, or as though the client was set to "disabled" when it clearly wasn't.

When Emilie says "the client is waiting for resource pack..." it sounds as though her client is already acknowledging the resource pack in a way that mine does not (in any of my testing).

That's what I meant when I said "no matter if I set the server listing to 'Prompt' or 'Enabled,'" and, "The option cited [ in MC-58387 ] is set correctly here."

I was referring to the client setting shown in the screenshots above. I've tried it both ways on both clients; in all my testing I made sure it was never set to "Disabled."