mojira.dev
MC-263065

Jukebox does not play sound when close, if playing started out of range

When a Jukebox starts playing a music disc from out of the players hearing range (65ish blocks away), the music disc cannot be heard when the player moves into the range.

link to video proof: https://drive.google.com/file/d/19jH_nwAKRp8h_IJMjYTUChwvCygyBd2y/view?usp=sharing

How to reproduce: 

  1. place a hopper facing into a jukebox and lock it with a torch.

  2. power the torch off from 70 blocks away

  3. observe that music disc is not playing when you approach the jukebox

Linked issues

Comments 8

I'm disappointed this is a won't fix. It feels as though this decision severely limits the potential of the relatively new feature that is being able to load jukeboxes via hopper. The player can hear a jukebox when they walk out of range and then back in; I would like to see the reasoning behind this decision. 

I'm commenting here to try to bring more attention to this issue. I completely agree with agonzales5071 that this issue severely limits the interaction between redstone and jukeboxes. Frankly, I can't even see much of a reason for redstone to interact with jukeboxes at all if this bug remains. If you have to be relatively close to the jukebox whenever it starts playing, why not just insert the record manually?

Some clarification of the reasoning behind marking this as Won't Fix would be nice.

Feel the same way SamSpooka and agonzales. Really cripples most use cases of the new hopper addition. Criminal won't fix on this one.

Noticed this bug in-game and Im glad to see others have reported it. I'd love to hear the thinking behind not fixing it, are there technical challenges Mojang doesnt want to address right now? This bug is holding back the jukebox from being a really great and fun block, in my opinion

this jukebox bug

was labeled won't fix

for reasons why, we wait

one billion game ticks

I'm also really sad this is a problem, but mainly for another reason: The same applies to custom sounds. If no player would hear it, then the command fails.

And as to answer the Won't Fix, probably because it would create too much lag playing a lot of sound events, although nobody would hear them, and for the blocks, it is exactly 64 blocks, the distance of which you can still hear sounds in the category "record"

But with commands I really don't understand it, there are so many things with commands, that create Lag, so why don't allow this, you can't have radios, or something like this, which just play, and when you're in range, you hear it otherwise not. And then you would have to look yourself to not create too much lag at once. Or maybe just a Force Override

agonzales5071

(Unassigned)

Confirmed

Sound

1.19.4, 1.20 Release Candidate 1, 1.20, 1.20.1

Retrieved