mojira.dev

Justin

More than one avatar was detected! There might be multiple accounts sharing this same name.

Assigned

No issues.

Reported

MCPE-226816 Problems with the minecraft marketplaces and the skin editor Duplicate MCPE-226697 Problems with the minecraft marketplaces and the skin editor Duplicate MCPE-226593 Problems with the minecraft marketplaces and the skin editor Awaiting Response MCPE-226250 hopper destroys bundle contents Unconfirmed MCPE-222667 Game crashes randomly after around 30 minutes to an hour of game play Invalid MCPE-219552 Game stutters while playing Duplicate MCPE-217540 My founder's cape and founder's skin back was taken from me. Invalid MC-296139 Bug with the parrots Incomplete MC-280557 Blaze aggro issues Duplicate MCPE-170851 New bug since small bug fix updates before 1.20 arrives Incomplete MC-251648 Allay's AI freezes when colliding with underside of hoppers Duplicate MCPE-150636 Cannot climb or descend scaffolding blocks Incomplete MC-241079 Mountain generation appears to be cut in amplified Cannot Reproduce MC-240690 Ocean Ruins generate above sea-level Duplicate MC-240614 Guardian Farm in 1.17.1 not producing Guardians in 1.18 (Snapshots) Duplicate MC-238054 Rain glitch Incomplete MC-228360 Redstone is acting up ???? Duplicate MC-226923 "X/Y players are sleeping" message hidden by Inventory Menu Awaiting Response MCPE-127636 Unable to unlock "The Beginning" achievement Incomplete MC-218541 I can't go to any server Invalid

Comments

​I've had the problem for a few days now and I'm playing on ps5

[media]

​I already have. I even logged out and then logged in again. And it didn’tI already have. I even logged out and then logged in again. And it didn't help.

I have two videos of the stutter.

https://youtu.be/mfaWNhkcE-I

https://youtu.be/KprFk0EB3xw

But that’s for version 1.21.70 and not 1.21.80.

Edit on my report it's actually 1.21.70 I Dubble checked after reporting it

Really would be nice to see this 6 year old bug resolved. Please fix blaze farms! This should be higher priority since this is removing the fun of finding blaze spawners and wasting many players time building farms that don’t work. I know I’ve wasted many hours trying to fix double blaze spawners to no avail

What was the actual technical fix?  Does it restrict spawning to only netherbrick within the entire nether fortress bounding box (the entire square of the fortress, default 1.17/1.18 behavior) or does it restrict spawning to only the fortress structure bounding box (the tiny boxs of only the structure).

The latter has the potential to break this farm. https://www.youtube.com/watch?v=ixGwh1pJb9o

Did you break and replace any of the beds?  When trying to replicate this issue, I found that if villagers could NOT get to the place they think their bed is to see that it is not there, they will constantly remember it (checking NBT tags).  Even if I move them 250+ blocks away from their NBT home location at night, they still think their bed exists, even with other beds nearby.

I think has something to do with not SEEING their bed broken.

In 1.18, now that we cannot sleep away rain, it "feels" like it's raining too long, and too often.

 

I understand that rain in inconvenient in real life, just as it is in Minecraft, however, in cold biomes, it is a nightmare because it snows.  I also understand that thunderstorms need to happen, so rain has to happen first.

 

The sliders just need adjusting a little bit.  The time between rain needs to be longer.  The time rain lasts needs to be shorter, and the thunder (the time rain has to run before thunder shows up) should happen sooner.

Can confirm.  Repeated same process for my world, receiving same error.

  • 1.17.1 world.

  • MCA Editor out some chunks

  • Backup "trimmed world"

  • Load 1.18-pre4 successfully.

  • Restore "trimmed world"

  • Unable to Load 1.18-pre5.

 

EDIT: pre6 resolves my issue.

No longer an issue, it had been fixed. Thanks!

I'm sorry, but the hotfix has changed absolutely none of these problems. I went into my realm, everything was fine. Asked one of my players who can't get in (see above comment I left) and as soon as he tried, chests stopped opening, mobs stopped moving, can't break blocks, etc .... and he couldn't get in.

If he or the other player try to join the realm, they are unable to and it freezes the entire realm for everyone.

Again, the realm works for me (owner) and four other players (US, UK, & SE) but if either of our other two players (UK & AU) try to join, they cannot get in and the realm stops working for everyone already in the realm. 

All players have updated to the current 1.17.41 hotfix.

I have been experiencing all of the above problems on my realm for weeks now. But something that I have noticed that I've not seen mentioned in other comments is that it doesn't seem to effect everyone. For example, Me and my son (US), and three other players (US, UK and SE) can still get into the realm and play mostly normally (with some minor issues like blank signs, delayed chat, etc).

However, if two of the other players (UK & AU) try to get in, they are unable to connect. Their name will show up in the player list (but it won't say they've joined in chat), and the game will freeze for the rest of us, as described by many others: chests won't open, mobs freeze, can't break blocks, and eventually all get kicked.

The realm functions mostly normally for five of us, but is completely inaccessible for two of our players, and just their trying to join the realm breaks it for everyone.

I've given up waiting for this. Just download this RTX pack here. It's just as good if not better than the official Nvidia one. https://mcpedl.com/vanilla-rtx/

I have the exact same issue in my own world. The purple and black checkmarks on crops as you've named. It's terrible to look at. Ruins the experience. I just want to play my own world with RTX on.

I have the exact same issue. It just has purple and black checkmarks. It's terrible to look at!! Ruins the experience. I just want to play my own world with RTX on.

it also does not seam to be directly linked to MC-11193 as it happens regardless of the location in the world and the distance of the redstone line is also not effected 

well it is not MC-182452 as it breaks with solid blocks and slabs 

This workaround only works if your goal is to get you villagers not to attach to POIs period. As someone who works heavily with villagers, I need them to connect to specific POIs; this is near-impossible when villagers over 100 blocks away want are prioritized over the villager literally touching it.