The worst version is 1.8 because it takes forever for mobs to cross a river when they're following the player. The boat breaks easily.
This is the least of the issues with 1.8, and all newer versions:
Minecraft 1.8 has so many performance problems that I just don't know where to start with. Maybe the biggest and the ugliest problem is the memory allocation. Currently the game allocates (and throws away immediately) 50 MB/sec when standing still and up to 200 MB/sec when moving. That is just crazy.
5. Why is 1.8 allocating so much memory? This is the best part - over 90% of the memory allocation is not needed at all. Most of the memory is probably allocated to make the life of the developers easier. [say what? how is bloated, over-complicated, over-abstracted, overly object-oriented code making their lives easier?]
The resource usage of modern versions is truly insane and this is hampering the playability of the game; for comparison, my own heavily modded version based on 1.6.4 uses minimal resources even in a biome which is more demanding than anything in vanilla; the only advantage that 1.8+ may have is multithreaded chunk rendering which doesn't even work that well (there would be zero lag spikes/framerate drops if chunk updates were truly independent of the render thread):
Nearly 1000 FPS, 1 millisecond server tick time (only 2% of the maximum), and 95 MB of memory usage out of only 243 MB allocated:
This was taken while flying around, generating new chunks; FPS decreased to around 300 due to chunk updates (a single thread both renders to the screen and updates chunks so the frametime is the sum of both), but still well above a more typical capped framerate, while server tick time is still less than 10 ms with memory usage varying between 100-200 MB at the rate of around 10 MB per second; the JVM felt no need to allocate more to keep up with garbage collection (243 MB seems to be the minimum it allocates):
Also, it only took 3 seconds to generate a "Mega Forest" world, despite only a single thread used for all server functions (1.13 multithreaded world generation, yet somehow it took 5 times longer to generate a world with more or less average terrain; forest, extreme hills, plains; the slowness of 1.13+ even adversely affects 3rd party tools like AMIDST):
TMCW:
2021-04-02 09:21:27 [SERVER] [INFO] Starting integrated minecraft server version 1.6.4
2021-04-02 09:21:27 [SERVER] [INFO] Generating keypair
2021-04-02 09:21:27 [SERVER] [INFO] Converting map!
2021-04-02 09:21:27 [SERVER] [INFO] Scanning folders...
2021-04-02 09:21:27 [SERVER] [INFO] Total conversion count is 0
2021-04-02 09:21:27 [SERVER] [INFO] Preparing start region for level 0
2021-04-02 09:21:28 [SERVER] [INFO] Preparing spawn area: 14%
2021-04-02 09:21:29 [SERVER] [INFO] Preparing spawn area: 49%
2021-04-02 09:21:30 [SERVER] [INFO] TheMasterCaver[/127.0.0.1:0] logged in with entity id 46 at (28.5, 64.0, -89.5)
2021-04-02 09:21:30 [SERVER] [INFO] TheMasterCaver joined the game
1.13 (this is the most recent version that I have run at all):
Also, Mojang completely missed the point of world customization; why can we still not customize the way caves generate? It would have been extremely easy to at least add "size"/"density" sliders to the 1.8 customization options, even now you can't change the frequency of mineshafts or dungeons (the latter could in 1.8-1.12.2).
Of course, that wouldn't even be needed if not for the changes in 1.7, which is truly the worst update in the game's history to me - it completely killed off any possibility of me ever playing vanilla on any newer version, which has also meant not playing them period (I've only briefly run a few newer versions to check something out, and not since 1.13). 1.17? Too late; I've been making made my own cave generation mods since 2013 with just the sort of generation that I prefer (one of my mods even made the ground up to 192 layers deep, 1.5x that of 1.17, though I prefer a more horizontally-oriented underground which is why I currently do not increase the depth beyond making bedrock one layer and lowering lava level to y=4), and I dislike many of the other changes they have made since 1.7; like, what is the point of adding new biomes if you'll mostly see the same 2-3 biomes unless you explore very far? In my modded worlds I've found dozens of biomes within only 1000-1500 blocks of spawn, ranging the full gamut of biome variations (deserts next to snowy biomes? Why not? Minecraft isn't and shouldn't be realistic).
The Meaning of Life, the Universe, and Everything.
Join Date:
1/21/2019
Posts:
43
Member Details
For me it was Beta 1.0, honestly just a disappointment. Hell, I struggle to remember what was even added aside from bug fixes, I think the "Finally Beta!" splash text? I really don't know, there were updates that you could call objectively worse but I guess I was expecting more for the game finally reaching the Beta stage and the price going up because of it.
Looking at the game from just standard, single player, survival I'd consider 1.9 to be one of the best updates, probably at least one of the top 5 for me. It added 2 insanely needed quality of life features and made the end somewhat useful
Rollback Post to RevisionRollBack
Come checkout my Youtube channel with Minecraft / general gaming videos - C4lico
In my opinion, it was Release 1.6. There were a lot of things that urgently needed improvement, but Mojang somehow decided to add horses, as if half of the games out there didn't already have horses. Hard to appreciate the fact that baby zombies now spawned naturally.
1.10 was at least understandable. Perhaps Mojang was scared of adding something too controversial after 1.9.
In my opinion, it was Release 1.6. There were a lot of things that urgently needed improvement, but Mojang somehow decided to add horses, as if half of the games out there didn't already have horses. Hard to appreciate the fact that baby zombies now spawned naturally.
1.10 was at least understandable. Perhaps Mojang was scared of adding something too controversial after 1.9.
Can't forget 1.14 either with the new textures.
Baby zombies are hard to hit because they're too fast and I rarely use horses.
For java.
Thanks.
Neither of these options.
The worst version is 1.8 because it takes forever for mobs to cross a river when they're following the player. The boat breaks easily.
My videos: https://www.youtube.com/user/robingravel
My cartoons: http://www.dailymotion.com/robin-gravel
Flash Animation (if your computer supports flash):
http://robingravel.byethost15.com/eflash.htm
Few flash movies have easter egg/extras
This is the least of the issues with 1.8, and all newer versions:
The resource usage of modern versions is truly insane and this is hampering the playability of the game; for comparison, my own heavily modded version based on 1.6.4 uses minimal resources even in a biome which is more demanding than anything in vanilla; the only advantage that 1.8+ may have is multithreaded chunk rendering which doesn't even work that well (there would be zero lag spikes/framerate drops if chunk updates were truly independent of the render thread):
This was taken while flying around, generating new chunks; FPS decreased to around 300 due to chunk updates (a single thread both renders to the screen and updates chunks so the frametime is the sum of both), but still well above a more typical capped framerate, while server tick time is still less than 10 ms with memory usage varying between 100-200 MB at the rate of around 10 MB per second; the JVM felt no need to allocate more to keep up with garbage collection (243 MB seems to be the minimum it allocates):
Also, it only took 3 seconds to generate a "Mega Forest" world, despite only a single thread used for all server functions (1.13 multithreaded world generation, yet somehow it took 5 times longer to generate a world with more or less average terrain; forest, extreme hills, plains; the slowness of 1.13+ even adversely affects 3rd party tools like AMIDST):
1.13 (this is the most recent version that I have run at all):
Also, Mojang completely missed the point of world customization; why can we still not customize the way caves generate? It would have been extremely easy to at least add "size"/"density" sliders to the 1.8 customization options, even now you can't change the frequency of mineshafts or dungeons (the latter could in 1.8-1.12.2).
Of course, that wouldn't even be needed if not for the changes in 1.7, which is truly the worst update in the game's history to me - it completely killed off any possibility of me ever playing vanilla on any newer version, which has also meant not playing them period (I've only briefly run a few newer versions to check something out, and not since 1.13). 1.17? Too late; I've been making made my own cave generation mods since 2013 with just the sort of generation that I prefer (one of my mods even made the ground up to 192 layers deep, 1.5x that of 1.17, though I prefer a more horizontally-oriented underground which is why I currently do not increase the depth beyond making bedrock one layer and lowering lava level to y=4), and I dislike many of the other changes they have made since 1.7; like, what is the point of adding new biomes if you'll mostly see the same 2-3 biomes unless you explore very far? In my modded worlds I've found dozens of biomes within only 1000-1500 blocks of spawn, ranging the full gamut of biome variations (deserts next to snowy biomes? Why not? Minecraft isn't and shouldn't be realistic).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
I don't know what the worst update is out of those ones, it has been a while since I played those versions.
I will say that Java began to run so much worse just before I migrated to bedrock edition however.
And I think at the time I was maining with render distances of 12 to 16 chunks, yet I was still receiving lag spikes,
and I tried allocating 2gb and 4gb, none really eliminated the problem.
if it were true, that it were my PC that was causing the problem then I would've been experiencing similar issues on bedrock edition also.
But clearly it wasn't.
supposedly Mojang made Minecraft Java multithreaded, I forgot which update it was though,
but it doesn't seem to do a very good job of that for some reason, lots of people not just myself
have complained about Minecraft Java and the majority of its performance issues seem to be stemming from the way it
handles chunk loading.
For me it was Beta 1.0, honestly just a disappointment. Hell, I struggle to remember what was even added aside from bug fixes, I think the "Finally Beta!" splash text? I really don't know, there were updates that you could call objectively worse but I guess I was expecting more for the game finally reaching the Beta stage and the price going up because of it.
Looking at the game from just standard, single player, survival I'd consider 1.9 to be one of the best updates, probably at least one of the top 5 for me. It added 2 insanely needed quality of life features and made the end somewhat useful
Come checkout my Youtube channel with Minecraft / general gaming videos - C4lico
In my opinion, it was Release 1.6. There were a lot of things that urgently needed improvement, but Mojang somehow decided to add horses, as if half of the games out there didn't already have horses. Hard to appreciate the fact that baby zombies now spawned naturally.
1.10 was at least understandable. Perhaps Mojang was scared of adding something too controversial after 1.9.
Can't forget 1.14 either with the new textures.
Baby zombies are hard to hit because they're too fast and I rarely use horses.
My videos: https://www.youtube.com/user/robingravel
My cartoons: http://www.dailymotion.com/robin-gravel
Flash Animation (if your computer supports flash):
http://robingravel.byethost15.com/eflash.htm
Few flash movies have easter egg/extras
even worse is they can catch a ride on an animal mob and make themselves that much harder to hit.
They're still not as bad as Creepers though, at least you can hear zombies in all their forms.