Bachsau
- Bachsau
- bachsau
- Europe/Berlin
- Yes
- No
MC-15525
MCPE-11018
MCL-4368
Minecraft does not use or event try to connect to IPv6 servers, even if there is a correct and working AAAA record. According to Java documentation this is a default behaviour
thatcan be changed through java.net.preferIPv6Addressesvariable, but it's a bad setting for the future,to continue using IPv4 when IPv6 is avaible. Minecraft should prefer IPv6.Minecraft does not use or event try to connect to IPv6 servers, even if there is a correct and working AAAA record. According to Java documentation this is a default behaviour which can be changed through java.net.preferIPv6Addresses system property. It's a bad setting for the future to continue using IPv4 when IPv6 is available. Minecraft should prefer IPv6 wherever possible.
Minecraft does not use or event try to connect to IPv6 servers, even if there is a correct and working AAAA record. According to Java documentation this is a default behaviour which can be changed through java.net.preferIPv6Addresses system property. It's a bad setting for the future to continue using IPv4 when IPv6 is available. Minecraft should prefer IPv6 wherever possible.
~ Reopen
Minecraft does not use or event try to connect to IPv6 servers, even if there is a correct and working AAAA record. According to Java documentation this is a default behaviour which can be changed through java.net.preferIPv6Addresses system property. It's a bad setting for the future to continue using IPv4 when IPv6 is available. Minecraft should prefer IPv6 wherever possible.
~ Reopen
is cloned by
MC-15555
Played on Minecraft Realms in a default survival world
options.txt
Since Minecraft 1.10 the player gets an en
ourmousspeed burst while in the air when jumping while running. It seems to accelerate to that of flying players. This was not the case with 1.9 and before.Since Minecraft 1.10 the player gets an ennredgg speed burst while in the air when jumping while running. It seems to accelerate to that of flying players. This was not the case with 1.9 and before.
Since Minecraft 1.10 the player gets an en
nredggspeed burst while in the air when jumping while running. It seems to accelerate to that of flying players. This was not the case with 1.9 and before.Since Minecraft 1.10 the player gets an enormous speed burst while in the air when jumping while running. It seems to accelerate to that of flying players. This was not the case with 1.9 and before.
Tell me why are you forcing me to have a WiFi connection to use realms? I'm having a fast 3G or LTE connection on the go. Inacceptable for a paid service.
Just rated Minecraft PE one star until this is fixed.
Ok, seems I have either been mistaken or they added this new switch with latest version. Anyway, it works now.
However, I find it somewhat confusig that it tells me "You need to be connected to a WiFi network to play with your friends" instead of "You need to enable use of mobile data".
The "Use cellular data" option is an operating system's setting about what an app is allowed to do. It applies to everything a specific app does and controls it's sandbox. But even if I allow Minecraft PE to use cellular data, it still demands I need a WiFi connection to play on realms. I'm asking the developers to not patronize users in terms of what connection method they are using.
No! Minecraft itself tells me: You need WLAN to play with your friends on realms. It is a useless, artifical limitation.
Tell me why are you forcing me to have a WiFi connection to use realms? I'm having a fast 3G or LTE connection on the go. Inacceptable for a paid service.
!
Realms demands WLAN?!
They look like tombstones. Funny way to build creepy graveyards^^
As I don't know HOW this was fixed: Wouldn't it be better to always run any structure generation code AFTER basic world generation is complete in general?
The launcher is unable to start legacy versions since the latest update.
What I expected to happen was...:
The legacy version being downloaded and started.What actually happened was...:
I got a "Sorry, couldn't start..." messageExcerpt from launcher_log.txt:
{{[Info: 2022-11-07 19:49:02.812957106: MinecraftJavaLoggingContext.cpp(52)] Launcher/launcher (main) Info Preparing to launch minecraft client for 1.8.9
[Info: 2022-11-07 19:49:02.812985754: MinecraftJavaLoggingContext.cpp(52)] Launcher/launcher (main) Debug Created game directory <APPDIR>
[Info: 2022-11-07 19:49:02.813026227: MinecraftJavaLoggingContext.cpp(52)] Launcher/launcher (main) Debug Prepared asset index
[Info: 2022-11-07 19:49:02.813321755: NetQueue.cpp(695)] NetQueue: Starting net action https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json
[Info: 2022-11-07 19:49:02.819167590: LauncherAppRenderer.cpp(290)] MCLauncher.triggerUpdateEvent("coreEvent.gameInstances");
[Info: 2022-11-07 19:49:02.840862352: LauncherAppRenderer.cpp(290)] MCLauncher.triggerUpdateEvent("coreEvent.gameInstances");
[Info: 2022-11-07 19:49:03.364740315: NetQueue.cpp(484)] NetQueue: Primary ip: 54.231.160.56, Host: s3.amazonaws.com
[Info: 2022-11-07 19:49:03.364809714: NetQueue.cpp(573)] NetQueue: Action finished: https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json
[Warning: 2022-11-07 19:49:03.365097243: Downloadable.cpp(242)] Couldn't download $HOME/.minecraft/assets/indexes/legacy.json after (0) retries : FAILED_TO_DOWNLOAD
Details:
URL: https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json
Name: legacy.json
File: <APPDIR>/assets/indexes/legacy.json
[Info: 2022-11-07 19:49:03.370699966: MinecraftJavaLoggingContext.cpp(52)] Launcher/launcher (main) Error Unable to download https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json to <APPDIR>/assets/indexes/legacy.json
[Warning: 2022-11-07 19:49:03.370788921: MinecraftJavaInstallerContext.cpp(786)] Error preparing asset index
[Warning: 2022-11-07 19:49:03.370775061: NetQueue.cpp(607)] Action https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json failed in response handler. response code: 403 - error string: '
[Warning: 2022-11-07 19:49:03.370865501: MinecraftJavaProductInstance.cpp(487)] Install result has error.}}The launcher is unable to start legacy versions since the latest update.
What I expected to happen was...:
The legacy version being downloaded and started.What actually happened was...:
I got a "Sorry, couldn't start..." messageExcerpt from launcher_log.txt:
[Info: 2022-11-07 19:49:02.812957106: MinecraftJavaLoggingContext.cpp(52)] Launcher/launcher (main) Info Preparing to launch minecraft client for 1.8.9
[Info: 2022-11-07 19:49:02.812985754: MinecraftJavaLoggingContext.cpp(52)] Launcher/launcher (main) Debug Created game directory <APPDIR>
[Info: 2022-11-07 19:49:02.813026227: MinecraftJavaLoggingContext.cpp(52)] Launcher/launcher (main) Debug Prepared asset index
[Info: 2022-11-07 19:49:02.813321755: NetQueue.cpp(695)] NetQueue: Starting net action https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json
[Info: 2022-11-07 19:49:02.819167590: LauncherAppRenderer.cpp(290)] MCLauncher.triggerUpdateEvent("coreEvent.gameInstances");
[Info: 2022-11-07 19:49:02.840862352: LauncherAppRenderer.cpp(290)] MCLauncher.triggerUpdateEvent("coreEvent.gameInstances");
[Info: 2022-11-07 19:49:03.364740315: NetQueue.cpp(484)] NetQueue: Primary ip: 54.231.160.56, Host: s3.amazonaws.com
[Info: 2022-11-07 19:49:03.364809714: NetQueue.cpp(573)] NetQueue: Action finished: https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json
[Warning: 2022-11-07 19:49:03.365097243: Downloadable.cpp(242)] Couldn't download $HOME/.minecraft/assets/indexes/legacy.json after (0) retries : FAILED_TO_DOWNLOAD
Details:
URL: https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json
Name: legacy.json
File: <APPDIR>/assets/indexes/legacy.json
[Info: 2022-11-07 19:49:03.370699966: MinecraftJavaLoggingContext.cpp(52)] Launcher/launcher (main) Error Unable to download https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json to <APPDIR>/assets/indexes/legacy.json
[Warning: 2022-11-07 19:49:03.370788921: MinecraftJavaInstallerContext.cpp(786)] Error preparing asset index
[Warning: 2022-11-07 19:49:03.370775061: NetQueue.cpp(607)] Action https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json failed in response handler. response code: 403 - error string: '
[Warning: 2022-11-07 19:49:03.370865501: MinecraftJavaProductInstance.cpp(487)] Install result has error.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
Bachsau, I doubt its a CPU or RAM Issue. Because he can still play the game.
My guess would be check hard-drive space, I know that happens with low space.
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
Bachsau: That would make sense, except for the fact that ores and such are part of a second layer of world generation (that occurs once a chunk has neighboring chunks), which is the same layer that structures are generating in. But I'm guessing the fix was to make sure that within the second layer, mansions are generated after ores. Though there is the complication of mansions spanning several chunks. I'm not actually familiar with the generation code; this is based off of what I remember it looking like the last time I looked at it.
I also don't know anyone with a "broken" IPv6 stack but many with truly native IPv6 connections through cable internet. If 0.015% can't connect, those 0.015% should fix their network settings.
> This is why we opted eons ago to prefer ipv4.
Time for a change. Eons ago is not today!
> Would an IPv4 user be able to connect to an IPv6 server?
He would be able connect to a dual stacked server. Indeed Minecraft WILL connect via IPv6 if available and the server can't be reached by IPv4, but the standards say IPv6 should be preffered and tried first. Minecraft violates this standard by prefering IPv4.
> [...] when you yourself are the minority.
IPv6 traffic is only a minority because of decisions like the one described here.
PS: Does anyone know how to reopen the bug?
And how do you expect it to become "mainstream" when everyone disables it instead of forcing people to fix their configuration? So angry about this. >
If they had other, non-ipv6 related connection issues you also couldn't help them, besides telling them the problem is on theirs side, and they will have to fix it.
But if people really encounter that sort of "bind exceptions", there is indeed something you can do instead: Catch the error and use IPv4 instead, but don't do it in general! You could also add a "Disable IPv6" setting for those not willing to fix their system. Be innovators not blockers!
And please don't ignore the community's wishes by closing bugs whose discussion is not finished yet.
It is not mojangs part to solve peoples computer problems in general. You also wouldn't help me if I wouldn't know how to install java on my linux system, would you? Anyway, the easiest guide for computer fools would be to tell them to disable IPv6 localy. In the system or in the launcher. And what is volatile on trying something else before doing what you already do? You also won't have to do it in the launcher. It would be enough to prefer IPv6 when connecting to multiplayer servers.
> if I order a product, I don't want it to be broken
Then why do you accept it to be broken? Why do you accept broken IPv6 stacks? If people would care, like you do, it wouldn't be broken.
> people just don't want to fix it.
They would if they weren't able to play their favorite game without it. Again, this is not Mojangs broblem. Minecraft isn't broken if it supports modern technology, their network connections are. People should blame their computer manufacturers and internet providers, and urge them to do something about it, not Mojang. But Minecraft is broken for me because I have to fix Minecrafts IPv6 connection where it should just work.
Using an automatic error handling and correction system solves this problem on both sides. Try-and-Catch mechanisms are everything but volatile. If something doesn't work in one way, it is done the other way. Wheres the problem?
New class is "net.minecraft.bootstrap.Bootstrap"
Idiots who are unable to configure their networks correctly should not expect anything to work, including minecraft. Making available new technology has nothing to do with "breaking" something. Even Google has AAAA records on their domains today. People with network configurations broken like that wouldn't even be able to search the web. So for hells sake they'll fix it!
I always wonder how mods and developers handle bugs, as if it were the reporters job to keep information up to date and test all sort of things. You should be clear on the fact, that it is your project. People pay for it and you should be thankful for anyone reporting bugs. It is your job to test, find and fix. Bugs usually don't fix themselves, so there is no reason to ask if something is still an issue in any later version. If no one has worked on it, it will! You can use your version control system to find out if there have been changes to relevant code sections. Users are not responsible for bugs in your project and don't have to care to get them fixed. If a product is full of bugs people will get frustrated and don't pay for it any longer. It is in your interesst to get any bugs fixed.
Are you sure this is a duplicate of #9722? I never switched between Survival and Creative. It has always been a Survival world.
> Because we manage such a vast quantity of open tickets
> It is not reasonable to test all 4,000 tickets
That should alert the people at Mojang as it shows they are incapable of good bug management. Developers should fix known bugs BEVORE doing new releases. If every bug would be fixed the time it is reported, there weren't so much tickets and there would be nothing old to test after releasing new versions.
When bugs are handled the way they are currently handled, they will almost never be fixed and this tracker is just useless.
> You're suggesting fixing 4000 bugs before next Wednesday.
I suggest releasing things when they're done. Which not means next Wednesday. Stable versions should be, well... – stable. That means not contain any known bugs.
May I suggest adding a bug type of "Feature Request" to the tracker, so they can be easily distinguished from bugs and do not need to be closed?
According to
MC-90885this seems to be somehow connected to specific worlds, so it might be of help if someone affected would upload his world. You could also start versioning your world with git whenever you exit a game for the developers to see what was going on before and after this occured.I think there must be something wrong with your CPU or RAM as this doesn't ever happen to most people while it always happens to you.
Also got this, but also with exactly the same integer of 165762. I really hope this didn't corrupt any biomes. If this affects saving, I would prefer it to fail/crash/retry instead of defaulting to anything.
Is it possible that this is somehow dependant on how old a boat is? I just tried to land some old boats floating around and always died. However, when I crafted a new boat and drove that into dock, I got no damage. In neither case I was in any boat longer than a few seconds. Minecraft 1.8.9.
Try using the Java Launcher. Mojang has proven itself incapable of coding a working native launcher.
Played on Minecraft Realms in a default survival world on Ubuntu Linux 14.04 with latest Java from Oracle using attached options.txt
How could a screenshot help anyone with something that can only be observed in a moving environment? o_O
You can test this by running around a while in any survival world. Maybe I can post a screencap video when I have time to and find it important enough to install a tool for this.
Hey, Mojang! This seems very special. Don't you think it is definitely worth further investigation even if only a small number of players is affected?
Using the java launcher on Linux all old versions are able to use their directory completely, so it's at least possible.
Look like some sort of file access problems. Check your access rights and filesystem.
But I still don't get why it continues to start when it can read neither level.dat nor level_dat.old. It definitely shouldn't!
@C.J. Bennett: No, it doesn't help anyone if you grab some random bug report and talk about something completely different. Furthermore I can't find anything buggy in what you describe.
Particles from hard materials should be removed completely. It looks weird. You won't whirl up dust when running on stone, wood or glass.
@C.J. Bennett: Right click your minecraft save folder, choose "properties", then "security" tab. Use Google and/or Wikipedia for further information on Windows access rights. However, this was an on-topic comment and might not effect your problem, which I think is not part of any bug at all.
If you think it is, please open another bug report! This one is about misplaced chunks, not about animals spawning in unexpected places.
Why not just remove the 1 extra damage for all mobs?
@joezim007 A player should never expect the game to crash and never worry about it. Things can work or not but should never result in a crash.
No, @Tiya tehJak, it has nothing to do with whatever you're trying. Please do not hijack other people's threads. This Bug is about the minecraft profile directories that can be set in the launcher.
When this bug was opened, Minecraft did not prefer IPv6. After Microsoft purchased Mojang, IPv6 support was removed completely, and it won't return anytime soon, as bad as that is. Microsoft is an enemy of IPv6. None of their services is available via IPv6. Microsoft does not adopt new technology unless they are absolutely forced to.
Seems to be a problem with access rights on AWS. This is what I found in my launcher log:
[Info: 2022-11-07 19:49:02.812957106: MinecraftJavaLoggingContext.cpp(52)] Launcher/launcher (main) Info Preparing to launch minecraft client for 1.8.9
[Info: 2022-11-07 19:49:02.812985754: MinecraftJavaLoggingContext.cpp(52)] Launcher/launcher (main) Debug Created game directory <APPDIR>
[Info: 2022-11-07 19:49:02.813026227: MinecraftJavaLoggingContext.cpp(52)] Launcher/launcher (main) Debug Prepared asset index
[Info: 2022-11-07 19:49:02.813321755: NetQueue.cpp(695)] NetQueue: Starting net action https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json
[Info: 2022-11-07 19:49:02.819167590: LauncherAppRenderer.cpp(290)] MCLauncher.triggerUpdateEvent("coreEvent.gameInstances");
[Info: 2022-11-07 19:49:02.840862352: LauncherAppRenderer.cpp(290)] MCLauncher.triggerUpdateEvent("coreEvent.gameInstances");
[Info: 2022-11-07 19:49:03.364740315: NetQueue.cpp(484)] NetQueue: Primary ip: 54.231.160.56, Host: s3.amazonaws.com
[Info: 2022-11-07 19:49:03.364809714: NetQueue.cpp(573)] NetQueue: Action finished: https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json
[Warning: 2022-11-07 19:49:03.365097243: Downloadable.cpp(242)] Couldn't download $HOME/.minecraft/assets/indexes/legacy.json after (0) retries : FAILED_TO_DOWNLOAD
Details:
URL: https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json
Name: legacy.json
File: <APPDIR>/assets/indexes/legacy.json
[Info: 2022-11-07 19:49:03.370699966: MinecraftJavaLoggingContext.cpp(52)] Launcher/launcher (main) Error Unable to download https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json to <APPDIR>/assets/indexes/legacy.json
[Warning: 2022-11-07 19:49:03.370788921: MinecraftJavaInstallerContext.cpp(786)] Error preparing asset index
[Warning: 2022-11-07 19:49:03.370775061: NetQueue.cpp(607)] Action https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json failed in response handler. response code: 403 - error string: '
[Warning: 2022-11-07 19:49:03.370865501: MinecraftJavaProductInstance.cpp(487)] Install result has error.
Same problem as
MCL-22665andMC-257293. Looks like M$ did screw up their AWS. In any case log files are much more useful than screenshots.You're inventing a problem that doesn't exist. It actually is a security feature that you can not just replace the contents of the game directory with anything else and have the launcher run it. Furthermore there is no good reason to try running the game with a runtime it wasn't created for. Even if the patches applied to java are security related, it is highly unlikely that it affects Minecraft in any way.
It seems to affect every legacy version on every operating system. Access to "https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json" is blocked, so the launcher can't download the assets. I would tentatively assume they moved more of the content to Azure and forgot about the legacy versions.
@violine1101 The Launcher is not displayed on the bug tracker's home page, so it is not obvious there is a section for it. You should consider having the logo of all tracked projects there. While there currently seem to be seven projects on this tracker, the start page lists only four of them and even your link list is missing the Mojang Web Services and Bedrock Dedicated Server.
It seems to affect every legacy version on every operating system. Access to "https://s3.amazonaws.com/Minecraft.Download/indexes/legacy.json" is blocked, so the launcher can't download the assets. I would tentatively assume they moved more of the content to Azure and forgot about the legacy versions.
I can confirm this is fixed, and exactly in the way I expected. Instead of putting it up on AWS again, they patched the launcher to get its files from elsewhere.
What details do you want? I think I gave every information there is. If you don't understand the request please inform yourself. Here's some more information on the updated gamertags in case you don't know what I'm talking about: https://support.xbox.com/en-US/help/account-profile/profile/gamertag-update-faq
Your questions are unreasonable and not applicable to the problem. Therefore I infer that you're unwilling and/or too lazy to implement the required changes. Of course it's always easiest to make up reasons so you can dismiss the problem. Unfortunately, bad quality control is something I can do nothing about. Have a nice day.
I think there should be a single UUID that's shared by all demo players.