mojira.dev
MCPE-147632

Updated world lags blocks

I copied my existing 1.17 world into the latest beta. Note: The world has existed since 1.13. The copy opens but I quickly notice that I cannot mine place or interact with blocks properly. When I try to mine the block disappears without sound or particles and the block will reappear after a minute or so. I can enter the space where that block used to be but if I am in the space occupied by the block when it reappears I will start to drown. If I try to place something in the space the missing block will almost immediately reappear instead of waiting. I cannot usually place an object anywhere but I’ve found that if I spam the place button it will sometimes work. It is difficult to interact with chests or blocks such as the crafting table; trying to usually results in nothing happening. Please note: I did not remember experiencing any of these issues prior to 1.18.0.25 when I made test upgrades of my old world.

 

I did find the block lag went away once when I ‘mined’ into a deep slate cave and moved around attempting to place torches. The way I came in had sealed back up but for a few minutes I was able to move  place and mine like normal. Eventually however the block lag returned and no amount of spamming the torch placement seemed to work.

 

 

Linked issues

Attachments

Comments 35

I tried again with version 1.18.10.20 when it came out and the issue was still there.  I tried to upload a short vide from my Xbox but was told the file size limit is 10 mb. I’ve never uploaded from my Xbox before so I’ll try and see if there is something I can do to bring down the file size.

My worlds original seed is -2063693165 (I’ve been playing it since 1.13

I trimmed my clip down to 15 seconds but it’s still too big. Unfortunately I can’t find a way to reduce the reselotiin or pixel size which I think would help tremendously.

I found I could change resolution on new clips so I recorded one of those and uploaded it.

 

in the clip the behavior was slightly different in that some blocks stayed broke after a short lag and some didnt

Update: I wanted to see what would happen so I put on a pair of elytra wings and equipped some rockets (not easy since it’s hard to open chests where I have them store, plus rockets don’t reliable go off for me when I try to launch) and flew off to unexplored chunks. I found some chunks that I had only explored since 1.17 went out, specifically a village, that I interacted with and I found I was now able to do everything as normal. It seems the lag affected centered around my home base which I had founded in 1.13 which was very close to spawn. I returned home hoping my world was working properly now but was disappointed to find I still was experiencing issues albeit everything seemed to be much less then before.

Update part 2: I was sorting through my saves to remove some of the copies I’ve made recently and I noticed a backup of my world I made over a year ago (14 months) before the 1.17 betas and I decided to try opening that in 1.18. The world updated fine and though I didn’t make any comprehensive tests I did not note the problems I reported above. Whatever made my world objectionable occurred later. I will see if I can find other not as old copies to try though usually I remove them to save space and remove clutter

25 more comments

Edit: for some reason I couldn’t attach the new screenshot with the counts. The Jiradashboard kept saying I was missing a token

 

For a quick count of llamas you could run /execute @e[type = llama] ~~~ say hi, and then count the "hi's". You could also put the [type = llama] into the other commands and use a separate player name (like "llamas") to run a llama counter.

As I said before, 250 entities is not a lot. It could be something like llama collisions or mobs unable to reach targets (MCPE-147882). Do you have zombies saved near villagers, perhaps? Or a ghast in a boat/minecart?

So I ran the ‘hi’ command on llamas and got a count of 8, which is 7 more then I knew about but doesn’t seem that high. I also counted the other mobs I knew were close to my base. Several were more then I expected but I still think short of the total the game thinks are nearby. I do not knowingly have any zombies nor any saved near my villagers which I think are out of range of my base (maybe 100 blocks or more).

I have long  noticed a curious thing about passive mobs in my world since it’s beginning : a large number of them will continuously want to head north, that is in the negative z direction. They bunch up in the north edges of their paddocks and many are pushing in that direction constantly. Whenever they get out or are taken out without a leash or food enticement and I lose track I will invariably find them north of the base. I have an ocean/swamp north of me and they will bunch up on the shore unwilling to get in the water but still looking to go further north. It’s made recapture easy whenever they get out for some reason. It’s made exploring on horses annoying because unless I leash them they will be going north almost immediately after dismounting. Even when I leash them to a post, I will find mobs at the limit of the leash trying to go north. This is especially common in horses , sheep, and pigs. Cows will do so if I have a lot of them.

I was finally able to load the 1.18.10.26 beta two days after it was released and loaded a copy of my world from when the lagging occurred. Fortunately there was now no lag! Not sure what changed, I didn’t see any bug fixes listed that had an obvious tie-in. Will keep trying some other copies when I get time and try them in the next beta"probably 

The changelog for 1.18.10.26 mentions the fix for MCPE-149214, which is the lag bug that was fixed in release in the 1.18.2 Hotfix. I guess they did not merge that into the .10 beta until this week, contrary to what some users on the Mojira Discord were reporting. I'm going to re-resolve this report as a duplicate. I'm glad your lag is gone.

Ronald Kinion

(Unassigned)

Unconfirmed

Xbox

Xbox

1.18.10.24 Beta, 1.18.10.22 Beta, 1.18.10.21 Beta, 1.18.10.20 Beta, 1.18.0.25 Beta

Retrieved