eSonOfAnder

Never seen this mechanism here, but based on the video it is nowhere near the fastest transportation. Even a normal ice road is faster than what is shown in the video. Packed Ice and Blue Ice are even faster. Also not sure what “technical difficulty” you’re referring to - it’s just a bunch of soul sand and ladders / fence gates. Also there is nothing “automated” here at all.

So while this mechanic is interesting, I expect the problem here relates to the ladders and how the boat now interacts with small variations in terrain heights.

As I said in my original post, this happens 100% on Chrome and 50%+ on Firefox, so it is not just a Chrome issue It took me three tries just now on Chrome on mobile to get it to work, so this is not a matter of a plugin/extension which would ALSO be disabled in an incognito window which I already explained shows the same behavior. I have literally no clue how you are getting it to work when it fails across two Windows 10/11 desktop systems, two Windows 10/11 laptops, a Chromebook, and an Android phone here, ALL with the exact same symptoms.

Just to add another detail to this issue - the screenshot function, itself, does work if you hit Esc and use the Screenshot icon in the lower left portion of the screen. It is just the hotkey that is not actually connected to the action. Have not tested the 1.21.60 Preview to validate JervieA20's comment.

Lumping all of the chunk loading and sound loading issues across all Bedrock platforms seems counterproductive, both from a bug report perspective (there is no longer one bug being reported and counted as part of this bug), as well as from a triage perspective on the Mojang side (how can you possibly try to reproduce something like this that has taken on a life of its own and is now so broad a topic as to be meaningless?).

There are at least four separate bugs identified just within the visible handful of comments shown when you first open this ticket:

• Chunk loading issues - this is being reported inconsistently across multiple platforms in different reported scenarios. My personal experience, and what I was redirected here for, is on Switch, where chunk loading issues happen 100% of the time, regardless of size of the world, without requiring the player to be moving faster than on foot sprinting, even with render distance set at the lowest setting. This segment alone needs to be broken up into individual bugs for it to make any level of sense or turn into an actionable bug.

• Performance / frame rate issues - again, being reported across multiple platforms, but seems concentrated on Switch. I have not experienced this issue at all, just the chunk loading issue, so again, lumping in my report with this massive, unwieldy thing is both counterproductive, and inappropriate.

• Skin and Marketplace content unavailable / non-functional - again seemingly focused on Switch, but the skin loading issue has been a known problem across all Bedrock platforms for years (known issue to players, at least - all tickets I am aware of about this have been closed as either "cannot repro" or "fixed" in spite of the constant flood of players experiencing the issue).

• Sound loading lag - I've experienced this on Xbox One (original Xbox One, and Xbox One X), PC, and Switch. Sounds will just not play, but get queued and eventually the whole queue plays at once, and sometimes it stays caught up, but frequently does not. Does not seem to be worse on any particular one of the platforms I have available to me. Sometimes sounds just don't play at all, and aren't even queued - just skips them entirely. This is all sounds, both in game sounds and UI sounds, both while a world is loaded and within the system menus before or after a world has been loaded.

I am quite sure if I dig further through the comments, there will be even more issues being lumped in here by having their tickets closed as duplicates of this one massive, "the game is broken" ticket.

That might be the way it is supposed to work, but in practice, that is not what is happening. As I described earlier in the ticket, deep dark biome generation is not behaving as described. Instead it is behaving as follows:

if (biome == (stony peaks || jagged peaks)) && y < 0

 set biome = deep dark

There may be other mountain biomes where this is happening, but these are the two that I have observed it happening in.

Please see your own definition of the priority of this bug. There is NO WORKAROUND for this, therefore "Normal" is not the correct priority for it. Please adjust as actually appropriate, and better yet, address the bug here so that you can close the ticket.

The web feedback tool is 100% broken, and apparently has been for over a month based on when this ticket was opened, and yet the priority on this remains at Normal and. O action has been taken yet? Says a lot about just how little Mojang actually cares about player feedback.

No, this is not a duplicate of that issue, though it is related. The major bug here is how the Deep Dark biome generates and replaces all of some of the overworld mountain biomes at a certain Y level. This is not how the biome was described to work, instead it was supposed to work the same as the Lush Caves and Dripstone Caves where specific 3-dimensional blobs of underground areas would have a new biome override, but this is not how the Deep Dark biome is behaving. The knock-on (and arguably the more impactful) effect is that it breaks rare ore generation also. I am updating the title of this bug to reflect the underlying bug better.

No, at no point was I offline during this process. This is a similar bug, but not identical to the linked one. I do not see the "Failed to load character" message at all on either platform, and this issue shows up directly on the first client with no change in platform needed. (I have encountered the linked bug, also, and mostly seem to experience that one on the Switch platform.)

I would expect changes to an offline profile to behave the way you are describing, but what I am seeing is the exact opposite of that. At game launch, the online profile is loaded properly with the skins created as expected. After saving and exiting from the game session and returning to the main menu, not only has the current skin been reverted to a default state, so have all other created skins on the account. And then, just to prove that this has all been done while online, those reverted skins are saved to the online account and can be seen as the "new" reverted to default state on all other platforms, as opposed to simply showing the "Unable to load character" error message if it were experiencing network issues for whatever reason.

This bug actually fully reverts character skins and saves them to the online account, without the player's action or permission.

Obviously some developer added this intentionally for it to be like this - that does not happen accidentally or through some interaction with unrelated code - however this is absolutely a bug. There is no other precedent for this type of restriction for a recipe (the closest similarity is the boat recipe unlocking when the player enters water for the first time). It is also, more importantly, completely inconsistent with all of the other rail recipes - none of which require the player to have had a minecart in their inventory to unlock. It makes NO sense for the player to have Powered Rails and Detector Rails unlocked but not the basic Rails recipe. And just so we are clear, the solution here is NOT to add the minecart requirement to the other rail recipes.

This issue happens very frequently if you continue holding down the activate button/key while eating, at least on PC.

Repro steps:

1. Have some non-zero number of empty hunger bars

2. Have a stack of more than one of a type of food that will completely restore the hunger bar selected

3. Hold down right click to eat

4. Continue to hold down the button.

Expected behavior:

• Character stops eating after the first piece of food is consumed and the hunger bar is filled

Observed behavior:

• Character will eat at least one more food item after the hunger bar has been filled. I have observed up to two more food items consumed after the bar is filled, but rarely. It usually stops at one additional.

There are other bugs being closed as duplicates of this one that accurately describe the issue correctly and are NOT actually duplicates of this, so either the description of this bug needs to be updated, or you need to STOP CLOSING TICKETS THAT AREN'T ACTUALLY DUPLICATES.

The actual issue:

Nether based woods, both Crimson and Warped, will catch fire from things like lava which is incorrect. Both wood types are supposed to be immune from catching fire as they are nether based blocks. Ignore the lighting of the blocks using a flint and steel, that has nothing to do with the ACTUAL big here.

And yes, I DID open this as a separate bug, but you closed it as a duplicate of this one. Several other people have as well of you would look at the list of supposed "duplicate" bugs, NONE OF WHICH talk about what this ticket was originally opened for.

Found within a few minutes of looking in each of these two worlds in 21w44a:

World seed: 185740704

Monuments at:

• 1758, -334

• 2242, -308

• 2656, -274

Edit: Searched this world a bit more using the grid described below, and found two more. Looks like, as mentioned below, things stopping the spawning include biome change, and depth of ocean available, but that's it.

• 2845, -911

• 3393, -1344

World seed: -480661120

Monuments at:

• 94, -1809

• 64, -2352

• 206, -2960

• 128, -3263

• 223, -3758

• 832, -2449

• 736, -1744

• 625. -1280

• 1214, -1889

• 1152, -2320

They appear to be generating in a rough grid along X/Z axes; as long as the biome remains an ocean, and it is deep enough for the structure to generate, you get one roughly every 500 - 600 blocks, with a bit of noise variations one way or the other. At least that's what it looks like.

I had found the first five monuments in the second world seed listed above in my original casual browsing of the seed - I then went back and did a grid approach, and found the rest of them simply by flying one of the cardinal directions from an existing monument.

I cannot give you screenshots because this was on a server and I did not take any. If the items were just invisible, I should still have picked them up because they existed. I did try logging out and back in to the server, but nothing reappeared. At least one other person from that server has stated that they've seen the exact same behavior multiple times. For this and many other reasons, I am unwilling to return to the game in its current broken state.

As I am not the original reporter, I cannot add the 1.17 versions to the affected list, but they should be added here.

This is still an issue on Xbox One. Game bootup/load times are extremely excessive, and take longer than most other significantly larger games. Happens on both an original Xbox One and an Xbox One X - there is no difference in load times; they are both painfully slow to load. Once in game, things are fine, but it takes on the order of minutes, multiple, to go from hitting the A button to launch Minecraft until the main menu is available.

Experiencing what appears to be a variation on this issue:

(This is in a naturally generated survival village)

• Trade with a farmer villager to get them to level 2

• Wait for a day/night cycle

• Return to the same villager, and they have changed their level one trades - they remain level 2

• In this example, the villager's level one trades were to buy beetroot and sell bread; after the day/night cycle, the level one trades are now to buy potatoes and sell bread

Between this, the bug that allows villagers to attach to workstations they cannot pathfind to, and the bug that requires pumpkins be placed with the player facing north before farmers will buy them, villages are not valuable or reliable resources in Bedrock as it stands currently.

This is not isolated to a specific platform; this will occur on all Bedrock platforms - iOS, Android, Win 10, Xbox, PlayStation, Switch.

Edit: Would also recommend updating the title of this ticket to specifically mention the player suffocation as that is the much more severe effect of this bug.

MC-160119 - this bug was never fixed; would be nice if this would actually get some attention and be FULLY fixed instead of just half-arsed.

This issue has never been fixed; I cannot find where I included videos showing this issue in action over a year ago, but can also confirm this is still a bug that has never been addressed (in spite of Mojang claiming that it has).

For additional reference, see the farm design shown here: https://www.youtube.com/watch?v=mLEdAnYjoL4

Specific timestamp to start watching for this issue: https://youtu.be/mLEdAnYjoL4?t=1148

This is an exceptionally easy bug to reproduce, would be nice if this would actually get FULLY fixed instead of just slap dashed and then ignored again.