[MC-277681] Guardian beam attack sound stalls when guardian is unloaded

When a guardian is readying its laser and you move so that it is outside your simulation distance, if it hasn't fired yet, it will continue playing the sound for charging its laser.

Steps to reproduce:

lower your simulation distance to 5 chunks, but have your entity distance and render distance greater than that.
spawn a guardian near a squid (the guardian will target the squid)
travel far enough away for the guardian to still be rendered (within entity distance), but not be simulated (outside simulation distance)

Observed result:

Guardian laser sound will continue playing until the guardian is within simulation distance or unrendered.

Expected result:

Unrendered entities should stop playing sounds. (Guardians are easiest to observe this with)

Related issues

duplicates

MC-57057 Guardian laser attack sound ignores distance

Comments

[Mod] Jingy 2024-10-22T19:43:42Z

We do not have enough information to reproduce this issue.

Please include the following information to help us understand your problem:

Steps to Reproduce:
1. (Explain what needs to be done for the issue to happen)
2.
3.
Observed Results:
(Briefly describe what happens)
Expected Results:
(Briefly describe what should happen)

Please also attach any needed commands, add-ons/behavior packs, data packs, resource packs, screenshots, videos, or worlds needed to help reproduce this issue.

Refer to the Bug Tracker Guidelines for more information about how to write helpful bug reports. Bug reports with insufficient information may be closed as Incomplete.

_{This issue is being temporarily resolved as}_{Awaiting Response}_{. Once the requested information has been delivered, the report will be reopened automatically.}

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

[Mod] Jingy 2024-10-23T02:30:46Z

Thank you for your report!
We're tracking this issue in MC-57057, so this ticket is being resolved and linked as a duplicate.

If you would like to add a vote and any extra information to the main ticket it would be appreciated.

If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.