[1.1.5.0] @Logic connections on Glove

The Tower Glove™'s Connection Tool mode can not connect the @Logic output of Logic Compare Gates to the @Logic input of AND, NOT, OR, or XOR logic gates; citing “Max Connection Reached” even when there are no other @Logic inputs or connections on the gates. The gates work as intended, if done through the connections menu instead of using the Tower Glove™.

Steps to Reproduce

  1. Place down a Counter Module
  2. Place down a Logic Compare
  3. Place down a Logic AND Gate
  4. Place down a Boolean Gate Toggle Module
  5. Equip your Tower Glove™ on it’s “Connections” setting
  6. Wire the Counter Module’s @Logic to the Logic Compare’s @Logic
  7. Wire the Boolean Gate’s Toggle Module’s @Logic to the Logic AND Gate’s @Logic
  8. Attempt and Fail to wire the Logic Compare’s @Logic to the Logic AND Gate’s @Logic

What I expected to happen

The Tower Glove™ successfully marries the @Logic output of the Logic Compare to the @Logic input of the Logic AND Gate.

What happened

The Tower Glove™ tells us that the Logic AND Gate (or NOT, OR, and XOR) has “Max Connections Reached”.


Notes / Media


Many hours of messing with a very large quantity of logic gates might have fried my brain by the time I create this post at 2:00 AM.

I do like really want this one fixed. I work with a very large amount of compare gates often, and the glove not properly being able to hook up gates makes the workflow extremely extremely slow even with good component naming schema to hunt down components quicker in the list.

In my experience logic gates in this game seem generally unreliable and unintuitive, to a point that I gave up on them entirely, and just do my best to implement logic with other components where possible. I don’t know if they’ve improved it over the past year or so, but I hope they do because the I/O system is very powerful and has a lot of potential.

I’ll take a look at what the glove is doing when checking for max connections.