Rule request thread

[hth3]

Life+LangtonsAnt but an ant cell is born when an off cell is surrounded by 6 life cells and a life cell is born when an off cell is surrounded by 6 or 7 ant cells.

Can anyone do this, please? I don't know Golly/LifeViewer rule format and it is very confusing.

[islptng]

This please

Code: Select all

name = "ProgrammableLife"
n_states = 18
n_neighbors = 8
# order for 8 neighbors is NW, NE, SW, SE, N, W, E, S, C
def transition_function(a):
	nw,ne,sw,se,n,w,e,s,c = a
	if c not in [14,15]:
		# Test CGoL parts
		alivelist = [(i % 2 == 1) for i in a]
		self = alivelist[-1]
		alivelist = sum(alivelist[:-1])
		cgol = False
		if alivelist == 3: cgol = True
		if alivelist == 2 and self: cgol = True
		# Test Wire parts
		if c in [2,3,8,9]: check = [12,13]
		if c in [4,5,10,11]: check = [8,9]
		if c in [6,7,12,13]: check = [10,11]
		try: check
		except: return self // 2 * 2 + cgol
		wire = False
		if check[0] in [n,w,e,s]: wire = True
		if check[1] in [n,w,e,s]: wire = True
		if nw in check and n in [0,1] and w in [0,1]: wire = True
		if sw in check and s in [0,1] and w in [0,1]: wire = True
		if ne in check and n in [0,1] and e in [0,1]: wire = True
		if se in check and s in [0,1] and e in [0,1]: wire = True
		if n in check and w in check: wire = False
		if s in check and w in check: wire = False
		if n in check and e in check: wire = False
		if s in check and e in check: wire = False
		# combine together
		if c in [2,3,8,9]: retval = [2,3,8,9]
		if c in [4,5,10,11]: retval = [4,5,10,11]
		if c in [6,7,12,13]: retval = [6,7,12,13]
		return retval[wire * 2 + cgol]
	wire = 0
	for i in [8,9,10,11,12,13]:
		if i in [n,w,e,s]: wire = True
	return 14 + wire

[b-engine]

Life, but cells check the neighbors at previous generation instead of current generation when updating.


EDIT:
I think this had gone wrong:

Code: Select all

#R PastLife
!
[[ RANDOMIZE ]]

@RULE PastLife
@TABLE
n_states:4
neighborhood:Moore 
symmetries:permute
var a={0,1,2,3}
var a1=a
var a2=a
var a3=a
var a4=a
var a5=a
var a6=a
var a7=a
var a8=a
var l={1,3}
var l1=l
var l2=l
var l3=l
var d={0,2}
var d1=d
var d2=d
var d3=d
var d4=d
var d5=d
var d6=d
var d7=d

0,l,l1,l2,d1,d2,d3,d4,d5,2
1,l,l1,l2,d1,d2,d3,d4,d5,2
2,l,l1,l2,d1,d2,d3,d4,d5,3
3,l,l1,l2,d1,d2,d3,d4,d5,3

2,l,l1,d1,d2,d3,d4,d5,d6,3
3,l,l1,d1,d2,d3,d4,d5,d6,3

0,a1,a2,a3,a4,a5,a6,a7,a,0
1,a1,a2,a3,a4,a5,a6,a7,a,0
2,a1,a2,a3,a4,a5,a6,a7,a,1
3,a1,a2,a3,a4,a5,a6,a7,a,1

[islptng]

Will anyone make Go into RULETABLE?

A small demo I made, displaying Lee Sedol v.s. AlphaGo Round 4:

Code: Select all

x = 21, y = 21, rule = GoCapture
21A$A19.A$A19.A$A19.A$A19.A$A19.A$A19.A$A19.A$A19.A$A19.A$A19.A$A19.A
$A19.A$A19.A$A19.A$A19.A$A19.A$A19.A$A19.A$A19.A$21A!

[[ STARTFROM 1 STEP 10 NOTHROTTLE ]]
[[ PASTET 10 PASTE H! 16 4 ]]
[[ PASTET 20 PASTE I! 4 16 ]]
[[ PASTET 30 PASTE H! 3 4 ]]
[[ PASTET 40 PASTE I! 17 16 ]]
[[ PASTET 50 PASTE H! 15 16 ]]
[[ PASTET 60 PASTE I! 15 17 ]]
[[ PASTET 70 PASTE H! 14 17 ]]
[[ PASTET 80 PASTE I! 16 17 ]]
[[ PASTET 90 PASTE H! 3 14 ]]
[[ PASTET 100 PASTE I! 6 17 ]]
[[ PASTET 110 PASTE H! 13 16 ]]
[[ PASTET 120 PASTE I! 16 15 ]]
[[ PASTET 130 PASTE H! 9 17 ]]
[[ PASTET 140 PASTE I! 5 3 ]]
[[ PASTET 150 PASTE H! 8 4 ]]
[[ PASTET 160 PASTE I! 3 7 ]]
[[ PASTET 170 PASTE H! 5 4 ]]
[[ PASTET 180 PASTE I! 3 10 ]]
[[ PASTET 190 PASTE H! 4 3 ]]
[[ PASTET 200 PASTE I! 2 16 ]]
[[ PASTET 210 PASTE H! 14 3 ]]
[[ PASTET 220 PASTE I! 17 9 ]]
[[ PASTET 230 PASTE H! 5 16 ]]
[[ PASTET 240 PASTE I! 5 15 ]]
[[ PASTET 250 PASTE H! 4 11 ]]
[[ PASTET 260 PASTE I! 6 16 ]]
[[ PASTET 270 PASTE H! 3 11 ]]
[[ PASTET 280 PASTE I! 4 10 ]]
[[ PASTET 290 PASTE H! 5 10 ]]
[[ PASTET 300 PASTE I! 5 9 ]]
[[ PASTET 310 PASTE H! 6 9 ]]
[[ PASTET 320 PASTE I! 5 8 ]]
[[ PASTET 330 PASTE H! 6 8 ]]
[[ PASTET 340 PASTE I! 2 10 ]]
[[ PASTET 350 PASTE H! 6 11 ]]
[[ PASTET 360 PASTE I! 6 7 ]]
[[ PASTET 370 PASTE H! 7 7 ]]
[[ PASTET 380 PASTE I! 6 6 ]]
[[ PASTET 390 PASTE H! 7 6 ]]
[[ PASTET 400 PASTE I! 13 3 ]]
[[ PASTET 410 PASTE H! 13 4 ]]
[[ PASTET 420 PASTE I! 12 3 ]]
[[ PASTET 430 PASTE H! 14 2 ]]
[[ PASTET 440 PASTE I! 9 4 ]]
[[ PASTET 450 PASTE H! 8 3 ]]
[[ PASTET 460 PASTE I! 10 7 ]]
[[ PASTET 470 PASTE H! 16 10 ]]
[[ PASTET 480 PASTE I! 16 9 ]]
[[ PASTET 490 PASTE H! 15 10 ]]
[[ PASTET 500 PASTE I! 15 9 ]]
[[ PASTET 510 PASTE H! 14 9 ]]
[[ PASTET 520 PASTE I! 14 8 ]]
[[ PASTET 530 PASTE H! 13 8 ]]
[[ PASTET 540 PASTE I! 14 7 ]]
[[ PASTET 550 PASTE H! 13 7 ]]
[[ PASTET 560 PASTE I! 13 9 ]]
[[ PASTET 570 PASTE H! 14 10 ]]
[[ PASTET 580 PASTE I! 13 6 ]]
[[ PASTET 590 PASTE H! 12 9 ]]
[[ PASTET 600 PASTE I! 14 5 ]]
[[ PASTET 610 PASTE H! 14 4 ]]
[[ PASTET 620 PASTE I! 13 10 ]]
[[ PASTET 630 PASTE H! 12 6 ]]
[[ PASTET 640 PASTE I! 13 11 ]]
[[ PASTET 650 PASTE H! 13 5 ]]
[[ PASTET 660 PASTE I! 14 6 ]]
[[ PASTET 670 PASTE H! 12 8 ]]
[[ PASTET 680 PASTE I! 17 10 ]]
[[ PASTET 690 PASTE H! 11 11 ]]
[[ PASTET 700 PASTE I! 9 11 ]]
[[ PASTET 710 PASTE H! 10 9 ]]
[[ PASTET 720 PASTE I! 7 8 ]]
[[ PASTET 730 PASTE H! 8 10 ]]
[[ PASTET 740 PASTE I! 7 5 ]]
[[ PASTET 750 PASTE H! 8 5 ]]
[[ PASTET 760 PASTE I! 6 4 ]]
[[ PASTET 770 PASTE H! 6 3 ]]
[[ PASTET 780 PASTE I! 11 9 ]]
[[ PASTET 790 PASTE H! 10 10 ]]
[[ PASTET 800 PASTE I! 12 10 ]]
[[ PASTET 810 PASTE H! 11 8 ]]
[[ PASTET 820 PASTE I! 10 8 ]]
[[ PASTET 830 PASTE H! 13 12 ]]
[[ PASTET 840 PASTE I! 14 11 ]]
[[ PASTET 850 PASTE H! 15 12 ]]
[[ PASTET 860 PASTE I! 15 11 ]]
[[ PASTET 870 PASTE H! 16 11 ]]
[[ PASTET 880 PASTE I! 16 12 ]]
[[ PASTET 890 PASTE H! 17 11 ]]
[[ PASTET 900 PASTE I! 14 12 ]]
[[ PASTET 910 PASTE H! 11 10 ]]
[[ PASTET 920 PASTE I! 9 9 ]]
[[ PASTET 930 PASTE H! 18 11 ]]
[[ PASTET 940 PASTE I! 15 13 ]]
[[ PASTET 950 PASTE H! 16 7 ]]
[[ PASTET 960 PASTE I! 17 12 ]]
[[ PASTET 970 PASTE H! 3 16 ]]
[[ PASTET 980 PASTE I! 3 15 ]]
[[ PASTET 990 PASTE H! 15 5 ]]
[[ PASTET 1000 PASTE I! 18 12 ]]
[[ PASTET 1010 PASTE H! 19 11 ]]
[[ PASTET 1020 PASTE I! 18 10 ]]
[[ PASTET 1030 PASTE H! 8 7 ]]
[[ PASTET 1040 PASTE I! 9 10 ]]
[[ PASTET 1050 PASTE H! 11 13 ]]
[[ PASTET 1060 PASTE I! 7 9 ]]
[[ PASTET 1070 PASTE H! 6 10 ]]
[[ PASTET 1080 PASTE I! 10 12 ]]
[[ PASTET 1090 PASTE H! 11 12 ]]
[[ PASTET 1100 PASTE I! 7 12 ]]
[[ PASTET 1110 PASTE H! 6 12 ]]
[[ PASTET 1120 PASTE I! 7 13 ]]
[[ PASTET 1130 PASTE H! 3 8 ]]
[[ PASTET 1140 PASTE I! 5 5 ]]
[[ PASTET 1150 PASTE H! 5 2 ]]
[[ PASTET 1160 PASTE I! 2 7 ]]
[[ PASTET 1170 PASTE H! 4 7 ]]
[[ PASTET 1180 PASTE I! 5 7 ]]
[[ PASTET 1190 PASTE H! 5 14 ]]
[[ PASTET 1200 PASTE I! 6 15 ]]
[[ PASTET 1210 PASTE H! 4 6 ]]
[[ PASTET 1220 PASTE I! 4 8 ]]
[[ PASTET 1230 PASTE H! 9 13 ]]
[[ PASTET 1240 PASTE I! 8 11 ]]
[[ PASTET 1250 PASTE H! 2 14 ]]
[[ PASTET 1260 PASTE I! 9 6 ]]
[[ PASTET 1270 PASTE H! 7 4 ]]
[[ PASTET 1280 PASTE I! 6 5 ]]
[[ PASTET 1290 PASTE H! 8 6 ]]
[[ PASTET 1300 PASTE I! 9 8 ]]
[[ PASTET 1310 PASTE H! 2 8 ]]
[[ PASTET 1320 PASTE I! 3 9 ]]
[[ PASTET 1330 PASTE H! 8 15 ]]
[[ PASTET 1340 PASTE I! 7 15 ]]
[[ PASTET 1350 PASTE H! 15 18 ]]
[[ PASTET 1360 PASTE I! 18 7 ]]
[[ PASTET 1370 PASTE H! 4 14 ]]
[[ PASTET 1380 PASTE I! 3 17 ]]
[[ PASTET 1390 PASTE H! 16 18 ]]
[[ PASTET 1400 PASTE I! 17 18 ]]
[[ PASTET 1410 PASTE H! 18 6 ]]
[[ PASTET 1420 PASTE I! 17 7 ]]
[[ PASTET 1430 PASTE H! 17 6 ]]
[[ PASTET 1440 PASTE I! 10 3 ]]
[[ PASTET 1450 PASTE H! 7 18 ]]
[[ PASTET 1460 PASTE I! 19 6 ]]
[[ PASTET 1470 PASTE H! 19 5 ]]
[[ PASTET 1480 PASTE I! 19 7 ]]
[[ PASTET 1490 PASTE H! 18 4 ]]
[[ PASTET 1500 PASTE I! 2 12 ]]
[[ PASTET 1510 PASTE H! 2 11 ]]
[[ PASTET 1520 PASTE I! 1 11 ]]
[[ PASTET 1530 PASTE H! 3 12 ]]
[[ PASTET 1540 PASTE I! 8 14 ]]
[[ PASTET 1550 PASTE H! 9 14 ]]
[[ PASTET 1560 PASTE I! 8 16 ]]
[[ PASTET 1570 PASTE H! 6 18 ]]
[[ PASTET 1580 PASTE I! 5 18 ]]
[[ PASTET 1590 PASTE H! 5 19 ]]
[[ PASTET 1600 PASTE I! 4 19 ]]
[[ PASTET 1610 PASTE H! 1 8 ]]
[[ PASTET 1620 PASTE I! 1 9 ]]
[[ PASTET 1630 PASTE H! 11 4 ]]
[[ PASTET 1640 PASTE I! 9 5 ]]
[[ PASTET 1650 PASTE H! 11 3 ]]
[[ PASTET 1660 PASTE I! 11 2 ]]
[[ PASTET 1670 PASTE H! 7 11 ]]
[[ PASTET 1680 PASTE I! 9 2 ]]
[[ PASTET 1690 PASTE H! 17 8 ]]
[[ PASTET 1700 PASTE I! 18 8 ]]
[[ PASTET 1710 PASTE H! 17 19 ]]
[[ PASTET 1720 PASTE I! 18 19 ]]
[[ PASTET 1730 PASTE H! 15 8 ]]
[[ PASTET 1740 PASTE I! 19 12 ]]
[[ PASTET 1750 PASTE H! 15 6 ]]
[[ PASTET 1760 PASTE I! 19 10 ]]
[[ PASTET 1770 PASTE H! 14 9 ]]
[[ PASTET 1780 PASTE I! 14 10 ]]
[[ PASTET 1790 PASTE H! 15 15 ]]
[[ PASTET 1800 PASTE I! 10 16 ]]

@RULE GoCapture

Simulation of Capturing in Go.
Use State 9 and 10 to play.

@COLORS
0 255 192   0
1 128  64  64
2   0   0   0
3 255 255 255
4  12  12  12
5 243 243 243
6   0   0 255
7   0 255 255
8   0 128   0
9 255 128 255

@TABLE
n_states:10
neighborhood:vonNeumann
symmetries:permute

# Any state
var a = {0,1,2,3,4,5,6,7,8,9}
var b = a
var c = a
var d = a

# Solid state
var p = {1,2,3,4,5,8,9}
var q = p
var r = p
var s = p

# White, marked black or border
var e = {1,3,4,5,9}
var f = e
var g = e
var h = e
# Black, marked white or border
var i = {1,2,4,5,8}
var j = i
var k = i
var l = i

# Black
var x = {2,4}
var m = {x,8}
# White
var y = {3,5}
var n = {y,9}

# Capturing
2,e,f,g,h,6
3,i,j,k,l,7
# Removing
x,6,a,b,c,6
y,7,a,b,c,7
6,a,b,c,d,0
7,a,b,c,d,0
# Mark
x,m,e,f,g,4
y,n,i,j,k,5
x,a,b,c,d,2
y,a,b,c,d,3
# Cool down
8,a,b,c,d,2
9,a,b,c,d,3

[hotcrystal0]

A rule (preferrably 5 or less states) where the “secret moderator camelship” works in all orientations.

[b-engine]

Life, but cells check the neighbors at previous generation instead of current generation when updating.

There are two different natural T-ships:

Code: Select all

x = 7, y = 3, rule = PastLife
B4.A$2C3.2C$B4.A!

@RULE PastLife
@TABLE
n_states:4
neighborhood:Moore 
symmetries:permute
var a={0,1,2,3}
var a1=a
var a2=a
var a3=a
var a4=a
var a5=a
var a6=a
var a7=a
var a8=a
var l={1,3}
var l1=l
var l2=l
var l3=l
var d={0,2}
var d1=d
var d2=d
var d3=d
var d4=d
var d5=d
var d6=d
var d7=d

0,l,l1,l2,d1,d2,d3,d4,d5,2
1,l,l1,l2,d1,d2,d3,d4,d5,2
2,l,l1,l2,d1,d2,d3,d4,d5,3
3,l,l1,l2,d1,d2,d3,d4,d5,3

2,l,l1,d1,d2,d3,d4,d5,d6,3
3,l,l1,d1,d2,d3,d4,d5,d6,3

0,a1,a2,a3,a4,a5,a6,a7,a,0
1,a1,a2,a3,a4,a5,a6,a7,a,0
2,a1,a2,a3,a4,a5,a6,a7,a,1
3,a1,a2,a3,a4,a5,a6,a7,a,1

[Citation needed]

Is there a rule that generates "Taxicab Voronoi Diagrams"?

[LuveelVoom]

Life, but a dot with no other cells in it’s R2 VN neighborhood travels upwards at the speed of light.

[confocaloid]

Life, but a dot with no other cells in it’s R2 VN neighborhood travels upwards at the speed of light.

I think that isn't clear enough to be an implementable request.

The idea "a dot ... travels upwards ..." isn't directly expressible as a rule in the ruleset of a cellular automaton, unless the conditions are completely boring.

The problem with "travels upwards" is that the range-2 von Neumann neighbourhood of the cell above the dot would be different, and there are different possibilities for what could be the neighbourhood configuration of the cell above the dot (even if the dot itself has no alive neighbours), and by that point it becomes unclear why exactly (for example) R1,C0,S1,B1,N@02 shown below doesn't count as a solution.

To clarify the idea, you would need to tell how a cell (whether alive or dead) should update its own state depending on its current condition (i.e. depending on some information derived from current states of its neighbours and/or its own current state), instead of telling that some cells would "move".

By "completely boring" I mean something like this (every dot "travels upwards at the speed of light"):

Code: Select all

x = 3, y = 3, rule = R1,C0,S1,B1,N@02
bo$2bo$3o!
#C [[ GRID ]]

[LuveelVoom]

Life, except:

Code: Select all

 x = 14, y = 5, rule = LifeHistory
2.B5.D$.3B5.D3.A$2BA2B.5D2.B$.3B5.D$2.B5.D!

but only upwards (the rule is anisotropic.)

[confocaloid]

Life, except:

Code: Select all

 x = 14, y = 5, rule = LifeHistory
2.B5.D$.3B5.D3.A$2BA2B.5D2.B$.3B5.D$2.B5.D!

but only upwards (the rule is anisotropic.)

If you mean that a single rule should prescribe future states of two different cells like that (rather than just the future state of a single cell), then the request remains unclear, there could be different interpretations and there can be contradictions when it would be impossible to evolve a pattern consistently.

To be clear, I think the following doesn't make an implementable request (state 4 = specified dead, state 3 = specified alive, state 2 = unspecified):

Code: Select all

x = 17, y = 5, rule = LifeHistory
2.D5.F5.B$.3D5.F3.BCB$2DC2D.5F.2BD2B$.3D5.F3.3B$2.D5.F5.B!
#C [[ GRID ]]

The following could be interpreted in an implementable way, but it's unclear whether that matches the intended idea:

Code: Select all

x = 17, y = 5, rule = LifeHistory
2.D5.F5.B$.3D5.F3.BCB$2DC2D.5F.5B$.3D5.F3.3B$2.D5.F5.B!
#C [[ GRID ]]

Code: Select all

x = 23, y = 7, rule = LifeHistory
7B9.7B$7B9.7B$3BD3B4.F4.7B$2B3D2B5.F3.3BC3B$B2DC2DB2.5F2.7B$2B3D2B5.F
3.7B$3BD3B4.F4.7B!
#C [[ GRID ]]

There may be other plausible interpretations, some of which might be implementable.

[Aleph]

Maybe this was intended?

Code: Select all

x = 14, y = 5, rule = LifeHistory
2.B5.D$.3B5.D$5B.5D2.A$.BAB5.D$2.B5.D!

[islptng]

Maybe this was intended?

Code: Select all

x = 14, y = 5, rule = LifeHistory
2.B5.D$.3B5.D$5B.5D2.A$.BAB5.D$2.B5.D!

If so, then:

Neighborhood weights: (in decimal; 45 = (2d)16)

Code: Select all

00 00 01 00 00
00 05 05 05 00
01 05 00 05 01
00 05 45 05 00
00 00 01 00 00

CGoL is R2,C0,S10-19,50-59,B15-19,55-59,NW00000100000005050500010500050100052D05000000010000; To add that, add B45.

Code: Select all

x = 22, y = 3, rule = R2,C0,S10-19,50-59,B15-19,45,55-59,NW00000100000005050500010500050100052D05000000010000
3o$2bo18bo$bo!

[confocaloid]

Here is what I got; there may be bugs in CGoL:

Code: Select all

x = 88, y = 36, rule = R3,C0,S21-41,49-76,84-104,126-132,B7,21,35-41,63-76,91-104,126-132,NW000000000000000000000000000000000E2A0E000000002A002A000000012A072A01000000010101000000000001000000
3b2o$3b2o2$34b2o$34b2o5$87bo$85b3o$86bo$12b3o7b2o$12bo8bobo$13bo9bo7$
12bo9bo$12bobo8bo$12b2o7b3o8$2o$2o2$31b2o$31b2o!
#C [[ GRID ZOOM 4 THEME MCell ]]

To get plain CGoL, remove the birth conditions B7 and B21. I used the following weighted neighbourhood (the weights are given in decimal):

Code: Select all

-- -- -- -- -- -- --
-- -- -- -- -- -- --
-- -- 14 42 14 -- --
-- -- 42 -- 42 -- --
-- 01 42 07 42 01 --
-- -- 01 01 01 -- --
-- -- -- 01 -- -- --

Life, except: [...]

[...][...]

The following could be interpreted in an implementable way, but it's unclear whether that matches the intended idea:

Code: Select all

x = 17, y = 5, rule = LifeHistory
2.D5.F5.B$.3D5.F3.BCB$2DC2D.5F.5B$.3D5.F3.3B$2.D5.F5.B!
#C [[ GRID ]]

Code: Select all

x = 23, y = 7, rule = LifeHistory
7B9.7B$7B9.7B$3BD3B4.F4.7B$2B3D2B5.F3.3BC3B$B2DC2DB2.5F2.7B$2B3D2B5.F
3.7B$3BD3B4.F4.7B!
#C [[ GRID ]]

[...]

[b-engine]

CGoL is R2,C0,S10-19,50-59,B15-19,55-59,NW00000100000005050500010500050100052D05000000010000; To add that, add B45.

Code: Select all

x = 22, y = 3, rule = R2,C0,S10-19,50-59,B15-19,45,55-59,NW00000100000005050500010500050100052D05000000010000
3o$2bo18bo$bo!

But there are stuffs like this:

Code: Select all

x = 4, y = 6, rule = R2,C2,S10-19,50-59,B15-19,45,55-59,NW00000100000005050500010500050100052d05000000010000
bo2$b2o$b2o$o2bo$o2bo!

[LuveelVoom]

There are indeed bugs.

Code: Select all

x = 20, y = 9, rule = R3,C2,S21-41,49-76,84-104,126-132,B7,21,35-41,63-76,91-104,126-132,NW000000000000000000000000000000000e2a0e000000002a002a000000012a072a01000000010101000000000001000000
3$7bo8bo2$8b8o$8bo6bo!

[islptng]

Continuing on LuveelVoom's request, I want:

Code: Select all

x = 16, y = 11, rule = LifeHistory
3.B5.D$2.3B5.D4.A$.2BA2B.5D3.D$2.3B5.D$3.B5.D2$2.2B5.D$.4B5.D$2B2A2B.
5D2.2D$.4B5.D3.2A$2.2B5.D!

i.e. Dot goes up, and domino goes down.
This lets horizontal HWSS become a rake too.

[confocaloid]

Continuing on LuveelVoom's request, I want:

Code: Select all

x = 16, y = 11, rule = LifeHistory
3.B5.D$2.3B5.D4.A$.2BA2B.5D3.D$2.3B5.D$3.B5.D2$2.2B5.D$.4B5.D$2B2A2B.
5D2.2D$.4B5.D3.2A$2.2B5.D!

i.e. Dot goes up, and domino goes down.
This lets horizontal HWSS become a rake too.

The following gives *only* the "domino goes down" part; there's no "dot goes up".
Even then, it doesn't quite implement the "domino goes down" part in the same sense in which "dot goes up" was implemented earlier in this discussion.
(I slightly modified which neighbours are checked, to avoid the need to distinguish between the possibility "domino to the left of the middle column" and the possibility "domino to the right of the middle column", because having to distinguish those two possibilities would exceed the limitations of the current implementation in Golly/LifeViewer, as far as I can tell). See pattern comments (Help/Comments in LifeViewer, View/Pattern Info in Golly).

Code: Select all

#C Two-state non-isotropic cellular automaton, defined using the following weighted neighbourhood (weights given in decimal):
#C
#C -- -- 01 01 01 -- --
#C -- -- 01 01 01 -- --
#C 01 01 13 39 13 01 01
#C -- 01 78 -- 78 01 --
#C -- -- 78 78 78 -- --
#C -- -- -- -- -- -- --
#C -- -- -- -- -- -- --
#C 
#C * (the birth condition B52) A currently-dead cell, with precisely one currently-alive weight-39 neighbour, with precisely one currently-alive weight-13 neighbour, and without any currently-alive weight-78 or weight-1 neighbours.
#C
#C * Otherwise, let N be the number of alive neighbours whose weight exceeds 1.
#C A currently-dead cell becomes alive if N == 3.
#C A currently-alive cell remains alive if 2 <= N <= 3.
#C Otherwise, a currently-alive cell dies, and a currently-dead cell remains dead.
x = 132, y = 39, rule = R3,C0,S26-38,52-77,91-142,156-181,195-207,234-246,B52,65-77,104-116,130-142,169-181,195-207,234-246,NW000001010100000000010101000001010D270D010100014E004E010000004E4E4E00000000000000000000000000000000
2bo15bo$2ob2o11b2ob2o$3b3o9b3o$3bo3b2o3b2o3bo$4bo3bo3bo3bo$31bo19bo$6b
3o3b3o15b2o19b2o$30bo2bo4b2o3b2o4bo2bo$7bo5bo20bob2obo3bob2obo$7bobobo
bo19bo15bo58bo$7bo5bo21b4o5b4o43bo2bo11bo3bo16b2o$9bobo27b2ob2o51bo15b
o13bo4bo$8b2ob2o78bo3bo10bo4bo19bo$6bo2bobo2bo25bobo49b4o11b5o13bo5bo$
4b2obobobobob2o22bo3bo82b6o$5bobobobobobo19b5o3b5o25bo$9bobo22b2o2b2o
3b2o2b2o24bo$5b2o2bobo2b2o18bo5bobo5bo24bo$4bo3bo3bo3bo15b4o2bobobobo
2b4o22bo$6bo7bo24bo3bo29bo$4bo11bo56bo$3bo13bo55bo$3bo13bo55bo$3bo2bo
7bo2bo55bo$6bo7bo58bo$5bobo5bobo$6bo7bo$3b2o11b2o$3b2o11b2o16bo15bo$3b
2o11b2o15b3o13b3o$5bo9bo23b3ob3o$5bo9bo15bo6bobo3bobo6bo35bo$5b2o7b2o
14bobobo3bo7bo3bobobo35bo$5b2o7b2o17bob2o2b3ob3o2b2obo36b3o$7bo5bo16bo
23bo$7bo5bo16b2o4b2o9b2o4b2o$8bo3bo17b2o4b2o9b2o4b2o49bobo$7bo5bo90b2o
$105bo!

Trying to implement both "dot goes up" and "domino goes down" leads to the following sketch:

Code: Select all

-- -- uu uu uu -- --
-- -- uu uu uu -- --
uu uu yy tt yy uu uu
-- uu zz -- zz uu --
-- ww zz xx zz ww --
-- -- ww ww ww -- --
-- -- -- ww -- -- --

where

• xx, yy, zz, tt form the Moore neighbourhood, to allow this to be "close to CGoL";
• tt, ww, zz form a region around the dot ('xx') to allow checking conditions for "upwards movement";
• uu, xx, yy, zz form a region around the expected domino (which would consist of one alive 'tt' cell and one alive 'yy' cell) to allow checking conditions for "downwards movement"

and (as far as I can tell) any workable assignment of weights instead of xx, yy, zz, tt, uu, ww would have some weights exceeding 127, which is the current limit on what the weight of a neighbour can be in Golly/LifeViewer.

That is, there's no theoretical impossibility for doing something that would likely count as an answer to your request, but it cannot be done in some currently-supported way in Golly/LifeViewer.

[CARuler]

Life, except:

Code: Select all

 x = 14, y = 5, rule = LifeHistory
2.B5.D$.3B5.D3.A$2BA2B.5D2.B$.3B5.D$2.B5.D!

but only upwards (the rule is anisotropic.)

dot gun

Code: Select all

x = 24, y = 9, rule = R3,C2,S21-41,49-76,84-104,126-132,B7,21,35-41,63-76,91-104,126-132,NW000000000000000000000000000000000e2a0e000000002a002a000000012a072a01000000010101000000000001000000
11b2o$4bo3bo6bo3bo$3bobo12bobo$3bobo12bobo$2obobob10obobob2o$2obo16bo
b2o$3bo16bo$3bobo4b2obo4bobo$4b2o4bob2o4b2o!

caped

Code: Select all

x = 24, y = 117, rule = R3,C2,S21-41,49-76,84-104,126-132,B7,21,35-41,63-76,91-104,126-132,NW000000000000000000000000000000000e2a0e000000002a002a000000012a072a01000000010101000000000001000000
5bo12bo$4bobo10bobo$5bo12bo106$11b2o$4bo3bo6bo3bo$3bobo12bobo$3bobo12b
obo$2obobob10obobob2o$2obo16bob2o$3bo16bo$3bobo4b2obo4bobo$4b2o4bob2o
4b2o!

[PHPBB12345]

dot gun

Code: Select all

x = 24, y = 9, rule = R3,C2,S21-41,49-76,84-104,126-132,B7,21,35-41,63-76,91-104,126-132,NW000000000000000000000000000000000e2a0e000000002a002a000000012a072a01000000010101000000000001000000
11b2o$4bo3bo6bo3bo$3bobo12bobo$3bobo12bobo$2obobob10obobob2o$2obo16bo
b2o$3bo16bo$3bobo4b2obo4bobo$4b2o4bob2o4b2o!

caped

Code: Select all

x = 24, y = 117, rule = R3,C2,S21-41,49-76,84-104,126-132,B7,21,35-41,63-76,91-104,126-132,NW000000000000000000000000000000000e2a0e000000002a002a000000012a072a01000000010101000000000001000000
5bo12bo$4bobo10bobo$5bo12bo106$11b2o$4bo3bo6bo3bo$3bobo12bobo$3bobo12b
obo$2obobob10obobob2o$2obo16bob2o$3bo16bo$3bobo4b2obo4bobo$4b2o4bob2o
4b2o!

dot eater:

Code: Select all

x = 3, y = 14, rule = R3,C0,S21-41,49-76,84-104,126-132,B7,21,35-41,63-76,91-104,126-132,NW000000000000000000000000000000000E2A0E000000002A002A000000012A072A01000000010101000000000001000000
bo$obo$bo11$bo!

[CARuler]

lane shift

Code: Select all

x = 8, y = 22, rule = R3,C2,S26-38,52-77,91-142,156-181,195-207,234-246,B52,65-77,104-116,130-142,169-181,195-207,234-246,NW000001010100000000010101000001010d270d010100014e004e010000004e4e4e00000000000000000000000000000000
2o6$3bo$2bobo$3bo11$6bo$5bobo$6bo!

edit:
delay

Code: Select all

x = 55, y = 9, rule = R3,C2,S26-38,52-77,91-142,156-181,195-207,234-246,B52,65-77,104-116,130-142,169-181,195-207,234-246,NW000001010100000000010101000001010d270d010100014e004e010000004e4e4e00000000000000000000000000000000
2o27b2o19b2o6$3b2o27bo20bo$2bobo26bobo18bobo$3bo28bo20b2o!

edit2:
smaller delay

Code: Select all

x = 3, y = 12, rule = R3,C2,S26-38,52-77,91-142,156-181,195-207,234-246,B52,65-77,104-116,130-142,169-181,195-207,234-246,NW000001010100000000010101000001010d270d010100014e004e010000004e4e4e00000000000000000000000000000000
b2o9$bo$obo$bo!

edit3:
lane shift with blinker

Code: Select all

x = 3, y = 12, rule = R3,C2,S26-38,52-77,91-142,156-181,195-207,234-246,B52,65-77,104-116,130-142,169-181,195-207,234-246,NW000001010100000000010101000001010d270d010100014e004e010000004e4e4e00000000000000000000000000000000
b2o9$bo$obo$2o!

can this rule be proven turning complete
edit4:
splitter

Code: Select all

x = 37, y = 12, rule = R3,C2,S26-38,52-77,91-142,156-181,195-207,234-246,B52,65-77,104-116,130-142,169-181,195-207,234-246,NW000001010100000000010101000001010d270d010100014e004e010000004e4e4e00000000000000000000000000000000
7b2o26b2o9$bo5bo21bo5bo$obo3bobo19bobo3bobo$bo4b2o20b2o4b2o!

edit5:

Code: Select all

x = 339, y = 21, rule = R3,C2,S26-38,52-77,91-142,156-181,195-207,234-246,B52,65-77,104-116,130-142,169-181,195-207,234-246,NW000001010100000000010101000001010d270d010100014e004e010000004e4e4e00000000000000000000000000000000
7b2o$26b2o14b2o$60b2o25b2o20b2o$132b2o30b2o18b2o3$216b2o$241b2o21b2o16b
2o$307b2o26b2o$2o5bo$obo3bobo17bo15bo278b2o$bo4b2o11b2o4bobo8b2o3bobo
11b2o3bo26bo21bo$18bobo4b2o8bobo3b2o11bobo2bobo18bo5bobo14bo4bobo14bo
6bo26bo4bo19bo$19bo16bo18bo3b2o18bobo4b2o14bobo3b2o14bobo4bobo24bobo2b
obo10b2o5bobo$80b2o21b2o20b2o4b2o25b2o3b2o11bobo4b2o$177bo38bo$210b2o
3bobo23bo22bo17bo$210b2o3b2o19b2o2bobo20bobo15bobo22b2o25b2o2b2o$236b
2o2b2o17b2o2b2o11b2o3b2o23b2o25b2o2b2o$259b2o15b2o40b2o3b2o$318b2o3b2o
!

edit6:

Code: Select all

x = 178, y = 22, rule = R3,C2,S21-41,49-76,84-104,126-132,B7,21,35-41,63-76,91-104,126-132,NW000000000000000000000000000000000e2a0e000000002a002a000000012a072a01000000010101000000000001000000
bo39bo13bo11b2o$obo25bo11bobo11bobo9bobo$obo24bobo11b2o12b2o10bo$bo26b
2o115b2o$144bo2bo$123b2o19bo2bo$122bo2bo19b2o$123b2o$175b2o$174bo2bo$
174bo2bo$175b2o2$2bo23bo16bo11bo$68bo2$124bo24bo5$177bo!

[confocaloid]

The descriptions of those "delays" and "lane shifts" need to mention explicitly that those are one-time components. It's destroyed when used.

Otherwise, if you don't tell "one-time" explicitly, then a reader would reasonably expect a stable delay device or a stable lane shifter, or at least a periodic component that would survive the interaction and self-recover to be able to process as many input pulses as desired.


Also:

[...] dot eater: [...]

Already known; read the preceding discussion. [...]

[...] 4. This is an academic forum, not a chat or microblogging platform. Please spend some time doing some research to familiarize yourself with what is and isn't already known [...] before posting your discoveries. [...]

[hotcrystal0]

dot gun

Code: Select all

x = 24, y = 9, rule = R3,C2,S21-41,49-76,84-104,126-132,B7,21,35-41,63-76,91-104,126-132,NW000000000000000000000000000000000e2a0e000000002a002a000000012a072a01000000010101000000000001000000
11b2o$4bo3bo6bo3bo$3bobo12bobo$3bobo12bobo$2obobob10obobob2o$2obo16bo
b2o$3bo16bo$3bobo4b2obo4bobo$4b2o4bob2o4b2o!

I have three barrels:

Code: Select all

x = 23, y = 11, rule = R3,C2,S21-41,49-76,84-104,126-132,B7,21,35-41,63-76,91-104,126-132,NW000000000000000000000000000000000e2a0e000000002a002a000000012a072a01000000010101000000000001000000
11bo$4bo3bo5bo3bo$3bobo11bobo$3bobo11bobo$2obobob9obobob2o$2obo15bob2o
$3bo15bo$3bobo4bobo4bobo$4b2o4b2obo3b2o$13bo$13b2o!

[b-engine]

Life, but the two cells in a single duoplet that detects nothing within its range-4 neighbourhood (expect other duoplets) would replicate itself, and immediately disintegrate into ashes or nothing if detecting anything else.

Code: Select all

x = 30, y = 10, rule = LifeHistory
22.7B$.7B6.E7.8B$8B6.2E4.10B$8B6.3E3.5BA4B$4BA3B2.8E2.5BDA3B$3BA4B2.8E
2.3BAD5B$8B6.3E3.4BA5B$8B6.2E4.10B$7B7.E5.8B$21.7B!
[[ VIEWONLY ]]

EDIT: This means that all off cells adjacent to the two cells of the duoplet and detect nothing else within its neighbourhood turns on.

[confocaloid]

Life, but a single duoplet that detects nothing within its range-4 neighbourhood (expect other duoplets) would replicate itself, and immediately disintegrate into ashes or nothing if detecting anything else. [...]

Similar to the previous case, the parts

"...duoplet that detects..." "...(except other duoplets)..."

make it unclear how would one implement this as a cellular automaton.

In cellular automata (such as Conway's Life, and you wrote "Life, but...") the only "entities" that can "detect" something and react to that within one clock-tick ("immediately") are the single cells. A single cell can "detect" a specific cell condition (i.e., detect an equivalence class of neighbourhood configurations, with the equivalence relation depending on the specific CA type), and the cell can "respond" to that cell condition by either changing its own state to some other specific state or remaining unchanged in the next generation.

A duoplet isn't a single cell.