A custom block can be turned into a redstone conductor with the following minecraft:redstone_conductivity configuration:
"minecraft:redstone_conductor": {
"redstone_conductor": true
}This will allow the block to connect adjacent redstone components to the circuit when powered, as well as preventing wire from stepping down to the block directly below, causing the wire to be cut off from the circuit.
However, when adding the minecraft:redstone_consumer component at the same time, the block fails to conduct redstone power while still cutting wire off. This behaviour should be impossible and is not seen in any vanilla redstone components. (See comments)
"minecraft:redstone_conductor": {
"redstone_conductor": true
},
"minecraft:redstone_consumer": {}In order to actually make a redstone consumer conduct redstone, a separate propagates_power parameter in minecraft:redstone_consumer has to be set to true. This parameter should not exist as propagating power is a feature of redstone conductors and so should only be linked to the redstone_conductor parameter. A block that is a redstone conductor should always propagate (or conduct) power, regardless of whether it is a block that can be activated by redstone, and a block that is not a conductor should never conduct power.
Conversely, if propagates_power is true and redstone_conductor is false, another situation that should be impossible is created, where the block is able to conduct redstone power while not (visually) cutting wire off.
Comments 3
Interesting, maybe it would be better if propagates power defaulted to the value of redstone conductor or if the wire cutting, comparator stuff were separate parameters in redstone conductivity
Having them as separate, labeled values for different solid/non-solid related properties, labeled accordingly, would probably be best, as there are also other properties controlled by solidity, like mob suffocation and whether minecarts bounce off of them, that could be separated into separate modifiable properties, maybe under a “solidity” grouping, as the multiple separate values for solidity in different areas seem to also cause issues for the Mojang devs, as the new shelf block has the same issue mentioned in your bug report, namely cutting redstone while not conducting signals or visually cutting it.
Also the issue where redstone can be visually cut/not cut while behaving differently needs to be fixed.
“This behaviour should be impossible and is not seen in any vanilla redstone components.”
Well… This exact issue is seen in about 20 - 30 ish vanilla blocks, which either visually cut redstone while not conducing it, or visually not cutting redstone lines while conducting power and actually cutting the visually uncut line. Also, comparator readings through conductive blocks are based on the redstone_conductor property, so they can also diverge from the actual conductivity of the block.
An incomplete list, based on memory:
Conducts, doesn’t cut visually, blocks comparator readings:
Target block, Bell, dripleaf.
Doesn’t conduct, cuts visually, allows comparator readings:
Piston, Sticky Piston, chain (both copper and iron), sniffer egg, path block, farmland, chorus plant, chorus flower, copper grate, also the shelf I think.
Special: Doesn’t conduct, cuts actually not visually, denies compartor readings:
Mob heads
Skulk shrieker
Copper bulb (also cuts visually as well as properly)
While this is strange, several mechanics here are used in actual vanilla redstone builds, and fixing this bug would annoy/anger many in the Bedrock Redstone community (that includes me, as I have used the piston/sticky piston and copper bulb properties in some of my redstone builds.)
Notably there is an earlier bug report related to this about comparators reading through chains (MCPE-138549), where many comments noted it uses in shuklerbox loaders (not sure how it is used though, I haven't tried to build one)
As a result, I don't really want nor expect Mojang to change this, and if so I would prefer them to make it either have some kind of consistency or some visual indication in game.
However, 4 blocks which used to have strange properties were fixed relatively recently, namely tnt, sea lantern, mangrove roots, and beacons, so some of the more obscure strange blocks may be fixed in the future.