Excavator does not report mineral vein depletion through redstone control interface
paperky opened this issue ยท 0 comments
Minecraft Version
1.21.1
Immersive Engineering Version
12.4.2-194
Expected Behavior
Expected behavior:
The manual states that an excavator "Outputs a signal relative to the remaining ore in the vein", and that unless otherwise mentioned, this signal should be available at the redstone control surface of the multiblock.
Actual Behavior
Observed behavior:
The comparator reading from the excavator always reads zero strength regardless of mineral vein depletion.
Comparator is reading a zero and not just un-powered since if placed with a solid block between the Excavator and the comparator, the comparator does not react to soft-powering of the block behind it, which is identical behavior to an empty container in place of the Excavator.
Attempting to change the saturation of the mineral vein has no effect on the comparator.
Steps to reproduce
- Generate a new creative world with Immersive Engineering version 12.4.2-194 and default worldgen
- locate a mineral vein with Mineral Survey Tools, or through console commands
- Build or structure-spawn an excavator near or on the mineral vein, and power it with a Creative Accumulator.
- Verify that the excavator is on a mineral vein using a core sample drill directly above the center of the bucket wheel. Keep the core sample item for reference.
- Place a comparator so it reads from the redstone control surface, observe no signal output.
- '' through a block, observe no signal output.
- Place a redstone probe on the redstone control surface and connect an output redstone wire connector to it. Connect the redstone wire connector to a lamp or other redstone component. Observe no signal output for any threshold.
- Use console commands
/ie mineral setDepletion <amount>while standing inline with the top of the excavator's bucket wheel - Take a new core sample at the same location as step 4. Verify that the new core sample has fewer expected ores.
- Repeat steps 5-7, observe the same no-output state of the comparator/probe
- Repeat step 8 with different values for
<amount>, and then 5-7. I have tested withamountbeing 15000, 20000, and 30000 and observed no change.
I have not tested every rotation and mirroring of the excavator.
The "empty container" behavior:
Redstone Probe with no output at threshold 0:

Comparator showing no output: