Hess
- _JessE
- JIRAUSER674451
- Europe/London
- Yes
- No
When a container is behind a comparator, it won't receive signals from anything except a container.
T
his also happens weirdly with trapped chestssince they're containers but they give off a signal when opened. Because they're containers, opening them will not power a comparator directlySteps to reproduce:
- Place down a comparator
- Place a
blockbehind the comparatorPlace a redstone torch under that block- And place a container behind the block
Expected results:
Comparator
turns on and gives off power
Observed results:
Comparator stays off
When a container is behind a comparator, it won't receive signals from anything except a container. Now this may be working as intended(not sure if it is) but it affects trapped chests weirdly
Trapped chests are containers but they give off a signal when opened. Because they're containers, opening them will not power a comparator directly
Steps to reproduce:
- Place down a comparator
- Place a trapped chest behind the comparator
- Open the trapped chest
Expected results:
Comparator activates
Observed results:
Comparator stays off
Comparators have their signals cut off by containers when they shouldn't
When a container is behind a comparator, it won't receive signals from anything except
acontainer. Now this may be working as intended(not sure if it is) but it affects trapped chests weirdlyTrapped chests are containers but they give off a signal when opened. Because they're containers, opening them will not power a comparator directly
Steps to reproduce:
- Place down a comparator
- Place a trapped chest behind the comparator
- Open the trapped chest
Expected results:
Comparator activates
Observed results:
Comparator stays off
When a container is behind a comparator, it won't receive signals from anything except the container. Now this may be working as intended(not sure if it is) but it affects trapped chests weirdly
Trapped chests are containers but they give off a signal when opened. Because they're containers, opening them will not power a comparator directly
Steps to reproduce:
- Place down a comparator
- Place a trapped chest behind the comparator
- Open the trapped chest
Expected results:
Comparator activates
Observed results:
Comparator stays off
When a container is behind a comparator, it won't receive signals from anything except the container. Now this may be working as intended(not sure if it is) but it affects trapped chests weirdly
Trapped chests are containers but they give off a signal when opened. Because they're containers, opening them will not power a comparator directly
Steps to reproduce:
- Place down a comparator
- Place a trapped chest behind the comparator
- Open the trapped chest
Expected results:
Comparator activates
Observed results:
Comparator stays off
When a container is behind a comparator, it won't receive signals from anything except the container. Now this may be working as intended(not sure if it is) but it affects trapped chests weirdly
Trapped chests are containers but they give off a signal when opened. Because they're containers, opening them will not power a comparator directly
Steps to reproduce:
- Place down a comparator
- Place a trapped chest behind the comparator
- Open the trapped chest
Expected results:
Comparator activates
Observed results:
Comparator stays off
Please check the video below and all the attachments
When a container is behind a comparator, it won't receive signals from anything except the container. Now this may be working as intended(not sure if it is) but it affects trapped chests weirdly
Trapped chests
are containers but they give off a signal when opened. Because they're containers, opening them will not poweracomparatordirectlySteps to reproduce:
- Place down a
comparator- Place
a trapped chest behind the comparator- Open the trapped chest
Expected results:
Comparator activates
Observed results:
Comparator
stays off
Please check the video below and allthe attachmentsTrapped chests don't power comparators correctly
Steps to reproduce:
- Place down a trapped chest
- Place redstone dust next to it
- Add a comparator which would be activated by the dust
- Open the trapped chest
Expected results:
Comparator activates
Observed results:
Comparator doesn't do anything
For more detail on this, see the attachments
Comparatorshave their signals cut off by containers when they shouldn'tComparators don't interact correctly with trapped chests
Trapped chests don't power comparators correctly
Steps to reproduce:
- Place down a trapped chest
- Place redstone dust next to it
- Add a comparator which would be activated by the dust
- Open the trapped chest
Expected results:
Comparator activates
Observed results:
Comparator doesn't do anything
For more detail on this, see the attachments
Trapped chests don't power comparators correctly
Steps to reproduce:
- Place down a trapped chest
- Place redstone dust next to it
- Add a comparator which would be activated by the dust
- Open the trapped chest
Expected results:
The comparator activates
Observed results:
The comparator doesn't do anything
For more detail on this, see the attachments
Trapped chests don't power comparators
correctlySteps to reproduce:
- Place down a trapped chest
- Place redstone dust next to it
- Add a comparator which would be activated by the dust
- Open the trapped chest
Expected results:
The comparator activates
Observed results:
The comparator doesn't do anything
For more detail on this, see the attachments
Trapped chests don't power comparators
Steps to reproduce:
- Place down a trapped chest
- Place redstone dust next to it
- Add a comparator which would be activated by the dust
- Open the trapped chest
Expected results:
The comparator activates
-
Observed results:
The comparator doesn't do anything
For more detail on this, see the attachments
Not to be confused with how bells act. bells only have a visual bug
When
Redstone is connected to a piston (using the new connectivity) the block that is next toredstone will be energized (see screenshot). I expect only the piston was energized.Device: Asus Zenfone 5
When redstone dust is connected to a piston (using the new connectivity) the block that is next to unintended blocks will also be powered (see attachments).
When redstone dust is connected to a piston (using the new connectivity) the block that is next to unintended blocks will also be powered (see attachments).
When redstone dust is connected to any redstone component that redirects dust but does not produce power(will call this a 'consumer' [*] component to match the technical community's term), unintended blocks will also be powered by it. See attachments
Note: This appears to work as if the dust wasn't redirected in the first place while also powering the consumer* component
Steps to reproduce:
- Build the setups from the attachments
- Power the lever
Expected results:
Powering matches with the visual representation(as it does in Java edition), and so only the components that seem like they'll be powered, get powered.
Observed results:
The dust powers not only the block it redirects into, but also blocks it shouldn't from visual logic (testing shows that it powers as if it was not redirected in that case)
When redstone dust is connected to any redstone component that redirects dust but does not produce power(will call this a 'consumer' [*] component to match the technical community's term), unintended blocks will also be powered by it. See attachments
Note: This appears to work as if the dust wasn't redirected in the first place while also powering the consumer* component
Steps to reproduce:
- Build the setups from the attachments
- Power the lever
Expected results:
Powering matches with the visual representation(as it does in Java edition), and so only the
components that seem like they'll be powered, get powered.Observed results:
The dust powers not only the block it redirects into, but also blocks it shouldn't from visual logic (testing shows that it powers as if it was not redirected in that case)
When redstone dust is connected to any redstone component that redirects dust but does not produce power(will call this a 'consumer' [*] component to match the technical community's term), unintended blocks will also be powered by it. See attachments
Note: This appears to work as if the dust wasn't redirected in the first place while also powering the consumer* component
Steps to reproduce:
- Build the setups from the attachments
- Power the lever
Expected results:
Powering matches with the visual representation(as it does in Java edition), and so only the blocks that seem like they'll be powered, get powered.
Observed results:
The dust powers not only the block it redirects into, but also blocks it shouldn't from visual logic (testing shows that it powers as if it was not redirected in that case)
Redstone poweringwrongsidewhen redirected bypistonRedstone powers the wrong blocks when redirected by some components
Hess you're wrong. This is not how the block placement works. An example of this would be a lot of reports...
For example: MCPE-116032, MCPE-116140
Marek Kedrierski that's not my point
The wiki is made by the fans, not devs afaik. It doesn't prove intentional behaviour
I get that it may be intentional with the first part where it gets the signal cut off by containers, but the trapped chest? It doesn't quite seem logical that it would be a power source which wouldn't power comparators
We can never know until they reply
found that it also doesn't power comparators that aren't detecting the trapped chest
Attachments
Fixing this would make people unable to put redstone dust on top of extended piston bodies and would break alot of contraptions which people have made.
Visual bug; a good fix for this would be making bells not redirect the dust
If this was changed to actually redirect dust, it would be the exact same as a target block(from 1.17.20.20+) but noisy, since bells conduct redstone signals for some reason.
I wouldn't mind them actually redirecting the dust but they should be changed to not conduct redstone signals if that happens
Instructor Snow what GH showed is exactly the thing this ticket was meant to be about
changed