TommyMC

I faced similar errors when the launcher tried to download files from s3.amazonaws.com
and I think this URL - as an obsolete - should be completely removed from the launcher
to make potential errors more clear and not confusing.

The confusing URL is visible in [launcher-install-dir]\game\launcher.dll file, that contains paths:

https://s3.amazonaws.com/Minecraft.Download/indexes/

https://s3.amazonaws.com/Minecraft.Download/versions/

and according to wiki.vg the above URLs are no longer used:
=> see the diff of Game files page revision as of 23:20, 4 October 2019
https://wiki.vg/index.php?title=Game_files&diff=next&oldid=15017

@jnhgaming , as we can see in the crash log is that you use a custom mod loader - Fabric.

I don't think this is supported by Mojang, so this problem should be resolved by Fabric's devs or by creators of the shader pack you use: Potato_v1.0b.zip (the exception message shows a problem with this shader pack).

@SeacraftGaming From what I know, the biome generation in 1.18 has rather changed to generate "terrain shape and elevation independently from biomes", but this does not mean that a regular land (as reported in this issue) should generate in an ocean biome.
In other words, the generator changes did intended to concern just "terrain shape and elevation" (I would suppose: "ocean floor" in this case) and not an illogical mess of biomes...
As for me, the reported issue is completely accidental and unintended.

OK, I understand. Previously I thought that the datapack you attached was originally different and only then it was modified so that the game crashed.
Then, what was the last version/snapshot where this datapack was working without a crash ?

OK, the dev could decide that, but I really doubt the issues were really intended.
I'm afraid they decided so, because it was too complicated to correct such weird issues about world generation.
So, in my opinion (and not only mine) the bug MC-236884 as well as this one should be really corrected and not "resolved" by a dodge "works as intended".

I agree it might be a duplicate of MC-236884, but why MC-236884 was set as Resolved, when the reporters clearly wrote it was still an issue...

@W_V Could you please attach also your original datapack ?
Just for reference, to see what you have changed in the datapack.

Another description of detail steps to reproduce this kind of issue is in MCL-19640.

OK, I agree that this issue can be now considered as fixed,
however I would like to mention that this problem can still be reproduced in version 1.16.5 (and earlier),
so I think that Resolution=Fixed in 1.17 version would be more adequate in this case.

I checked this several times in versions 1.17 and 1.17.1 and now it looks like the problem has gone 😉
However I think that someone from Dev or Test team could confirm that this issue was really repaired, because I haven't found any issue fixed in 1.17/1.17.1 that would be related to the original problem I reported.

On the MC Wiki
https://minecraft.fandom.com/wiki/Java_Edition_1.17.1
it is stated that 1.17.1 is not compatible with 1.17 servers.

For anyone interested in this issue - there is a discussion thread about that problem on the official Minecraft Forum :

Does Minecraft client need a DHCP server on LAN to work properly ? (Problem: no query for DNS SRV records) - Java Edition Support - Support - Minecraft Forum
https://www.minecraftforum.net/forums/support/java-edition-support/3057536-does-minecraft-client-need-a-dhcp-server-on-lan-to

I can confirm this for 1.15.1 version.

(attachment: W-1.jpg)