KittyTac wrote:Sarp wrote:Lom to r
Code: Select all
x = 11, y = 15, rule = B3/S23
b2o$b2o3$8b3o$2o5bo2bo$2o5b3o6$8b2o$8b2o!
It's one-time. :(
Technically it's not quite one-time. The R appears a long time before the block catalyst is destroyed, and escapes from the reaction envelope 16 ticks before that destruction. So at least theoretically, there's time to add more catalysts and rescue the signal:
Code:
Select all
x = 20, y = 17, rule = LifeHistory
16.2B$10.9B$9.9B$9.9B$7.11B$6.12B$.B.5B2ABD7B$2AB.3BABAB2D7B$2A5BABA
2D7B$.2B.3B2A9B$4.13B$5.10B$5.6B2.B$4.4B.2B.3B$5.4B.2B2AB$5.2B2AB2.2A
$7.2A!
#C [[ AUTOSTART THUMBNAIL THUMBSIZE 2 GPS 15 PAUSE 2 T 49 PAUSE 2 T 65 PAUSE 2 T 81 PAUSE 2 LOOP 82 ]]
In practice there are probably only a few ticks before that backspark has gone irretrievably out of control, though. I don't think any of the R-to-Xs in the current
Elementary Conduits Collection can do anything with that R output.
The bigger problem is that you also have to get the LoM to that position in the first place. It would probably make more sense if people would come up with a half-decent source of LoMs before they bother to find
all these converters that need LoM inputs. It kind of
limits the usefulness of the conduit if the LoM has to be there at T=0 and there's no practical way to produce another one.
Some of the linked LoM-to-X converters allow the LoM to be produced by colliding two gliders, at least. That's expensive enough to make the whole exercise ultimately fairly pointless, but at least there's
something. This latest LoM-to-R seems to have a block in the way of one or the other of those gliders, no matter which way you build the LoM.
