Affects Version/s: 18.104.22.168 Beta, 22.214.171.124 Beta, 126.96.36.199 Beta, 1.14.20 Hotfix, 188.8.131.52 Beta, 184.108.40.206 Beta, 220.127.116.11 Beta, 18.104.22.168 Beta, 1.13.3, 1.13.2, 22.214.171.124 Beta, 1.13.1, 1.14.1 Hotfix, 126.96.36.199 Beta, 188.8.131.52 Beta, 184.108.40.206 Beta, 220.127.116.11 Beta, 18.104.22.168 Beta, 22.214.171.124 Beta, 126.96.36.199 Beta, 188.8.131.52 Beta, 184.108.40.206 Beta, 220.127.116.11 Beta, 18.104.22.168 Beta, 22.214.171.124 Beta, 126.96.36.199 Beta, 188.8.131.52 Beta, 1.13.0, 184.108.40.206 Beta, 1.14.0
Fix Version/s: 220.127.116.11 Beta
Platform:Windows 10 - PC
The bug happens when exiting the world and loading the world again.
Basically, before exiting the world, the barrel can receive a redstone signal and give and output (just like a regular block).
But - if you will exit the world and then relogging -> the barrel stop working which means that redstone don't pass through it at that point!
See the video if it wasn't clear. Ask me anything you want.
By PHO: Confirmed to be affecting 1.14.0 (iOS).
Barrels behaves like a solid opaque block until you relog. That is,
- Strongly powered Barrels can power adjacent redstone dust.
- Weakly powered Barrels can activate adjacent redstone components.
- Redstone torches attached to a side of a Barrel can negate its output based on the powered state of the Barrel.
- Repeaters can receive power from weakly powered Barrels.
But once you relog, Barrels lose all of these properties and starts behaving just like Glass blocks. Breaking and re-placing them will recover their initial functionalities.