Dawson81702

Beforehand, might I add that the crash had reset my options.txt file, starting me at the "Tutorial" (press WASD, hotkeys changed, options changed, and reset my Advancements)

Though a crash report is missing, all that was available was a 0kb crash txt; A massive launcher log was made at the point of incidence.

the launcher_log.txt log with a whopping near 1,000,000 (Million) lines, at 253 Mebibytes. contains only the point of error that happened around 4am PST on July 1st.

Since due to the sheer size of the txt file, I have provided a download link through Google Drive.

Here is the link to launcher_log.txt (265 MB)

https://drive.google.com/file/d/1TGozjYlrLFfqkJtzmANgVkdHrAg3wDEH/view?usp=sharing

Can confirm in latest PS4 Bedrock update, long worked on World decided it wanted to corrupt most likely Autosave. Unfixable and had to delete losing all the progress that was made. It’s happened to me in the past as well. When will Mojang focus on more important things like preventing these Game-Breaking glitches.

Confirmed not fixed for 1.16.5, happened to me for a while. Can't reproduce, Fixed by hitting horse, but then created another "Return" point.

@GoldenHelmet I didn't necessarily mean that it was a magma block trap what I meant was there is a hole in the opposite corner of where they are trying to pathfind to. And blazes are resistant to fire damage so It would not damage them and they wouldn't need to avoid it. 

There is North West Bias, but the Blazes will not Pathfind onto my magma block trap that so happened to be in the South-East corner and just go straight to the north and west sides. I checked today and its still the same situation. I had it until the room was full and the blazes were in a triangle heading to the north-west corner. It has totally broken my Farm which sucks.

Current: 1.16.0: The pathfinding did fix from the last update for a bit but now it's totally broken again.