mojira.dev

ziggurism

Assigned

No issues.

Reported

WEB-632 Jar files not downloadable over IPv6 Won't Fix MC-106401 Can't use leads on villagers Invalid MC-96522 No LAN interoperability, perhaps due to 32bit Duplicate MC-96521 After clicking "Delete World", hardcore world still runs in background Fixed MC-93648 Snow golems with pumpkins sheared off regain pumpkins Fixed WEB-197 Minecraft authentication server not reachable over IPv6 Won't Fix MC-92923 "Open to LAN" servers accessible on IPv6-only LAN should show up under Multiplayer without manually entering IP address Community Consensus

Comments

Mojang have stated that they're not interested in supporting IPv6 for the foreseeable future, so there is no point in me updating this bug for newer versions. Just close it as "won't fix" like the rest of them

This issue also has a discussion at reddit where there is disagreement whether Michael Wobst's solution of setting -Djava.net.preferIPv6Addresses=true is a fix,that will break in the same way for IPv4-only hosts, with a link to the jdk discussion at the JDK bugtracker

I guess this may be a duplicate of MCL-11618

This issue is affecting me on 15.2 and snapshot 20w08a. I'm not running from DMG so this seems like a bug. Why is this marked "resolved"?

So if this is a duplicate of MCPE-59043 then close it

in Minecraft 1.6, clicking delete world after dying in a hardcore world actually deleted the world from disk. So to say that "return to the title menu" is always what the actual functionality of that button was, is wrong. In my opinion this should be marked "won't fix" instead of "fixed".

I just found an illager patrol at my base, which is nowhere near any village. Is this normal? I'm not complaining, it was fun. I like the idea of action coming looking for me at my base eventually. But is this intended behavior?

@Galaxy_2Alex: yes, in my current launcher, version 2.1.2480 on Mac (version 423 (1) reported in "about Minecraft Launcher..."), the problem persists.

There are different failures to connect. Firstly, when you first start the launcher in IPv6-only mode, it goes into offline mode, and does not populate the list of newest versions and snapshots. Secondly, if you start the launcher in dual stack mode, then turn off IPv4, and select a latest version or snapshot version that is not already downloaded, then it will attempt to download but fail, with the messages:

  1. info: Preparing to launch minecraft client for 19w14b

  2. info: Checking installations.

  3. info: Minecraft client 19w14b requires 18720341 bytes to download.

  4. info:Starting!

  5. error: Unable to download https://launcher.mojang.com/v1/objects/a008dc3c45cb4f120ae5e0f124d5af2de1bafed5/client.jar to /Users/username/Library/Application Support/minecraft/versions/19w14b/19w14b.jar

On my macs, I can no longer reliably populate LAN multiplayer sessions, even if the host is not IPv6 only. I think that's MC-98598. The list also doesn't populate for IPv6-only hosts, but the discrepancy between "expected behavior" and "actual behavior" does not occur, so I cannot test this bug. Is MC-98598 a mac-only issue? Maybe this could be tested on windows boxes.

I think the services are listed at the mojang help page: https://help.mojang.com/customer/en/portal/articles/1452251-minecraft-java-edition-services

  • minecraft.net

  • account.mojang.com

  • authserver.mojang.com

  • sessionserver.mojang.com

  • skins.minecraft.net

  • textures.minecraft.net

Ideally an IPv6 infrastructure change would address all six of these Mojang servers simultaneously, as well as switching over to IPv6 on Amazon Web Services for downloading JAR files, as per WEB-632.

Like A. Mouse, my test was a 18w30b world exhibiting the bug frequently, loaded in 18w31b. Not a fresh 18w31b. Well also fixed in fresh 18w31b of course.

My 18w31a world also seems fixed. If it's indeed not fixed as Kumasasa says, then maybe it's gotten more rare?

Confirm 1.13pre4. If you never stop sprinting through the water, you never stop the swimming animation, even after you leave the water.

Another one today https://pastebin.com/jcbvgFwx. version 1.13-pre4. launcher 2.1.1144. macos 10.13.5. Exited successfully with launcher remain running 5 times or so, before crash.

@Petr Only sometimes. Launched and exited 4 times successfully before crash on 5th. Seems to be more likely to happen if game session is longer.

I have been seeing this ever since the new launcher came out. And confirm still present in today's update. launcher 2.1.1144. I'm on macOS 10.13.5, 2016 MBP with no external monitor. But I do have "keep launcher open while game runs" and "open output log" set to yes. Here is the Apple "Problem Report" dump

https://pastebin.com/L6F9UZps