Live data from Hacker News

Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

videocardz.com

31–40 of 85 posts

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#31
post #11
post #3

Earlier 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

I really don't care about Microsoft's maintenance costs. I should be able to play the game I paid for 20 years from now without having to jump through hoops in the intervening period. It's not my fault that they decided to make my perfectly normal account a "legacy" account, that was their decision.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#32
post #11
post #3

Earlier 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

It would have been better if they hadn't required you to migrate at all. And a lot of people, including me, ran into issues during the migration process. Thankfully I was able to get it sorted out after contacting support, but other people weren't so lucky.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#33
post #5

Is this 16GB for those so-called "Vibrant Visuals" or just for parity with the old version? If the latter, then what's the point of the transition to Vulkan if it quadruples resource use?

Are they cutting the default world update distance to leave more room for bling too? :)

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#34
post #21

I remember playing back in like the 1.6.4 era on a piece of garbage from 2005 with a monstrous 1GB of ram.

1.6.4 released in 2013.

I'm pretty sure I had 8 GB back then, possibly 16 GB.

I can't imagine how poorly that ran.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#36
Minecraft is not more demanding than some years ago, they didn't neceserily raise it, they just updated the info page. This snapshot from 2022 says minimum 4gb and recommend 8gb: https://archive.ph/NTMU4. Source was posted some days ago: https://news.ycombinator.com/item?id=49038901

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#37
post #4

If 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.

Mineclonia is the 'game' that loads into Luanti (formerly Minetest). Luanti has a c++ core engine, but definition of the worlds, rules, games, interactions is all lua

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#39
post #21

I remember playing back in like the 1.6.4 era on a piece of garbage from 2005 with a monstrous 1GB of ram.

1.6.4 released in 2013. I'm pretty sure I had 8 GB back then, possibly 16 GB. I can't imagine how poorly that ran.

He is probably referring to Beta 1.6.x. I remember running 1.7.3 in 2011-2012 on a potentially 1 or 2GB RAM machine and some Nvidia 7xxx series card (7600?). It worked fine on Linux.

Re: Minecraft Java raises recommended memory to 16GB ahead of Vulkan transition

#40
post #12
post #8

Earlier 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.

I mean, the code is unappreciated because the fundamental premise was broken. Locking users out of their paid accounts if they don't respond within some X deadline (no matter how long X is), without a refund, is a completely unacceptable "solution" to technical debt. The fact that you tried your best to give users a good experience doesn't matter if it's serving a fundamentally broken goal.
Post reply on HN