Given the state that 1.14 has arrived in I am not surprised that the modding community is dragging its feet to embrace the new version.
There are strong indications that there are significant structural and design issues with 1.14 that were not adequately addressed during snapshotting, allowing a full release to arrive with issues that would normally have been squashed during early testing. Mojang seem to have been a little too willing to dismiss many tickets on bugs.minecraft.net as 'edge cases' and this has allowed a release to arrive with broken mechanics.
This goes beyond bugs. A bug is a malfunctioning piece of code, but I suspect 1.14 contains entirely flawed mechanics that will yield terrible results no matter how well it's coded, and then there are bugs in those terrible mechanics. I am increasingly worried that even if every bad piece of code was resolved tomorrow there would still remain fundamental mechanics that are hopelessly broken.
If a physical product was sold with sort of structural and design issues that 1.14 has it would be recalled, and I feel that we're approaching that point: Mojang need to honestly evaluate the situation and say "1.14 is not ready... we need to go back to the snapshot process and rework some of these mechanics. We'll see you in three months with version 1.15"
I have been playing since the 1.5 release. By 1.8 I was deeply interested in technical Minecraft and redstone machines, but the irony of the situation today is that you avoid redstone wherever possible. Need to send a signal? Use powered rail, it costs fewer clock cycles. Got a naked hopper? Cram a dropper on top to reduce its overhead. There are mob farm designs I built in 1.8 and 1.9 that I would never even consider on 1.14 because of the insane overhead they would generate.
I have found lately that I am using mob AI mechanics for mob farms as more dynamic and productive farms come with too much server lag (let alone needing Optifine near any water flushing farm).
SciCraft are sticking with 1.12 because 1.13 and 1.14 would annihilate their performance. Despite 1.14 having impressive levels of threading (compared to previous releases) it is the worst performing release. If I have to choose between new content and working redstone... well, redstone wins every time.
One light on the horizon are the very public issues Hermitcraft are experiencing with 1.14... With some front-line youtubers in direct contact with the devs we might finally see some real action from Mojang, rather than these frustrating half measures. I just wish that Mojang would pull their finger out and get around to actually communicating the scope of the issue with the community.
Quote: A small FYI: 1.14.2 is not the last 1.14 release. We're focusing on releasing fixes for the most critical bugs (like things that cause permanent world damage or kill you) first.
Which.. Ooookayyyyyyy… and it isn't SlicedLime's "fault," I've no interest in shooting the messenger. But WOW I wish Mojang had a better handle (and priority) on these things closer to when they were reported some months ago.
Guys, relax. They are actively fixing the many bugs of 1.14, and they're actually surprisingly fast.
For me, the worst issue I've had in 1.14, was some minor rubber-banding and random lag, even though I am playing Single Player....lol.
Besides that, I keep getting blazes trying to shoot me through the walls. How they are able to track me through solid blocks is beyond me, but they do...
Anyway, I think at this point, Optifine should be getting ready for 1.14.3, because its around the corner.
In fact, some technical Minecrafters have revealed amazingly bad game design (not just buggy code, but stupid code) around raids that is causing havoc on SMP servers (and I can attest to these issues as I have both personally experienced them and received numerous end-user comments regarding them). For example, MethodZz from SciCraft published this video describing much of the 1.14 insanity: . MethodZz also pointed out other "showstopper" bugs around mob AI and other massive issues in his Showstopper series of videos. Over the last three months I have seen video after video from MethodZz and ilmango clearly demonstrating that the people cutting code for Java Minecraft, especially those implementing the new features for 1.14 (like Raids), do not know what they are doing and are making terrible design decisions.These are not minor bugs that can be fixed with a few changed lines of code; these are intrinsic flaws in the way these systems are being implemented. Many changes have been made to important underlying systems (like chunk loading and unloading, for example, and spawn chunks) and these changes have been made without a single comment in the patch notes. The changes to the spawn chunks have huge ramifications for server admins and end users, but I had to see the evidence in a video to explain what I and other users were experiencing because Mojang neglected to document a major systemic change without any community consultation and without telling anybody.
1.14.3 should address some of the piston/moving block client side lag but the reality is that Mojang has released 1.14 in a garbage state and are now scrambling to make it work. No release is ever perfect, but in my experience (spanning back to 1.5) I can't remember a release that has arrived in such an unusable state. Many of the mechanics needed significantly more testing as the changes were very broad and had knock-on effects. I remember when they were tinkering with minecart physics around 1.8 or 1.9 and they rolled those changes back because they were too much of a bear to wrestle and had too broad an impact. Any changes to villager AI has wide ranging direct and secondary impacts, and I have seen community estimates that per villager processing cost has increased by a factor of ten! If that increased cost had come with streamlined redstone wire (OMG, redstone wire processing lag... when will that garbage get addressed already?) then maybe the community could have absorbed the shock, but there were only very modest efficiency gains in 1.14 and a lot of new load (the increase in the spawn chunk count on it's own is a huge up-tick in load, especially if you
As someone who administers Minecraft servers I can say that 1.14 is a total nightmare. User complaints are through the roof and administrative workloads are radically higher than usual, even when compared with previous releases. The increased threading and new I/O system should have made 1.14 an amazing release for server admins, but instead it has been a total disaster. The "--forceUpgrade" and "--eraseCache" command line options should have made server admin's lives better, but they were snuck into the game and are still not documented anywhere. 1.14 is shambolic, and I am tired of Mojang's total disinterest in properly supporting their product.