McDodge34

Now worried that Mojang totally ignores this bug, it makes the game unplayable and yet absolutely no correction, no update, nothing in over 3 days, if its anything like the 1.13 release that had a very annoying bug (can't remember which one), we may have to wait up to a month before they fix this which is extremely annoying. I would urge anyone that want to play 1.14 to use the pre-release 5 version, if only we could find the download link for the servers for it at least.

Vindicators in Patrols are killing the game for me, you can't even start any new game because they will find and kill you before you even have resources to deal with them, even in full iron armor, they killed me right away, there's no more peaceful days in this game, I give up, if this isn't adjusted to only spawn at night, the game is now unplayable. I use 18w46a.

Since you can change the color of the text now, I'm not sure if this could be considered a bug, just right click with the dye of your choice to change the color of the text on any signs, you can do this multiple times if you want.

Seems to be fixed, I can confirm, but I see a little lag spike after chopping down a tree now, its not extreme, but I think its related to the leaves despawning mechanic, which is maybe a new bug report, I'll browse through the new ones tomorrow when I have more time, if its not there, I'll try to reproduce it again and report it.

I can confirm its still in 18w43c, I'm not surprised being one of the first released snapshot for this version, perhaps it was a little bit too early, I'm blaming the new lighting engine on this one, I see the same lag for each block I mine or I put down, so I suspect its the way the new lighting engine is calculating its way out.

I also noticed this even while running a server on a 2nd PC, and also while just mining blocks in the same chunk, every single time you break a block, it stutters for a few seconds, I'm guessing its the new lighting engine, cause I see the same issue while just replacing the floor of a new house, every block I put down cause a slight freeze, I've tested this in the official 1.13.2 and I didn't see this problem at all.

Every 5-10 blocks or when I reach a chunk border, it freeze the game for a few seconds, its not a ram problem, it makes the game unplayable PC is I7 4790K 16GB, game on SSD on a GTX 770 latest java 191

I've decided to stop playing Minecraft 1.13, I'll wait till this is really fixed, its ridiculous how this game was released so badly optimized and now any simple redstone contraption for mob spawners or automation makes the game lag like crazy. Its an awesome update and I love all the new changes and the Aquatic Update, but this Vanilla update is worst in performance and fps wise than when I play Foolcraft 3 modpack which rely on a crap ton of mods and is on 1.12.2. So its clearly not my PC that is the problem. And its not only redstone, but just roaming around makes the game lag like crazy. RIP Aquatic Update, lets hope Mojang really cares about optimization soon enough. Oh yeah, its a brand new world created in 1.13 so its not an old world conversion problem either. At first my adventures were nearly smooth as butter, but the more stuff I build, the worst the performance become. Also I tested to run the server on a better PC and on my Main rig, it doesn't change anything, perhaps a little better at loading chunks on my 2nd rig that has a better SSD. 2nd rig is I5 3550, 16GB, GTX 770, Windows 8.1 Pro 64 bits.

Main PC Specs: 

Intel I7 4790K stock 4.0GHZ speed

16GB DDR3

GTX 770 OC WF3 4GB edition

Samsung 840 Pro SSD 512GB edition

Windows 10 Pro 64 bits

Latest version of Java 8

Server running the world Vanilla in 1.13 pre1

I'm the only player on this world since its family only.

Intel Q9400 2.6GHZ

8GB DDR2

Samsung 840 Pro 256GB

Video card irrelevant since its a server

Wndows 7 Ultimate 64 bits

Latest version of Java 8

My guess is optimization isn't in their top priority list right now, so many bugs need to be squashed down, I feel like the 1.13 release is still in a snapshot state and shouldn't have been released yet, but before release, there's not that much about bug reports, you start seeing them once something is officially released, cause I'm going to say perhaps only 15-20% of Minecraft players test the snapshots, the others wait for real release.

Any forums to discuss that horrible issue and vent a little, just got killed again by a horde of zombie pigmens that got shot by a ghast, smart me killed the ghast and then, I've lost a full set of diamond armors with mending on each pieces 3 stacks of nether quartz half a stack of glowstone blocks, a silk touch pick with mending on it, around 45 steak and 6 fire resistance potion. All of this because of a stupid bug that should have been fixed before but nope.

The wither skeletons can't really hit a pigmen, but you can accidentally hit a pigmen while hitting a wither skeleton, or a damn regular skeleton can hit the pigmen. Its a nightmare right now, I avoid the Nether like the plague, and I don't think they consider this a bug so I would be surprised if the fix this issue. Its getting worse with the new combat update, a swing of your sword can hit a pigmen while you wanted to just kill a blaze and bam, you're dead.

At the same time, this bug can be helpful, you can park your horse anywhere, just dig a 4x1 deep hole and you can park it there

Affect 1.9pre1 2 3 and 4, they need to fix this issue, a blaze fired at a pigmen near my blaze farm and I was dead in no time, lucky for me I always place important stuff in my ender chest

I can confirm this, was wondering why my horses were dying when I parked them in their stalls, tested it multiple time, to reproduce grab a horse, ride it for awhile and park it, they take serious damage and some die instantly if they don't have enough hearts.

Tested, horses jump fine in 15w51b, 16w02a, 16w03a, 16w04a and 16w05b, I can do a video if you get any doubts about this, this issue is affecting only 16w06a right now.

I know we're not supposed to comment but to help someone here, if you don't want to follow this thread anymore (I'm going to do the same since its fixed) look on the right of the bug report there's a number of watchers, right next to it, there's an option to stop watching this bug, this will stop sending you emails about this bug report.

I've copied the file to my local saves folder from the server and if I play it in single player, the zombie spawner works flawlessly, so it must be related to a server issue somehow.

It was assigned to Dinnerbone if I can remember, and since he's out of the project, he's not assigned anymore, I think we will end with a 1.9 without a fix for this bug which at this point is the most inconvenient and most annoying bug I've ever seen in a game, unusable minecarts and horses for more than 2 months already.

That would explain the problem we have, our AFK gold farm use iron golems to kill the zombie pigmen, so if that is the problem, we won't be able to migrate to 15w44b anytime soon. Now I totally understand cause I wasn't near the gold farm and had no problems, soon as my brother connected he's always near the gold farm, the crash started to happen.

Yup, will have to remember that mob killed by wolfs = ticking entity error I have, not easy sometimes, I'm tracking and reporting bugs for 3 different games right now