Eyeth

I apologize. That might be something else.

It doesn't fade at 15th and 16th. It is at 17th vertical and horizontal of the chunk order with the adjacent chunk border behind (16th). Look closely. It has been like this since 1.11.

No, it doesn't disappear, instead it fades in which indicate the chunk border. This is useful in finding the chunks without the calculation or in game measurements.

No, I haven't try that resolve.

Evidently, the invisible stack can be picked up by the player and will become visible in hotbar/inventory and throwing dropped items/stack again.

WAI. Water disappears when waterlogged block is push or pull by piston. See changelog in 1.15 or 1.16

I was able to reproduce in east and west directions.

I recommend try this first before you uninstall the game.

Before you start the world and or close the game when you are finish playing.

Go into the world option and wait 5 seconds or so on. It basically clearing up the cache history by itself automatically. Your loading screen should be better next time. (Notice the difference between cached and cleared cache file size)

I do this after I exited the world. Because I will have chance experiencing stuck loading screen sometimes. If you are going to make a copy of world, clear cache first by wait for a few seconds when you get in world option.

Clear cache of every world. You will notice that you will be dropped from the sky in creative world. That's normal because it erased cache that remembers player's position as well as temporary data that loads up the world faster when you rejoin.

There seems to be conflicted when the system was retrieving information from the cache and saved data. IDK

Yup. Worst idea when the Dev allows wither to destroy grass/dirt blocks which flood the CPU/RAM usage quite easily. Imagine having to deal with despawn timer of every dropped items/stacks that also dropping FPS.

Suggestion: each explosion destroy fewer blocks but the damage deal to the player/ mobs stay the same

Disable auto saving would solve 99.9 percent problems. I would rather lose progress from minutes to hours than having file permanently corrupted, etc

Try it on Console Edition with auto saving disabled. Not only it reduces problem, the performance is so great. This is a dream for Bedrock.

Steps to reproduce

1. MC main menu> Settings> Video> Outline Selection> Off

2. Start world

3. Place piston

To stop piston from turning black

1. Exit world

2. MC main menu> Settings> Video> Outline Selection> On

3. Start world

4. Place piston

Yes, it will lose progress without save, corruption or losing mob won't occured. You have to make save manually at pause. I would rather lose 15 minutes to an hour progress between manual save.

I doubt it is possible on Bedrock due to the infinite world. The only way to do is backup routine.

I remembered why I disabled auto saving in Console Edition for years before Bedrock. Auto saving caused multiple issues. When it was disabled, the game became problem free, experienced rare issue but will not save upon crash or freeze eventually.
I don't like auto saving and load/unloading chunks simultaneously.

Give us the ability to disable auto saving, with the options of save the progress and save and exit at pause screen. I don't mind longer saving progression at pause. 🙂 Like we asked for from the early Bedrock release long ago. This was available in single and multiplayer in CE.

Other solution that I have been doing since disable auto saving doesn't exist in Bedrock, is to make a copy before each play session. You lose less and time than having 1 original copy. I usually have 10 or more copies. Delete oldest saves when it is safe and keep few in hand.

Exactly my thought on wasting cpu/ram usage. Also, if I may add, if 1 in number chance of mob despawning at certain range is used in 4 chunk should be disabled. Since 4 chunk is small enough for them to instant despawned in seconds to a few minutes when walking away from the player. So, having 2 similar operations running simultaneously unnecessary.

Beside that, I agreed the r44 is too small. It should have been r54 or higher.

It makes sense for r128 to have a chance of despawn at certain range since the area is very large with more than 4x mob cap. TBH, 4 chunk never need 1/xxx chance of despawning since it falls within range, keeping mobs actively near the player in small area. They will be most likely insta-despawn when move away in seconds to a few minutes after they spawned. That said having despawn by chance is useless for 4 chunk simulation distance. It only need instant despawn and spawn range from the player.

Do this test: do not sleep at all and go through all rain periods in peaceful day and night. (optional creative) Do not exit and rejoin. Sometime rain has a chance of becoming thunderstorm for a short time before return to rain. Also, there is a 0.5 to 7.5 days delay between thunderstorms.

Again, do not sleep. Try more than 7.5 days for better chance of seeing at least 1 thunderstorm event.

Best to spot them where they just spawned and have them follow and stick with you by home beach, and then breed.

20/20 turtles laying eggs successfully as of 1.14.60. Just stand and wait by its home beach patiently. Use seagrass as a leash. The turtle will attempt repeatedly between wait time in range of seconds and up to 20 minutes. But, other times it may farther several more attempts into 30 to an hour. Eventually, they will lay. I have yet find the cause of delay. I believe it is not ideal. Wiki stated it takes few minutes to lay egg, not as immediate as other animals.

How to know when:
As soon as the turtle ignores you, moving toward the potential lay location. When it stops, either starts digging or pause for a second and returning to you. Each attempt will have turtle randomly choose the lay location nearby.

For those who was hitting turtle to reset may have been just coincidence.

Comment and vote at MCPE-59043

Animal spawn in a pack of 4.

Affects 1.16.0.61