mojira.dev

N F

Assigned

No issues.

Reported

MC-191212 Leads break when chunk loaded by player who owns leads/pet Awaiting Response MCPE-59214 Mcpacks and mcworlds can't be imported Incomplete MC-118471 Missing Strongholds Awaiting Response

Comments

Just happened again when the owning player joined the empty server (loading the chunk).  All but one of the dogs teleported and broke the leads.

No to both.  Both tests mentioned above were done with adult dogs.  Please don't mark this resolved without investigation.

This happens in all 1.16 pre-release versions, including RC1.  This, combined with villages overbreeding implies the whole breeding mechanic/calculation is busted.  You get a bunch of angry particles some times, then villages ignore bed numbers are breed 5-10 extra villagers anyway.

@Michael Yes, every pre-version of 1.16 has this issue.

@Michael It most definitely exists in 1.16 RC1.  Villager AI has not been touched in any meaningful way through the 1.16 snapshots, pre-releases, etc.  Their poor pathfinding, workstation stealing, door struggling, over breeding bugs are beyond frustrating (all have been reported here, thankfully).

Including 1.16 RC1.  It's an absolute nightmare.  What's more, I created many buildings with double doors in an attempt to avoid this.  The villagers instead press up against one door, and 'ignore' the existence of the other, just standing outside all night long.  I can nudge them to the other open doorway and they immediate walk through.  But doing that manually for many villages every night is unacceptable.

@violine1101 Having just spent a good bit of time on my server riding a very fast horse I can say two things with confidence.  General performance in 1.14.1 is worse than 1.13.2, and the bug with chunks not rendering looks solved.  I was not able to 'outrun' a single chunk.  1.14 is now officially playable for those of us previously afflicted, thanks.

@zenico13 And the masses rejoice 🙂  I can't test until later but many will be quite happy if it is solved for all.  Thanks.

  • Affects Version/s: Minecraft 1.14, Minecraft 1.14.1 Pre-Release 1 

By definition, a bug cannot affect a version and be fixed in that same version.  Which is to say, this bug isn't fixed.  MC-151084 is proof of that.  This record should actually not have been closed since you know, it was never fixed.  God help Mojang is 1.14.1 gets released and chunk loading still isn't fully fixed, customer exodus is all but guaranteed.

@violine1101 (or anyone at Mojang)

So where can we get an official update on when 1.14.1 will be available that doesn't include following every Mojang dev on Twitter?  A singular official channel that provides regular updates is needed. The silence is dismissive and to be honest, Mojang employees posting how awesome 1.14 is when so many cannot even play it is excruciatingly tone deaf.  Thanks.

@Sip When a bug in this system is set to Resolved, it means that internally they reproduced the bug, made code changes, and tested that the changes correct the issue.  It does not mean the fix is presently available.  Normally the "Fix Version" field shows you which version the fix was included in.  Here, it says "Future Version" which is to say, they haven't created a record in the system for the next version (or named it even).  They are 'stacking up' multiple bug fixes and will release an update with many fixes altogether, this one included.

The bad part is that the new version is 100% broken for so many people due to this bug, that waiting on other fixes hardly seems worth it.  A hot patch would have been more appropriate, instead of waiting for the next minor release, presumably 1.14.1.  Mojang shipped a flat busted product and seems less bothered by it that their customers are.  And that's a shame.

Make no mistake, Mojang shipped a broken product.  The fact that is clearly a critical level defect yet we receive no updates and seemingly no attention for multiple days is disappointing.  Thanks for leaving us busted on the side of the road.

@violine1101 @HelenAngel Thanks for letting me know, I was unaware of the Mod role in everything.

Helen, further updates through official (here, I suppose) channels is desired; more don't monitor Twitter.  Words articulating a mutual assessment of priority/urgency and ongoing ETAs are helpful.  As a server admin, I have users that are particularly anxious.

@violine1101 @boq Any progress reports on this would be appreciated.  I trust this is receiving the highest of priorities.  To be clear, this is a game breaking bug with no reasonable workaround.  1.14 is unplayable for a large portion of the customer base; rolling back clients and servers to 1.13 is the only way to actually play the game.  Under most considerations, this is worthy of a hotfix and I certainly hope no one internally thinks that waiting until 14.1 a month or two out is an option.  It needs to be understood plainly, the game is broken.

There are many new tickets for 1.14 release related to this issue, it's constant and consistent.  Fair to say Mojang should be ashamed this made it through and so clearly broadly effecting.

Yep, definitely an issue.  I just updated to 1.14 from 1.13 and chunks load so much slower, I can outrun them, especially on a horse.  I literally have to stop and sit still for multiple seconds for the ground below me to load.  1.14 is full on unplayable in its currents state of chunk loading.  Good lord it's terrible, legit broken.

Yep, definitely an issue.  I just updated to 1.14 from 1.13 and chunks load so much slower, I can outrun them, especially on a horse.  I literally have to stop and sit still for multiple seconds for the ground below me to load.  1.14 is full on unplayable in its currents state of chunk loading.  Good lord it's terrible, legit broken.

Yep, definitely an issue.  I just updated to 1.14 from 1.13 and chunks load so much slower, I can outrun them, especially on a horse.  I literally have to stop and sit still for multiple seconds for the ground below me to load.  1.14 is full on unplayable in its currents state of chunk loading.  Good lord it's terrible, legit broken.

 

Dedicated server, client on windows 7, local network so network lag is ruled out.

Yep, definitely an issue.  I just updated to 1.14 from 1.13 and chunks load so much slower, I can outrun them, especially on a horse.  I literally have to stop and sit still for multiple seconds for the ground below me to load.  1.14 is full on unplayable in its currents state of chunk loading.  Good lord it's terrible, legit broken.

Definitely still an issue.  I just updated to 1.14 from 1.13 and chunks load so much slower, I can outrun them, especially on a horse.  I literally have to stop and sit still for multiple seconds for the ground below me to load.  1.14 is full on unplayable in its currents state of chunk loading.  Good lord it's terrible, legit broken.