Skip to content

Redstone interface fixes (1.21.1)#132

Open
rafern wants to merge 6 commits into
North-Western-Development:1.21.1from
rafern:1.21.1-redstone-interface-fixes
Open

Redstone interface fixes (1.21.1)#132
rafern wants to merge 6 commits into
North-Western-Development:1.21.1from
rafern:1.21.1-redstone-interface-fixes

Conversation

@rafern

@rafern rafern commented Apr 2, 2026

Copy link
Copy Markdown

Added support for bundled cables to the redstone interface card (interface block already supported it, but not the card that you put in the computer block, which was inconsistent), and fixed bugs related to the redstone interface card and block.

Bug fixes:

  • Fixed redstone interface card and block emitting signals in the wrong direction (might clash with Clearly separate local and global directions when using Side #126, which I unfortunately only found after working on this)
  • Fixed getBundledInput returning null instead of a list of 0-level signals if a bundled cable is not connected

Note that, to test this, I had to change the NeoForge version to 21.1.222, and had to use this fork of MarkdownManual. These changes are not included.

Edit: there were some issues with handling of bundled cable directions, which are now fixed. I don't think I've fully understood how these are supposed to work though, as there seems to be some inconsistency between how directions are handled for redstone versus bundles, so more work might be needed

rafern added 6 commits April 2, 2026 22:26
BundledRedstone.isAvailable should probably also be deprecated, since
you have to check that the return value of getBundledInput isn't null
anyway. Either that, or BundledCableHandler.getBundledInput should never
return null
Not super happy with the implementation, lots of copy-pasta. Code could
be shared
@dhouck

dhouck commented May 7, 2026

Copy link
Copy Markdown

I think this does clash with my PR as you point out, and that the issue is deep enough that the smaller fixes you do arenʼt really enough.

Part of the problem is that you can pass either front or south to the API and it tries to handle both, so I needed to do a much deeper fix. And part of the problem is that the current code tries to use the same type to mean too many different things and doesnʼt clearly separate them, which is why four of your six commits are trying to fix.

If GitHub had the concept of stacked PRs Iʼd suggest you rebase on top of mine, but it doesnʼt, so Iʼm not sure what the best option is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants