28c/88 caterpillar

[googoIpIex]

This is a fairly promising reaction:

Code: Select all

x = 21, y = 129, rule = B3/S23
2o$2o3$b2o$b2o16b2o$19b2o22$2o$2o3$b2o$b2o16b2o$19b2o22$2o$2o3$b2o$b2o
16b2o$19b2o22$2o$2o3$b2o$b2o16b2o$19b2o22$2o$2o3$b2o$b2o16b2o$19b2o7$
11bo$10b3o$9b2o2bo$11b3o!

is there any way to make it reburnable?

[dvgrn]

This is a fairly promising reaction:

Code: Select all

x = 21, y = 129, rule = B3/S23
2o$2o3$b2o$b2o16b2o$19b2o22$2o$2o3$b2o$b2o16b2o$19b2o22$2o$2o3$b2o$b2o
16b2o$19b2o22$2o$2o3$b2o$b2o16b2o$19b2o22$2o$2o3$b2o$b2o16b2o$19b2o7$
11bo$10b3o$9b2o2bo$11b3o!

is there any way to make it reburnable?

Unfortunately, if the output is lined up with the input, the singleton block is one diagonal cell away from where one of the half-blockade blocks appears in the post-burn configuration. The burning process only produces one glider, but three gliders would be needed to kill the other block in the half-blockade and then (2,1)-shift the remaining block into place. So unfortunately that seems like a fairly long way from an over-unity reaction.

[googoIpIex]

I really don’t know how to run gencols, but we could look through a list of one Glider collisions with lumps of muck.

[muzik]

It's easy to delete one block; repositioning the remaining one wouldn't be easy though.

Code: Select all

x = 28, y = 38, rule = B3/S23
5b2o$5b2o3$6b2o17b2o$6b2o17b2o$2bo$obo$b2o23b2o$26b2o19$5b2o$5b2o3$6b
2o17b2o$6b2o17b2o3$26b2o$26b2o!

[googoIpIex]

I was thinking a collision with the LOM while it’s still active.