Redstone/torch state changed by IC lever output does not propagate to adjacent redstone (affects all ICs)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
Research direction
Start by reproducing the issue with any IC, an output lever, and adjacent redstone dust or a torch. Trace the IC output lever update path and its adjacent-block notifications, comparing the observed behavior with a manually flipped vanilla lever. Done when directly attached redstone updates immediately whenever the IC output changes.
Written by the indexing model from the issue text.
Description
CraftBook Version
reproduced on 3.10.12 and 3.10.13
Platform Version
Minecraft 1.21.11 paper-1.21.11-132
Confirmations
- I am using the most recent Minecraft release.
- I am using a version of WorldEdit compatible with my Minecraft version.
- I am using a version of CraftBook compatible with my Minecraft version.
- I am using the latest or recommended version of my platform software.
- I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
- 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
- Build any IC (e.g. a simple gate) with a sign on one side and a lever
on the other, as normal. - 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. - Trigger the IC so its output lever changes state.
- 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.
- Dominant language
- Java
- Stars
- 320
- Forks
- 165
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EngineHub/CraftBook
-
status:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
status:pending type:bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
status:pending type:bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
status:accepted type:feature-request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Wireless RedstoneOpenstatus:pending type:feature-request
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in EngineHub/CraftBook
Similar issues
-
type: possible bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
grimmory-tools/grimmory#2850 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aoqia194/leaf-loader#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/streampark#4521 ·