I reported this in another bug report but the mod who answered had a brain fart and forgot which report he was replying to (or read the summary only and none of the message and completely misunderstood). Called it a duplicate of something completely unrelated in any way.
When using xyz coordinates and range the space affected can't be shrunk to 1 block. A 3x3x3 globe is the minimum size. This makes sense if a command block is the center of the globe but not if a specified xyz is.
Comments 11
This is not a feature suggestion. It is a bug report. Being completely unable to sense only 1 block is clearly a bug, as it should be the default behavior.
Just to let you know I found a workaround. I'm sure mojang won't like it. Apparently until this gets fixed people are intentionally causing integer overflows. And yes, it works fine. Using the number 65536 for the range will shrink it to 1 block.
Yeah i'm pretty sure over half the mods here don't bother reading anything past the title, and simply close the issue with a condescending remark. I think they get paid per issue they close, so they simply do not have time to help the average player.
Anyways, this is actually technically not a bug because it works the way it is intended. With range 1, it senses blocks that are 1 away from the center block, making it a 3x3x3 globe. With the way the code is, putting the range as 0 makes it sense nothing. Not sure why a range of 0 isn't allowed, kind of dumb in my opinion, but that's just the way it is.
Glad you found a workaround though, thanks for sharing!
@Nicholas, thank you for the explanation, as it is the justification for closing this report. One thing, however, that you may want to note, is that all the Mods are volunteers. Another thing is that as we often close many issues for the same reasons, we have "standard responses" we typically use. If you find these responses aren't appropriate, please suggest some improvements, as we are always looking to better assist the reporters.
remove the range and it counts it as infinite range (nearest player to that block, no range restriction at all)
"If you find these responses aren't appropriate, please suggest some improvements, as we are always looking to better assist the reporters."
Well there is that map corruption bug that you folks have decided is intended behavior. What do we do in cases like that where the issue being marked "resolved" is obviously BS and it's a catastrophic bug or exploit? One that people could use to nuke other people's maps on multiplayer (they'd have to have enough privileges to use cheat codes so that scenario is unlikely but possible).
My report of it was MC-42539 but it was marked as a dupe of MC-30484
Just to update this was eventually fixed in snapshot 14w03a. Range 0 works now, and range 65536 now actually searches a range of 65536 (owch!). Here's a link to the changelog for that snapshot:
Any chance a mod could change the incorrect resolution. It wasn't invalid, it was a bug and it was resolved in 14w03. I know it's petty of me to want my fixed bug reports to actually list as fixed rather than an incorrect marking of duplicate or invalid from a mod not bothering to read past the title and mismarking it but there you go.
This site is for bug reports only. For feature suggestions or changes please do this on Minecraft Suggestions on Reddit.