71–80 of 85 posts
Earlier quoted context omitted.
Is that ever since 1.8 made the whole game engine vastly less efficient? The game used to run with 256MB.
Less efficient but faster, which is a fun combination. At least they seem to have improved FPS.
Earlier quoted context omitted.
The underlying voxel game engine is written in C++. https://github.com/luanti-org/luanti
Yes, the engine handles shaders, networking, DBMS backends (Sqlite, Postgres,... to store "worlds"), entities (mobs/items/vehicles...) to name the obvious things, but the logic of the game (weather, mob AI, user/world interaction, inventories, forms and other dialog box, custom world generation) and other other functions (area protections in multiplayer, account management , chat moderation , ...) are done with Lua 5…
Earlier quoted context omitted.
It's only a change on paper, in reality it was unrealistically low for a long time
Is that ever since 1.8 made the whole game engine vastly less efficient? The game used to run with 256MB.
Earlier quoted context omitted.
Yes, the engine handles shaders, networking, DBMS backends (Sqlite, Postgres,... to store "worlds"), entities (mobs/items/vehicles...) to name the obvious things, but the logic of the game (weather, mob AI, user/world interaction, inventories, forms and other dialog box, custom world generation) and other other functions (area protections in multiplayer, account management , chat moderation , ...) are done with Lua 5…
I didn't mean to make it seem small. I interpreted the comment as being surprised that it is written in a scripting language but Lua is no slouch, especially when the most performance sensitive code is C++. It's a very common pattern in games to boost iteration times - even the Unity engine does something similar.
Earlier quoted context omitted.
Are you referring to Minecraft Pi Edition that came with Raspberry Pi OS back in the day? The one made in C++ instead of the original Java edition? > run both server and client when in singleplayer - doubles memory use When did this change? It's been like that for as long as I can remember. It's actually a very common thing for games to do because it requires less code. Also it doesn't actually double memory use - ga…
1.3, not beta 1.3. Chunk data was traditionally the biggest part of Minecraft's memory use until they added a bunch more garbage.
> Chunk data was traditionally the biggest part of Minecraft's memory use until they added a bunch more garbage.
But that's only really because it is extremely light on assets that are typically large in other games.
I'm a bit indifferent about this. Obviously they made a lot of decisions that aren't good for performance but it's a tradeoff. Notch was most productive working in Java so he could pump out updates quicker, and it helped with modding even though builds were obfuscated. NBT helped maintain backwards compatibility of worlds and probably helped with modding too. If they had done things differently then Minecraft may not have been the huge success that it is.
Earlier quoted context omitted.
don’t know why you’re getting downvoted, they gave legacy users literal years to migrate
They should have made it a seamless transition for legacy users.
This 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.
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
Earlier quoted context omitted.
Less efficient but faster, which is a fun combination. At least they seem to have improved FPS.
That's probably because you got a new graphics card some time in the last 10 years.
They go hand in hand, the bigger the render area, the more game has to be simulated at once.
Earlier quoted context omitted.
That's probably because you got a new graphics card some time in the last 10 years.
The stuff they're rendering has to come from somewhere. They go hand in hand, the bigger the render area, the more game has to be simulated at once.