Description: The current behaviour of a Nixie tube is that, when some text is written inside of it using a name tag, the shown content can then be reset to the redstone signal if you manually right-click the tube.
This doesn't seem to happen when using a deployer: a deployer can right-click with a name tag a Nixie tube to set its content, but it can't right-click, with the empty hand, to reset it back to the redstone signal mode.
In addition, when having a deployer constantly interacting with the Nixie tube, manually right-clicking the tube to reset its content works but isn't shown until a block is placed/broken near the tube. This leads me to think that the tube-resetting mechanic is inconsistent when used along with a deployer, and pretty buggy. Here's a video to show what happens, first when no deployer is placed and then with a deployer.

To reproduce: place a Nixie tube and a daylight sensor near it. The tube will show the signal strength. Now, write something inside the tube using a name tag. Then, right-click the tube with the empty hand, the Nixie tube will show the redstone signal again. Then, use the name tag on the tube again and place a deployer with the empty hand, 1-block distance from the tube: the it won't reset its content and won't go back to the redstone signal mode.

More info: I experience this bug in 1.16.5 Forge v36.2.4 creative mode, using creative motors, running Create v0.3.2d and Flywheel v0.2.3. I have not tested in different versions.

I noticed this issue while creating a mechanism that needed two Nixie tubes, one near the other, the first showing a redstone signal and the second showing some text. Name tags on tubes, though, affect all the near tubes starting from the left. I wanted to show the text only in the second tube, and then I thought of having a deployer that constantly reset the first Nixie tube to the redstone signal, but this can't be done due to this bug.

This issue has been marked as stale because it has been inactive for 3 weeks. It will be closed if it remains inactive for another 3 weeks.

This issue has been closed since it has been inactive for 3 weeks since it was marked as stale.