EngineHub / EngineHub/CraftBook

Redstone/torch state changed by IC lever output does not propagate to adjacent redstone (affects all ICs)

Open
#1,373 2 comments 0 reactions 0 assignees View on GitHub
status:pending type:bug
Dominant language
Java
Stars
320
Forks
166
Avg merge
6d 21h
Merged PRs (30d)
2

Description

### CraftBook Version

reproduced on 3.10.12 and 3.10.13

### Platform Version

Minecraft 1.21.11 paper-1.21.11-132

### Confirmations

- [x] I am using the most recent Minecraft release.
- [x] I am using a version of WorldEdit compatible with my Minecraft version.
- [x] I am using a version of CraftBook compatible with my Minecraft version.
- [x] I am using the latest or recommended version of my platform software.
- [x] I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
- [x] I am NOT using a fork of WorldEdit, such as FastAsyncWorldEdit (FAWE) or AsyncWorldEdit (AWE)

### Bug Description

When an IC (any IC - not specific to one type) toggles its output lever,
the resulting redstone/power change is not properly propagated to blocks
placed directly on/adjacent to the IC block itself (the block the lever
and sign are attached to). Redstone dust or torches connected on that
block do not update to reflect the new power state.

### Expected Behavior

Toggling an IC's output lever should trigger a full redstone update to all
directly adjacent blocks, exactly like a player manually flipping a lever
would in vanilla Minecraft. Specifically, redstone dust or redstone torches
placed on the same block as the IC's lever should immediately reflect the
new power state, without requiring an unrelated/manual block update to be
forced first.

### Reproduction Steps

1. Build any IC (e.g. a simple gate) with a sign on one side and a lever
on the other, as normal.
2. Place redstone dust (or a redstone torch) directly on the IC block
itself, so that it should be powered/depowered whenever the IC's
lever toggles.
3. Trigger the IC so its output lever changes state.
4. Observe: the redstone dust / torch does not update its visual or
functional state, even though the lever itself has visibly toggled.

### Anything Else?

**Workaround found**
Manually forcing an unrelated block update on the same block (e.g. via
a separate redstone signal momentarily touching it) makes the redstone
dust/torch refresh correctly to match the actual lever state. This
confirms the lever state itself is correct internally - only the
neighbor block update/notification is missing.
**Expected behavior**
Toggling an IC's output lever should trigger a full redstone update to
all adjacent blocks, exactly like a player manually flipping a lever
would in vanilla.

**Additional context**
This appears to affect ICs broadly (not one specific IC), specifically
whenever redstone wiring is taken directly off of the IC's own block
rather than off a block the lever is attached facing outward from.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.