-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Describe your idea (If you have more than one idea, please open the rest in other issues)
I would suggest re-adding the Redstone Integrator, as it is beneficial to have a standalone peripheral for redstone I/O, even if it duplicates many of the features from CC:T's base relay. Most importantly, it can be given a persistent name which can then be queried in programs, so there is a source of truth for complex setups. In testing with CC's relays, there is just no way I can think of to have foolproof individual identification for large setups where cables and network connections are constantly changing. The ability to name integrators with an anvil and then query that specific integrator later by sorting calls to .getName() is a feature that will be sorely missed, and I can't be the only one - is there room to add it back in?
Describe alternatives you've considered if any
I have attempted to find any sort of consistent automatic identification scheme for the base CC relays, and when networks are updated (blocks changing, etc.) it seems to mess with all of my relay mappings. I attempted naming the relays, as well as assigning names in a program to all the relays initially discovered by getting all peripherals, and the issue is just than none of these ID's seem to stick.
Additional context
No response