Rio
- Riothamus
- riothamus
- America/Indiana/Indianapolis
- Yes
- No
MCPE-38165
This is what the areas that were already rendered but then upon later return where destroyed by the game look like on a map:
20181014_124930.jpg
We noticed while playing on the Switch yesterday that hunger points are not accurately being accounted for, details below:
In all instances we found, "consuming" food would award the display properly of hunger points as it was supposed to, but in the coding background it would not always actual register.
One way we could tell when the issue occurred: food was consumed, hunger points, were restored, but food item stock was not depleted.
Another way we could tell when the issue occurred: food was consumed, hunger points were restored to within 1 point of maximum, yet health did not regenerate.
In both cases, attempting to eat another food would correctly remove the previously awarded hunger points to show what the game had actually registered.
We have found in our gameplay that this issue is currently occurring 100% of the time with Cooked Mutton.
We have also attempted Potatoes, Carrots, Raw Chicken, Raw Mutton, Raw Beef, Raw Porkchop. Sometimes each of them would work, and sometimes they would glitch with the above outlined bug.
Edit (more details of what we tested / observed):
-These were not during periods of lag or chunk loading; they were during seamless gameplay.
-Food was properly and fully consumed (as acknowledged by the awarding of the hunger points). Sometimes even eaten without letting the button go so that multiple were eaten back-to-back.
-All unnecessary Minecraft video options were disabled.
![[MCPE Mod] Auldrick](../../../data/avatars/users/10122.svg){kind=small}
Rio: Yes, I agree that your other report describes a different issue. I will reopen it momentarily. Sorry for the delay in noticing your appeals.
I noticed a lot of "Issue Links" have been referenced and marked as resolved. Could you please add my MCCE-4714 that I started a year and a half ago to that list please. I had posted it about the animals becoming non-responsive to their owners and essentially becoming stuck, as they were told to be in their sit positions before the error occurred.
The ticket was for the Wii U, but we tried converting the world to Switch when Switch came out, and later converting it to Bedrock, but the issue was never fixed.
It will be nice when this rolls out - that world that I cited the issues with has been dead to us since that time, because our villages were overrun with non-responsive pets!
I can also confirmed this happened to us on our world.
Nintendo Switch - logged into accounts. Version 1.6. Survival world, Normal difficulty. Two players.
We had one Skeleton Horse in a pen in our village. Another person went exploring and came upon a Skeleton Trap. Managed not to kill three skeleton horses. Tied them to leads and tried to lead them back to the village. One by one, they died off. Upon checking the pen in the village, our previous Skeleton Horse had also died and was now gone.
No issue pre-1.6.
I can also confirm this, it is a feature we've been lacking since the introduction of Bedrock for Nintendo Switch and sometimes when we just get really frustrated we load up the old Minecraft for Switch where there were no cursor wrapping issues.
Console: Nintendo Switch. Version: current (1.6). Current world mode: Survival, Normal, two players.
Confirmed on Nintendo Switch 10/12/18 on current version at that time. Survival world, normal mode, two players on same local device, local world non-server/realm. I will have to check on what Texture pack we were using, but it was not City for us, I believe we used the Natural pack on that world.
Unable to reproduce - it happened only that one time.
Our solution was to immediately Save & Quit the game and reload. That fixed it in the moment.
With all due respect, this is NOT a duplicate AT ALL.
MCPE-19308is truly two issues in the same bug report - it is about rendering issues - about the blocks taking a while to show up, and a little bit of this. I am aware of that, I have that issue too.The sole focus of this bug is that the blocks were ALREADY rendered, and are now COMPLETELY destroyed by coding. Please reopen this, unless Mod Neko believes on behalf of Jagex that the two issues are resolved in the same strand of game coding, then I will concede.
Four screenshots added - one showing our 3x5 map at zoom level 3/4. We are standing right at the crosshairs (green indicator). The destroyed areas are at the western/northwest (black areas). Closeups show them are pure black after the areas are destroyed by the game coding.
Three more added of another in-person destroyed chunk where it's showing and you can see the snow thinks there's supposed to be land there, and it'll sit and form, but then within a couple of seconds it falls down to the abyss because there are no actual blocks after the coding destruction destroyed the area.
Mods needs to re-evaluate this.
The main issue on this page is the rendering issue of how long chunks take to load, with two screenshots touching on a second opposite issue of the coding's permanent destruction of game chunks!
To that end,
MCPE-38165is NOT a duplicate because it is SOLELY about the coding's DESTRUCTION of ENTIRE chunks AFTER RENDERING had already occurred at least once in the game.