Andrei

Because Mojang devs as programmers are completely understanding things that I described in my reports. All the obstacle is only because these bugreports aren’t currently promoted to them yet

depending* on that guess

Maybe because you are not programmers and don’t see what things are completely clear for programmers, but you don’t promoting bugreports to them because those things aren’t enough clear for you… Maybe. I just guess. And review please my other reports depending, there also more than enough details, but in comments I every time getting canned responses like something is missed, but there nothing, I guarantee

We do not have enough information

Actually you do. My description is easy as 2+2 and self-explaining.

server-ip.com is working while connecting to server via that IP.

server-ip.party is not.

Seems like it was Cloudflare issue, but you’re guys… That’s not an approach. You’re always asking to provide more info even it’s provided on 101%. You’re (moderators) often acting like bots, sorry. That’s not an approach.

That’s the bug.

So real/actual leash wasn’t broken, but sound is infinitely playing crackling

Example of server-side cancellation of entity unleash:

So leash is kept longer than it’s max length (bypassing max leash length limitation), but since Minecraft 1.21.6+ it cause client-side crackling sound caught in loop 😵

Buggy sound name is: entity.leashknot.break (added in Minecraft 1.21.6).

It must play only on actual leash breaking, not if leash breaking was cancelled on server side

You have!

Steps to reproduce:

1. Leash any entity on server

2. On server side deny unleash, so leash will exceed it’s max length so it’s trying to break

3. You will hear leash break sound added in Minecraft 1.21.6+ infinitely, each millisecond - lead part of this sound, so it sounds like a devilish screamer or “nuclear bomb explosion inside infinite loop” x_x 😬 😵‍💫 💀

Sorry. Are you joking? Developers know what I am talking about as "two plus two", just show them the ticket. Steps to reproduce anyway:

1. Open IDE

2. Write code for Minecraft Bedrock server that spawning an entity in world (any kind, no matter). I coded it as server plugin, Minecraft developers can do the same directly in game code of vanilla Minecraft server (Bedrock)

3. Set “no gravity” attribute to it and then set velocity (`entity.setVelocity(vector…)`) to move entity smoothly from point A (entity’s current location) to any point B near (e.g. 3 blocks in any direction)

4. In game (using Bedrock client) you will see that entity wasn’t actually moved from point A to point B (completely wasn’t moved)

I even tried tons alternative workarounds:

• Tried to use teleport instead of setVelocity (doesn’t work too)

• Tried to send “despawn” packet for each block entity and then spawn them (the same block entities) again, but on their new locations (doesn’t work too)

• Tried to use Block Display entities instead of Falling Block entities (doesn’t work too, no any Block Display is actually displayed in game)

• Tried milltion possible combinations that can probably help, but nothing helped at all

I found the same problem discussions in internet:

1. First: https://feedback.minecraft.net/hc/en-us/community/posts/360043329072-Add-falling-block-entity-to-bedrock

2. Second:

   [media: image-20250716-041027.png]

3. Third:

   [media: image-20250716-041252.png]

Java (perfect):

Bedrock (nothing works):

I just setting velocity to falling block entities (which this jump rope consists of).
But on Java it’s work, and on Bedrock it doesn’t.

Seems like on Bedrock those falling blocks having velocity just once, so as you see, they (falling blocks) are moved a little bit, but then stopped. Just visual bug, because Java Edition players see jump rope as working in the same time.

Video from Java I was attached as 2 links in post above,

and this one is video from Bedrock

It’s problem is caused by the new Minecraft sound named entity/leashknot/break invented in 1.21.6. Please mark it as fast-fixeable for developers 🙏🏻

Now I got it. It was not clear when I was filling fields in bug report form, but it became clear after your explanation

Why unreleased versions are even exist then? I was marked them this way with mind. It’s too long to describe my decisions why I labeled my report with both these labels and I’m not from laptop (from mobile phone) now. 1.21.6 means that bug exist in this version (and means that bug persist and not fixed even in latest version). Hotfix in future means that this fix should be made in future (hot fix = in near future, not e.g. in year). I was think so

Hello this is also hapenning to me and idk how to fix this. I got the cape on my bedrock account but it is not moving to my java one…this really is bad…we need a fix pls Mojang! or microsoft…

As far as I can tell, this issue has been resolved on KDE side via better integration of Gnome Keyring:

• https://pointieststick.com/2022/07/09/this-week-in-kde-big-things/

• https://invent.kde.org/frameworks/kwallet/-/merge_requests/11

Ok. Copied description from here into MC-245915 as a separate h3 section in the description.

@ampolive kind of, but it describes summoned entities. This issue is about hostile mobs that spawn naturally, without commands.

Still an issue in 1.18.1:

This problem has been going on for several months, right after the purchase of the license😥

Developers are lazy😡👎