Describe the Suggestion

I suggest the modification or addition of a new Redstone Link, adding new useful features:

1. NBT data in Frequencies: As of now, only the item ID seems to be used to determine the frequency, limiting not only the number of frequencies that can be used (2,900,209 unique frequencies, using vanilla minecraft + create alone) but also causing problems on multiplayer worlds, as many players might use the same blocks as frequencies and sometimes can create structures close to each other, which generate conflicts (Ex.: Crushing wheel + cobblestone for a cobblestone crushing contraption). With the addition of NBT data on the frequencies, it would allow for "private" frequencies to be created (Ex.: written books), which would solve the two problems mentioned.
2. Labels: This feature is linked to the one before it, as it would be hard to distinguish between two unique frequencies if two items of the same type but with different tags were used. To solve the issue, I suggest the introduction of labels, which would be strings of text that could be added to Redstone Links, similarly to how Tile Entities can be named. This would allow for easily identifying the frequencies the Redstone Links are using.
3. Locks: This feature would prevent all except the one with the corresponding key to modify the frequencies of the Redstone Link, which could prevent griefing and accidental frequency clearings. Keys could be copied, allowing for multiple players to be able to modify the frequencies. An alternative to this solution could be locking Redstone Links to the player that placed it, though I believe it could generate more problems, as players many times work together, and such locking would prevent easy collaboration between players.

Screenshots and Videos

As a Proof of Concept, commands were used on the second and third examples. The implementation of the second example would possibly be an addition to the create rendered UI.

1. In this example, each colored pair of Redstone Links have different written books, which would allow them to transmit data separately.
   

2. In this example, each frequency could have the name of it's item shown on hover. It could also have the name of the Redstone Link on top of it.
   
   

3. In this example, the Redstone Link on the left is locked, while the Redstone Link on the right is unlocked.

Additional Context

No response

+1. I would like to request being able to choose to respect/ignore nbt data on a redstone link/linked controller. It took me a minute to realize that my naming my items did nothing to differentiate them. I'm writing this comment on this repo as the fabric port says they don't add features, and to request it with you instead. I play on Fabric 1.20.1 and would love to see this feature added to both versions of Create

Fabricators-of-Create#1277 (comment)