Soni L.
- soni
- soni
- America/Sao_Paulo
- Yes
- No
MC-266
Low![[Mojang] Georgii Gavrichev](../../../data/avatars/users/22428.png){kind=small}
Microsoft Windows [Version 6.1.7601]
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode)Microsoft Windows [Version 6.1.7601]
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode)
When blocking with a sword it works, but when sneaking (left shift key by default) it doesn't...
Inconsistency between repeaters and buttons/levers/torches/redstone blocks activating redstone devices
http://imgur.com/a/lyml8
The "original design", when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to always work is by using a sticky piston and a redstone block, and then it always works.
http://imgur.com/a/lyml8
The "original design", when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to
alwayswork is by using a sticky piston and a redstone block, and then it always works.
http://imgur.com/a/lyml8
The "original design", when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to work is by using a sticky piston and a redstone block
, and then it always works.
http://
imgur.com/a/lyml8
The "original design", when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to work is by using a sticky piston and a redstone block.
http://www.minecraftforum.net/topic/2472184-survival-friendly-half-tick-offsetter/
This redstone device, when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to work is by using a sticky piston and a redstone block.
http://www.minecraftforum.net/topic/2472184-survival-friendly-half-tick-offsetter/
This redstone device, when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to work is by using a sticky piston and a redstone block.
Edit2:
The expected output is the repeater line outputting exactly 1 game tick (1/20 of a second) after the comparator goes off, but when activated with repeaters both the comparator and the repeater line go off at the same time...
http://www.minecraftforum.net/topic/2472184-survival-friendly-half-tick-offsetter/
This redstone device, when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to work is by using a sticky piston and a redstone block.
Edit2:
The expected output is the repeater line outputting exactly 1 game tick (1/20 of a second) after the comparator goes off, but when activated with repeaters both the comparator and the repeater line go off at the same time...Edit3:
There's a possibility of this being position/orientation dependent, but I haven't tested that...
http://www.minecraftforum.net/topic/2472184-survival-friendly-half-tick-offsetter/
This redstone device, when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to work is by using a sticky piston and a redstone block.
Edit2:
The expected output is the repeater line outputting exactly 1 game tick (1/20 of a second) after the comparator goes off, but when activated with repeaters both the comparator and the repeater line go off at the same time...Edit3:
There's a possibility of this being position/orientation dependent, but I haven't tested that...Edit4:
(Tested as of 1.8.1-pre3) Reproducing now requires a different design. See attachment.
Windows 7; Java 7 update 45
Windows 7; Java 7 update 45 (up to and including edit 3)
Arch Linux. Oracle JDK 7 update 71. (since edit 4)
http://www.minecraftforum.net/topic/2472184-survival-friendly-half-tick-offsetter/
This redstone device, when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to work is by using a sticky piston and a redstone block.
Edit2:
The expected output is the repeater line outputting exactly 1 game tick (1/20 of a second) after the comparator goes off (as in, turns on), but when activated with repeaters both the comparator and the repeater line go off (turn on) at the same time...Edit3:
There's a possibility of this being position/orientation dependent, but I haven't tested that...Edit4:
(Tested as of 1.8.1-pre3) Reproducing now requires a different design. See attachment.
Inconsistency between repeaters, pistons and buttons/levers/torches/redstone blocks activating redstone devices
http://www.minecraftforum.net/topic/2472184-survival-friendly-half-tick-offsetter/
This redstone device, when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to work is by using a sticky piston and a redstone block.
Edit2:
The expected output is the repeater line outputting exactly 1 game tick (1/20 of a second) after the comparator goes off (as in, turns on), but when activated with repeaters both the comparator and the repeater line go off (turn on) at the same time...Edit3:
There's a possibility of this being position/orientation dependent, but I haven't tested that...Edit4:
(Tested as of 1.8.1-pre3) Reproducing now requires a different design. See attachment.Edit5:
Sticky pistons + redstone block produce yet another different behaviour.
http://www.minecraftforum.net/topic/2472184-survival-friendly-half-tick-offsetter/
This redstone device, when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to work is by using a sticky piston and a redstone block.
Edit2:
The expected output is the repeater line outputting exactly 1 game tick (1/20 of a second) after the comparator goes off (as in, turns on), but when activated with repeaters both the comparator and the repeater line go off (turn on) at the same time...Edit3:
There's a possibility of this being position/orientation dependent, but I haven't tested that...Edit4:
(Tested as of 1.8.1-pre3) Reproducing now requires a different design. See attachment.Edit5:
Sticky pistons + redstone block produce yet another different (but related) behaviour.
http://www.minecraftforum.net/topic/2472184-survival-friendly-half-tick-offsetter/
This redstone device, when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to work is by using a sticky piston and a redstone block.
Edit2:
The expected output is the repeater line outputting exactly 1 game tick (1/20 of a second) after the comparator goes off (as in, turns on), but when activated with repeaters both the comparator and the repeater line go off (turn on) at the same time...Edit3:
There's a possibility of this being position/orientation dependent, but I haven't tested that...Edit4:
(Tested as of 1.8.1-pre3) Reproducing now requires a different design. See attachment.Edit5:
Sticky pistons + redstone block seem to produce yet another different (but related) behaviour.
Inconsistency between repeaters, pistonsand buttons/levers/torches/redstone blocks activating redstone devicesInconsistency between repeaters and buttons/levers/torches/redstone blocks/pistons activating redstone devices
http://www.minecraftforum.net/topic/2472184-survival-friendly-half-tick-offsetter/
This redstone device, when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.Edit: When activated by powering/unpowering a torch it also fails. The only way for it to work is by using a sticky piston and a redstone block.
Edit2:
The expected output is the repeater line outputting exactly 1 game tick (1/20 of a second) after the comparator goes off (as in, turns on), but when activated with repeaters both the comparator and the repeater line go off (turn on) at the same time...Edit3:
There's a possibility of this being position/orientation dependent, but I haven't tested that...Edit4:
(Tested as of 1.8.1-pre3) Reproducing now requires a different design. See attachment.Edit5:
Sticky pistons + redstone block seem to produce yet another different (but related) behaviour.
Inconsistency between repeaters/activated torches and buttons/levers/player-placed torches/redstone blocks/pistons activating redstone devices
Block entities become stuck when reloadingaworldBlock entities in player's chunk become stuck when reloading the world
On reloading the world, block entities become "stuck":
- Chests don't play sound when opening/closing
- Furnaces stop working
- Probably other block entities too
On reloading the world, block entities become "stuck":
- Chests don't play sound when opening/closing
- Furnaces stop working
- Probably other block entities too
This only happens if you're on the same chunk as them. Going to another chunk and reloading fixes it, until you reload on the same chunk as them again.
On reloading the world, block entities become "stuck":
- Chests don't play sound when opening/closing
- Furnaces stop working
- Probably other block entities too
This only happens if you're on the same chunk as them. Going to another chunk and reloading fixes it, until you reload on the same chunk as them again.
http://www.minecraftforum.net/topic/2472184-survival-friendly-half-tick-offsetter/
This redstone device, when activated with repeaters, will not produce the expected output. When activated with torches, buttons, redstone blocks, levers, etc it works just fine.
Edit: When activated by powering/unpowering a torch it also fails. The only way for it to work is by using a sticky piston and a redstone block.
Edit2:
The expected output is the repeater line outputting exactly 1 game tick (1/20 of a second) after the comparator goes off (as in, turns on), but when activated with repeaters both the comparator and the repeater line go off (turn on) at the same time...
Edit3:
There's a possibility of this being position/orientation dependent, but I haven't tested that...
Edit4:
(Tested as of 1.8.1-pre3) Reproducing now requires a different design. See attachment.
I took the screenshot in MC 1.2.5, but I did test it in MC 1.4.2
Because it's useful for PVP traps, and nobody knows about it.
Eh, true...
... Why do people want this fixed?
This bug is completely unrelated to MC-8184, this bug is about block updates not causing redstone updates, the other bug is about redstone updates not updating dispensers/note blocks/TNT.
Eh... Sometimes I feel like Minecraft needs a wrench-like thingy... :/
Sneaking with a sword doesn't show bobbing either...
Well
MC-28346doesn't include an in-depth fix for the bug...That wouldn't explain why it works with user input and pistons but not repeaters and other "automated" inputs...
This is what the design looks like without all the additional repeaters:
http://www.minecraftforum.net/topic/2472184-survival-friendly-half-tick-offsetter/
I think nobody ever gets the annoying advanced redstone bugs I report... too advanced maybe? :/
New design (as of 1.8.1-pre3) for reproducing.
Attached "different" design. One of the levers activates the last piston, the other doesn't.
This seems to have been fixed sometime between 14w31a and 1.8.1-pre3.
That doesn't explain why a repeater chain keeps the proper timing offsets
Stick 2 repeater chains on the 2 outputs, all repeaters set to 1 tick, then do a slow motion video and you'll see one chain firing, then a delay, then the other, then another delay, etc so it can't be that.
eh guess I'll have to do this myself :/
How do you explain this: http://youtu.be/TKSiNOuyYlw
Because pistons are buggy (hint: there are more piston-related bugs than anything else)
It's the behaviour when repeaters activate pistons that is wrong, stop trying to change that, I want my 20 TPS songs to be playable in survival Minecraft! (without the use of command blocks)
Why should they make no sound when placed? All blocks currently make sound when placed, even lilypads. (but only when they're placed on the side of a block)
The levers attached to the piston with a redstone block activate the circuit the same as the bottom-most lever. From the repeater attached to that piston, the only lever which doesn't activate the circuit as expected is the one above the repeater (or, more specifically, the one east of the repeater).
This proves that the issue is specifically with repeaters. Pistons can be used to correct the repeater.
Ok so I figured out why it happens.
It has to do with this method in WorldServer:
I'm not entirely sure how it happens, but repeaters, pistons, note blocks and a few other blocks use them, and they are processed after every other processing that happens in the world, except entities and tile entities (which are also used by pistons, and the player is an entity).
I'm guessing it has something to do with entities and tile entities updating after block event processing. I'm guessing processing block events after entities and tile entities would fix it.
Doesn't explain pistons with a redstone block acting like players.
Hmm... OH!
Ok I didn't see that before. Player updates are actually done before block event processing. The fix might be to actually move player updates to after block event processing (together with entity and tile entity updates).
So currently you have player update -> redstone update -> block event queued -> block event processed, which makes it happen in the same tick. But for tile entity updates it only happens on the next tick. I think.
My current system setup is not capable of running multiple X sessions. Means I can no longer test this.
The code-accurate description of the issue is that light-emitting blocks let light through, even if they're solid and their light level is much less than the light they're letting through.
MC-102162is just a side-effect of the lighting update code not handling light-emitting blocks which emit less light than their in-world value. In other words,MC-102162is caused by this issue.Fixing
MC-102162doesn't fix this issue. On the other hand, fixing this issue would hide (but not technically fix)MC-102162.The same applies to sunlight, as both sunlight and block light share most of the update code (NB: sunlight code also includes direct downwards propagation, which is the part that does not suffer from this issue - the solid blocks listed in this issue stop downwards propagation - however see
MC-3961). The part that is shared uses a simple value to control which lightmap to access.It's not just furnaces - chests stop making sound, and you get... "interesting" behaviour if you replace one of those "broken" furnaces with a chest.
MC-144603MC-144603Try reloading the world with the player in another chunk. If it works again, it has everything to do with that bug.
I'd expect the lava oceans of the nether to be water oceans in the overworld using the Caves buffet. so I don't think it makes sense.
both the reddit and the feedback website also consider it invalid, so if it's not a bug nor is it a feature request, wtf is it?