Describe the Bug

If two redstone links are placed more than 127 blocks apart on the y axis (vertical), they apparently do not connect. However, when another redstone link is placed within range, the status of the apparently out-of-range link is also considered when the state of the in-range link is changed.

Reproduction Steps

1. Place a redstone link in receive mode at some y level, powering a redstone lamp or similar.
2. Place another redstone link at the same x,z, but at a y level at least 128 blocks lower or greater in send mode.
3. Power the sending link and note it does not power the receiving link.
4. Create another link within 127 y levels in send mode.
5. Power and un-power the in-range send link.
6. Note the receiving link remains powered.
7. Un-power the out-of-range link, note the receiving link remains powered.
8. Power and un-power the in-range send link, note when the in-range send link becomes de-powered, so does the receiving link.
9. Repeat as necessary at various x,z distances. This process seems to work out to the intended horizontal range in a x,z oriented cylinder.

Expected Result

Redstone Links outside of 127 y-levels should either link or not consistently, instead of being "relayed" through state changes of an in-range link.

Screenshots and Videos

No response

Crash Report or Log

No response

Operating System

Windows 10

Mod Version

0.4.0e

Minecraft Version

1.18.1

Forge Version

39.1.0

Other Mods

Reproduced with no other mods running alongside Create 0.4.0e

Additional Context

No response

Its scope is a sphere.

I'm not 100% sure this is correct from the testing I did, more like a 127-high cylinder. That said, my issue is not focused on the scope of the device, but rather that it respects signals from outside its range when updated by an in-range link.

This issue has been marked as stale because it has been inactive for 3 weeks. It will be closed if it remains inactive for another 3 weeks.