If you remove the white rod from the white slot, the displays should fade away. But again, implicit taking can mess things up:
>PUT WHITE ROD IN WHITE SLOT
As you insert the rod, the walls come alive with a white tracery of controls,
dials, and gauges. In addition, a black slot surrounded by an ominous dead-black
circle appears.
>TAKE WHITE ROD
When you remove the rod, the displays fade and the wall becomes featureless
gray, except for the white slot.
>PUT WHITE ROD IN WHITE SLOT
As you insert the rod, the walls come alive with a white tracery of controls,
dials, and gauges. In addition, a black slot surrounded by an ominous dead-black
circle appears.
>READ WHITE ROD
(Taken)
How can I read a white rod?
The room description is updated properly because it checks if the white rod is in the white slot, but WHITE-KEY-FCN also moves/removes the black slot.
I noticed that WHITE-KEY-FCN also calls TRYTAKE when you put it in the slot. It looks to me like this should work even if WHITE-KEY has TRYTAKEBIT, but the message may be different. I haven't tried it, though.
If you remove the white rod from the white slot, the displays should fade away. But again, implicit taking can mess things up:
The room description is updated properly because it checks if the white rod is in the white slot, but
WHITE-KEY-FCNalso moves/removes the black slot.I noticed that
WHITE-KEY-FCNalso callsTRYTAKEwhen you put it in the slot. It looks to me like this should work even ifWHITE-KEYhasTRYTAKEBIT, but the message may be different. I haven't tried it, though.