Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition
21–30 of 85 posts
Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition
#22This might have impacted me, had Microsoft not deleted my legacy account. So I suppose I'll just stick to Tekkit Classic on my pirated client.
I have lots of problems with Microsoft but the Minecraft transition was handled very responsibly.
Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition
#23This might have impacted me, had Microsoft not deleted my legacy account. So I suppose I'll just stick to Tekkit Classic on my pirated client.
Was it really Microsoft or was it Mojang? There were two account transitions, and in my experience, most customers use Microsofts name, but are complaining about the first (Mojang, not Microsoft) transition.
Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition
#24Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition
#25Earlier quoted context omitted.
I have lots of problems with Microsoft but the Minecraft transition was handled very responsibly.
don’t know why you’re getting downvoted, they gave legacy users literal years to migrate
But no, subnautica was ready to go, though the base building was just as buggy as it was before.
Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition
#26Earlier quoted context omitted.
I have lots of problems with Microsoft but the Minecraft transition was handled very responsibly.
don’t know why you’re getting downvoted, they gave legacy users literal years to migrate
Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition
#27If the new requirements are a dealbreaker for anyone, Mineclonia is a lightweight open-source alternative that runs on much weaker hardware and feels close to Minecraft.
Great platform for hacking.
Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition
#28This might have impacted me, had Microsoft not deleted my legacy account. So I suppose I'll just stick to Tekkit Classic on my pirated client.
I have lots of problems with Microsoft but the Minecraft transition was handled very responsibly.
Also, can I say what a mess the whole Microsoft account thing is? There's at least three different systems kinda duct taped together and settings are scattered seemingly at random among those systems. Want to connect your Java Minecraft instance to a server you are running? Be ready to dive through pages of kid protection and security settings looking for the option that lets you do that again. Also, logging in used to be "enter your username and password when the game starts", but now involves a bunch of bouncing around half a dozen or so Microsoft pages getting redirects that fail 60% of the time for no stated reason. It's kinda killed any enthusiasm I have for checking out new releases, just knowing that I'm going to waste 10 minutes just trying to get the damn login working again.
Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition
#29Earlier quoted context omitted.
I would agree. They honored my account, and I originally bought the game when you had to send Notch money directly for him to send you a copy. Microsoft was great in this instance.
As one of the Devs responsible for the technical part of that transition: thank you. We tried real hard to give users the best possible experience, but I think it has nevertheless been the least appreciated piece of code I have ever written. So it's nice to finally hear some positive accounts from users! So, again, just thanks for saying this.
If you choose to work for EvilCorp don't be surprised when you get assigned to work on tickets that make people unhappy.
Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition
#30Earlier quoted context omitted.
As one of the Devs responsible for the technical part of that transition: thank you. We tried real hard to give users the best possible experience, but I think it has nevertheless been the least appreciated piece of code I have ever written. So it's nice to finally hear some positive accounts from users! So, again, just thanks for saying this.
I truly think you folks did the account transition in the most user-friendly, considerate way you possibly could. There was SO MUCH TIME to migrate and SO MANY WARNINGS about it needing to be done. I'm sorry you haven't been appreciated for it. Well done!