shell echo
In the Dimension Update, Transmitters/Receivers currently somehow only accept shape signals as channel IDs, even though the symbol for the channel ID is a "#" which indicates numbers, and the Signal Producer can also produce number signals (e.g. "5") or color signals (e.g. "color-r"). In particular, feeding a number signal into the Global Transmitter/Receiver yields neither the expected result (i.e. the transmitted signal), nor any helpful error message or symbol.
sage sluice
#🔌wires message
scenic raft
(Not a bug)
relevant feedback: https://discord.com/channels/1000343719314198548/1379537839967961191
shell echo
It may not be intended behavior that one can use number signals, but surely the fact that the "#" symbol doesn't accept number signals counts as a bug? If not one of gameplay, then certainly one of form vs. function.
blazing reef
# can mean channel without number, like the # at the start of channel names in discord
shell echo
I'm from a generation where my first association for "#" is very clearly "number" and not "social media hashtag" or "Discord channel name". Seems like a suboptimal symbol if it can be misunderstood in such a way.
left helm
Sir we've been using Irc in 1994
tulip stratus
Agreed. My initial assumption was it used numbers. When that didnt work I tried colours. Stupidly didn't think it would use shapes till I was told.
frigid wyvern
Having numbers would allow for machines that use 1 to N channels depending on requirements. Procedurally generating shape codes sounds like hell
subtle blaze
Came here to submit the same. Very odd to me that the # is looking for and works for shape codes but not for numbers. Would be much easier to remember that I'm producing a shape on channel number 1 than channel red circle. And as mentioned in the feedback channel, the in game Knowledge Panel has no information on how the Global Transmitters are supposed to work
left helm
Having numbers would allow for machines that use 1 to N channels depending on re...
If procedural generation is an issue, how do you add two numbers in shapez wires? I can't wrap my head around how many wires a bitwise adder takes, subjectively I think procedurally generating shapez is more viable than numbers with the tools we have
frigid wyvern
If procedural generation is an issue, how do you add two numbers in shapez wires...
Im assuming we get mathematical buildings in the future
vital jasper
There is no argument that the current implementation is unintuitive. It is intended to work this way but will likely be change.
uneven holly
Thank you for your report! 😄
There's already a ticket being worked on in our internal server. The team is looking into using numbers as channel IDs 🙂
unkempt jolt
scenic raft
Hopefully shapes will still be usable as channels in the future.
quick basin
I'll also add that clicking the question mark for both Global Signal Transmitter and Global Signal Receiver bring you to the "Wires" knowledge panel, which says that logic signals can be any of number/color/shape/etc. It wasn't until I came here to find this bug that I realized I wasn't even looking at a knowledge panel for transmit/receive, because it was so close otherwise.
acoustic anchor
To me, # always means 'number' and has for decades - I wasted so much time on this thinking I was going mad until I came to this thread. Constructing a different shape for a new channel is just nuts to me - so much easier to have an actual channel number. The "help" text when you configure the channel says null, conflict, Number, colour, or shape - yet only "shape" actually works.
This is a bug to me.
blazing reef
fwiw that help text describes the different signal types that wires can transmit, not the signal types that can be used as global transmitter channels
scenic raft
those should be the same thing
eager rose
Same here - I haven't found any transmitter/receiver setup to work - so I'm not sure what I'm doing wrong.