MC-41006Comparator same distance, different results
Linked Issues
is duplicated by2
relates to2
Low
Normal
![[Mod] Skylinerw](../../../data/assets/gravatar/skylinerw.png){kind=small}
Created Issue:
comparator same distance different results
comparator on the same distance give different end results. see picture below. tested some different setups all more whit one comparator seem to have major bugs in the signals. if the picture isn't clear enough ill that will try to explain it more.
Environment
tested in a creative single player world in 13w48b
Linked Issues
is cloned by1
TRASH-5894
Attachments1
comparator on the same distance give different end results. see picture below. tested some different setups all more whit one comparator seem to have major bugs in the signals. if the picture isn't clear enough ill tha
twill try to explain it more.comparator on the same distance give different end results. see picture below. tested some different setups all more whit one comparator seem to have major bugs in the signals. if the picture isn't clear enough ill than will try to explain it more.
comparator on the same distance give different end results. see picture below. tested some different setups all more
whitone comparator seem to have major bugs in the signals. if the picture isn't clear enough ill than will try to explain it more.comparator on the same distance give different end results. see picture below. tested some different setups all more than one comparator seem to have major bugs in the signals. if the picture isn't clear enough ill than will try to explain it more.
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
is cloned by
is cloned by
your perfectly clear =D
Yes the Status still stands on Open.
thank you for confirming this bug I placed yesterday. I were just mad ad your comment "Please do not clone your own reports." as there were not looked into it yet (or so is seems)
ps. I do see the "Confirmation Status: Confirmed" (just now)
tested in a creative single player world in 13w48b still bugs in 14w11b
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
is duplicated by
tested in a creative single player world in 13w48b still bugs in 14w11b, update tested in
tested in acreative single player world in 13w48b still bugs in 14w11b, update tested increative single player world in 13w48b still bugs in 14w11b, update tested in 1.8.1-pre3 bugs are still there.
comparator on the same distance give different end results. see picture below. tested some different setups all more than one comparator seem to have major bugs in the signals. if the picture isn't clear enough ask me and ill than will try to explain it more.
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
15w49b/vanilla
creative single
player worldin 13w48b still bugs in 14w11b, update tested in 1.8.1-pre3 bugs are still there.creative and survival, single-player world: vanilla
creative and survival, single-player world: vanilla
creative and survival, single-player world: vanilla
All minecraft versions from: 26/Oct/2014 till far into the future !!
2013
2014
2015
creative and survival, single-player world: vanilla
All minecraft versions from: 26/Oct/2014till far into the future !!
2013
2014
2015creative and survival, single-player world: vanilla
All minecraft versions from: 27/Nov/2013 till far into the future !!
also affects minecraft versions from the years:
2013
2014
2015
2016
2017
2018
creative and survival, single-player world: vanilla
All minecraft versions from: 27/Nov/2013 till far into the future !!
also affects minecraft versions from the years:
2013
2014
2015
2016
2017
2018
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
Thank you for reporting the bug.
Please be nice to our volunteers as it would sadden me to fulfill a possible future request to restrict your access to the bugtracker if you continue to behave like you are doing currently.
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
comparator on the same distance give different end results.see picture below.tested some different setups all more than one comparator seem to have major bugs in the signals.if the picture isn't clear enough ask me andill than willtry to explain it more.
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
relates to
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
duplicated by MC-41006
a comparator clock will not update a comparator except at the moment it is placed and the comparator will remain in a powered or unpowered state (depending on the signal it receives at the moment it is placed) unless another comparator is placed directly in front of it at which point it will update as normal but the last comparator in the chain will not update.
unlike the similar effect with repeaters which due to applying to the last repeater in a chain of 2 or more can be worked around by placing a block between the repeaters, this effect applies to even single comparators and is exclusive to 1.14
Duplicate of MC-41006
Please do not clone your own reports.
wow a comment ever looked in to the Bug ?
What I can tell you is that I have confirmed the bug (though it has already been marked as confirmed). I do not work for Mojang, so I couldn't tell you if the bug has been looked into. Do not expect to receive regular updates on the issue. When the issue is fixed, it will be resolved as such (and you should be notified of this).
do you also notice a big drop in FPS if you use a comparator as a clock ?? (GTX 670 FTX)
That is understandable. No I do not notice a drop in fps. Keep in mind that this website is intended to be used strictly as a bug tracker. Do not expect forum-like behaviour with your reports. You will not necessarily receive any notification that the bug is being looked at or worked on. Also, try to keep comments relevant to the bug itself (this applies to all reports). I hope I am not sounding rude in any way, but I don't want you to have certain expectations or get the wrong idea.
michael: In that case, thats a clone of
MC-51102...And by the way, comperators and any other redstone devices lagg, and there isn't much we can do about it.
And comperator clocks work from the side:
Where the number is the redstone power
Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Yes the Bug is still there in 1.8.1-pre3/vanilla, Will it ever be fixed ?
The left side (south side) stays ON
The top side (west side) stays ON but on power level 1 (only 1 redstone dust will go on and sty on)
The right (north side) go's ON and OFF at the alternated current of the original input.
see picture: http://www.server075.com/Minecraft_bugs/Untitled.gif
ps, I tried my best to explain it as clear as possible I know your people are not willing or that smart to test it your self, that's why I even added a picture for you that's a .gif so you can see it move =O
I'm currently reviewing around 4000 bug reports. I cannot test each one of them.
Status: Resolved is not TRUE
Maybe you shut start by doing 1 bug at the time.
You are the person that reported the bug, it is your job to keep it up to date. I don't expect you to test it in every single Snapshot, but maybe at least for the big versions. My, by the way 100% voluntary, job is to keep it organized, and to check if new tickets are valid or not, test old tickets if they are still valid or tell the reporter to update it. Don't expect to just put up a report, and everything else will be done by someone else.
Is this still an issue in the current Minecraft Snapshot 15w49b or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Man o man what kind of people do i do this for, they dont even take the the them self to look if they ever fixed the bug.
[mod] Kumasasa it took me les time to go into minecraft and see if its still a issue, than to post a command here.
So i hoop you read all the text so i can make it appear there for you to read if its fixed or not but for you to reset the Status to Resolved even whitout looking your self is just lazy if this is the best way for you to resolf problems and bugs than good luck to you. even when the post is from Oct the 14 at 2:29 PM. and then reposted a even beter picture for that next major update Nov the 13 at 8:28 AM. and so today agan whit a boring text inbetween that i hope you all read 2x just to see if you mist someting like that iam from holland and realy dont give a F... about your well spend time on here being the best that you can as i can see now even more clear than bevore the hole posting of bugs and issue`s is probaly false like [mod] Galaxy told me: "You are the person that reported the bug, it is your job to keep it up to date. I don't expect you to test it in every single Snapshot, but maybe at least for the big versions. My, by the way 100% voluntary, job is to keep it organized, and to check if new tickets are valid or not, test old tickets if they are still valid or tell the reporter to update it. Don't expect to just put up a report, and everything else will be done by someone else." just do your work and ill do mine whits shud be Playing the game. so for now the bug issnt fixed and just to mess whit you some more a storry after the fact. If you dont test the issue`s your self there is no confurmation that it is a issue at all. Greeting server075 http://www.skyblock.nl/
Oh, excuse us for not testing every single bug ourselves. If you don't keep your bugs updated it's very hard to keep track of them.
Maybe that's because you chose to go off on a rant instead of simply updating the list of affected versions
[Mod] redstonehelper your exuse is worthless just like you, the bug were tested and confirmed.
First time reported this bug 2 years agow !! on this same page.
Also added the up coming years for you, added: 2016, 2017, 2018
to update all the bug`s (as are in minecraft now) is not productive at all;
lots of people would update this page just for the reason that NO-ONE is looking in to them.
>>> When a bug issnt fixed it will probaly be there in the next update! <<<
There are a lot of bugs that are inexplicably fixed without anybody knowing because people, such as yourself, do not update the affected versions of their own report and nobody else is following the report closely enough to do so otherwise. A bug could be fixed without it intending to be, and reports concerning it would go unnoticed.
Mojang is not omniscient to the 93,000+ (and growing) total reports on the tracker, and it is unreasonable to expect voluntary moderators to be as well. Moderators, as was already disclosed to you in 2013, again in 2014, and now again in 2015, are meant to clean up reports, not assign themselves as the reporter to every single report and update every single non-duplicate report every single time an update rolls out on top of handling every single new report. You need to understand that the role the moderators play is not the role you want them to play.
If you want them to give the attention to every single report in the way that you want them to give attention to your own report, then I'm afraid to say that it's simply impossible. The number of reports will always increase. How would you reasonably ask them to cycle through 300,000 reports every snapshot week in a few years from now? There are too many reports to babysit for free already. Why do you not volunteer and attempt to perform what you're asking, if you're so concerned about it?
If your report didn't hold any attention since 2014 from Mojang, moderators, or other users (including from yourself), it is likely a very low priority bug and is not of any urgency to be aware of, and even less urgency to harass the moderators over. At the very least you could try keeping your 1 open report up-to-date. If you don't think you can do that, then you can relinquish ownership of the report to somebody else and not have to worry about it anymore. I will take it off your hands myself if you'd prefer.
Relates to MC-11193
One day, the dog named John walked over the street.
Suddenly, a pink car with three legs ran over the street. It stopped
and asked for the 5`th session of Friends, but John told that it wasn`t made yet.
The car was angry, and spitted cacodemons out his two mouths.
The cacodemons duplicated each other, and ate up all
the Scooby-snacks. The old lady shouted at Pikachu, and fired
a missile at him. Pikachu evolved into Weedle, and throwed a
burning banana at the car. The banana got angry, and tried to
rule the world. John told the banana that MTV ruled the world,
and ate him. The banana tasted old shoes, wich was not so weird,
because it was a super sayajin. The green pig with the bell,
ran towards the car, and exploded like a sheep.
Suddenly, the car started an earthquake, and the whole world turned
into a ice cream. The orcs started an revenge on Donald Duck, and
turned him to a pink bear. The old lady advanced into level 10, and
turned into a Fire Demon. The fire demon burned down all mushrooms,
(which was the houses on the planet) and fried all flying carrots.
A pointless story...
Didn't read the story, assuming it meant "I relinquish ownership of this report". Reporter changed to [Mod] Skylinerw.
Taking credit for work you didn't do?
Thank you for reporting the bug.
Please be nice to our volunteers as it would sadden me to fulfill a possible future request to restrict your access to the bugtracker if you continue to behave like you are doing currently.
No no no Thank you,
For all that you do.
sigh... And I feel guilty when i make duplication/invalid report that mod must close it because i didn't find original one.
Dear michael,
bug tracker is not for you or someone. It is for community to make such a great game like Minecraft even better. If you want any bug to be fixed, report it and keep up to date. Some bugs are not easy to reproduce, requires sometimes half an hour to get single reproduction (eg
MC-89064), but if you want anything to be fixed, you need to test itevery so often, because mods do not have enough time for it. They have got their lives. I also want some bugs to be fixed, some of them are not reported by me, but i gave them vote and do test them again and again, if noone else remember to do this.Can confirm for 1.12
Confirmed for 1.13.1.
Confirmed in 1.15.2 and 20w20b.
Can confirm in 20w51a.
Can confirm in 21w05b.