Rule request thread

[CARuler]

Life but if a dead cell is surrounded by 7 live cells it becomes a fire cell, a fire live cell connected to any number of fire cells then it becomes a fire cell, all fire cells die

what is the interaction between a fire cell and a live cell, and a fire live cell and a live cell? Also did you mean if a dead cell is surrounded by 7 live cells it becomes a fire live cell?

if a dead cell is surrounded by 7 live cells it becomes a fire cell, if any live cell has any fire cell neighbors it becomes a fire cell and no matter the neighbors a fire cell always dies

[pifricted]

if a dead cell is surrounded by 7 live cells it becomes a fire cell, if any live cell has any fire cell neighbors it becomes a fire cell and no matter the neighbors a fire cell always dies

Will dead cells birth when there are any fire cell neighbors?

[CARuler]

if a dead cell is surrounded by 7 live cells it becomes a fire cell, if any live cell has any fire cell neighbors it becomes a fire cell and no matter the neighbors a fire cell always dies

Will dead cells birth when there are any fire cell neighbors?

good question, I didn't think about that but birth conditions are treat fire cells like dead cells

[pifricted]

FireCells

When dead cells don't birth when there are any fire cell neighbors:

B-hep. is a c/2 ship, and pulsar is really common.

Code: Select all

x = 55, y = 4, rule = FireCells
2.A14.A29.A$.3A12.A.A27.A.A4.2A$2A.A12.A.A27.A.A4.2A$16.2A28.2A!
@RULE FireCells
@COLORS
1 255 255 255
2 255 0 0
@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
var a={0,1,2}
var q=a
var w=a
var e=a
var r=a
var t=a
var y=a
var u=a
var b={1,2}
var s=b
var d=b
var f=b
var g=b
var h=b
var j=b
var k=b
1,2,a,q,w,e,r,t,y,2
0,1,1,1,0,0,0,0,0,1
1,1,1,0,0,0,0,0,0,1
1,1,1,1,0,0,0,0,0,1
0,1,1,1,1,1,1,1,0,2
b,a,q,w,e,r,t,y,u,0

When dead cells birth when there are one or no fire cell neighbors:

Code: Select all

x = 4, y = 3, rule = FireCells
2.A$.3A$2A.A!
@RULE FireCells
@COLORS
1 255 255 255
2 255 0 0
@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
var a={0,1,2}
var q=a
var w=a
var e=a
var r=a
var t=a
var y=a
var u=a
var b={1,2}
var s=b
var d=b
var f=b
var g=b
var h=b
var j=b
var k=b
var z={0,2}
var x=z
var c=z
var v=z
var n=z
var m=z
var l=z
1,2,a,q,w,e,r,t,y,2
0,1,1,1,z,0,0,0,0,1
1,1,1,0,0,0,0,0,0,1
1,1,1,1,0,0,0,0,0,1
0,1,1,1,1,1,1,1,0,2
b,a,q,w,e,r,t,y,u,0

[LuveelVoom]

Ulam's Bones: 3 state generations. A cell is born if it has exactly one state-1 and one state-2 neighbor (0 is the void.) There is no survive condition, cells progress to the next state no matter what.
Regionality: 4 states. State 0 is "CGOL void", state 1 is "B34/S34 void", state 2 is a living cgol cell, and state 3 is a living B34/S34 cell. state 2 turns into state 3 when entering state 1, and the other way around as well. state 1 behaves like CGOL except in 3x3 blocks. If it is less than a 3x3, it immediately dies, but this can only happen in the first generation of a pattern. A living cell (states 2 or 3) or a void cell (0,1) behaves like the corresponding rule, so for example a cell on the boundry of state 1 but in state 0 would behave like cgol (i explained this pretty badly, but the concept is "what if rules were variant across time and space") (this can of course be generalized to any set of rules and any size blocks)
LifeHistory Mod 2 +1: Lifehistory, except when a history cell is occupied it becomes a different-history cell and vice versa, so history cells have different states depending on whether they have been occupied an even or odd number of times (can obviously be generalized)

[CARuler]

variant of Ulam's bones

Code: Select all

# You can save the pattern into this box with Settings/Pattern/Save or Ctrl-S.
x = 7, y = 3, rule = Ulams BonesV
o3b3o$3o2bo$bo!
@RULE Ulams BonesV
@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
var a = {0,1,2}
var b = a
var c = a
var d = a
var e = a
var f = a
var g = a
var h = a
0,1,2,0,0,0,0,0,0,1
0,1,2,2,0,0,0,0,0,2
0,1,1,2,0,0,0,0,0,2

#default
1,a,b,c,d,e,f,g,h,0
2,a,b,c,d,e,f,g,h,0

edit:
ulam's bones

Code: Select all

# You can save the pattern into this box with Settings/Pattern/Save or Ctrl-S.
x = 7, y = 3, rule = Ulams Bones
o3b3o$3o2bo$bo!
@RULE Ulams Bones
@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
var a = {0,1,2}
var b = a
var c = a
var d = a
var e = a
var f = a
var g = a
var h = a
0,1,2,0,0,0,0,0,0,1


#default
1,a,b,c,d,e,f,g,h,2
2,a,b,c,d,e,f,g,h,0

[confocaloid]

Ulam's Bones: 3 state generations. A cell is born if it has exactly one state-1 and one state-2 neighbor (0 is the void.) There is no survive condition, cells progress to the next state no matter what.
[...]

Does this work as intended? Each state-1 neighbour is weighted x9, each state-2 neighbour is weighted x1, each neighbour place is weighted x1, and the birth condition is encoded "B10" (10 = 1 + 9). No separate file needed.

Code: Select all

x = 20, y = 3, rule = R1,C3,S,B10,NW111101111,091:T64,64
2.B16.A$17.B$A!

edit:

[...]
LifeHistory Mod 2 +1: Lifehistory, except when a history cell is occupied it becomes a different-history cell and vice versa, so history cells have different states depending on whether they have been occupied an even or odd number of times (can obviously be generalized)

I think one would also need two different "alive" cellstates (so that the information about which "history" state should be used next can be kept in an alive cell).

I can see at least two ways to interpret the request:

• (1) every single generation where some cell is alive counts as "one time", to decide which history cellstate should be used when the cell dies,
• (2) every maximal sequence of consecutive generations where some cell stays alive counts as "one time".

In the case (1), the following should work:

Code: Select all

x = 28, y = 1, rule = testing_LHmod2plus1_post197679_version1
4A5.3A6.10A!
#C [[ GRID ZOOM 12 ]]

@RULE testing_LHmod2plus1_post197679_version1

0 = dead, will become 1 if born
1 = alive A, will become 2 if it dies one tick later
2 = history A, will become 3 if born
3 = alive B, will become 4 if it dies one tick later
4 = history B, will become 1 if born

@COLORS
0  40  40  40
1  40 240  40
2  40  80  40
3  40  40 240
4  40  40  80

@TABLE
n_states:5
neighborhood:Moore
symmetries:permute

var L={1,3}
var L1=L
var L2=L
var L3=L
var D={0,2,4}
var D1=D
var D2=D
var D3=D
var D4=D
var D5=D
var X={0,1,2,3,4}
var X1=X
var X2=X
var X3=X
var X4=X
var X5=X
var X6=X
var X7=X
var X8=X

# birth rules:
0, L1,L2,L3,D1,D2,D3,D4,D5, 1
2, L1,L2,L3,D1,D2,D3,D4,D5, 3
4, L1,L2,L3,D1,D2,D3,D4,D5, 1

# survival rules:
1, L1,L2, X,D1,D2,D3,D4,D5, 3
3, L1,L2, X,D1,D2,D3,D4,D5, 1

# death rules:
1, X1,X2,X3,X4,X5,X6,X7,X8, 2
3, X1,X2,X3,X4,X5,X6,X7,X8, 4

In the case (2), the following should work:

Code: Select all

x = 28, y = 1, rule = testing_LHmod2plus1_post197679_version2
4A5.3A6.10A!
#C [[ GRID ZOOM 12 ]]

@RULE testing_LHmod2plus1_post197679_version2

0 = dead, will become 1 if born
1 = alive A, will become 2 if it dies one tick later
2 = history A, will become 3 if born
3 = alive B, will become 4 if it dies one tick later
4 = history B, will become 1 if born

@COLORS
0  40  40  40
1  40 240  40
2  40  80  40
3  40  40 240
4  40  40  80

@TABLE
n_states:5
neighborhood:Moore
symmetries:permute

var L={1,3}
var L1=L
var L2=L
var L3=L
var D={0,2,4}
var D1=D
var D2=D
var D3=D
var D4=D
var D5=D
var X={0,1,2,3,4}
var X1=X
var X2=X
var X3=X
var X4=X
var X5=X
var X6=X
var X7=X
var X8=X

# birth rules:
0, L1,L2,L3,D1,D2,D3,D4,D5, 1
2, L1,L2,L3,D1,D2,D3,D4,D5, 3
4, L1,L2,L3,D1,D2,D3,D4,D5, 1

# survival rules:
1, L1,L2, X,D1,D2,D3,D4,D5, 1
3, L1,L2, X,D1,D2,D3,D4,D5, 3

# death rules:
1, X1,X2,X3,X4,X5,X6,X7,X8, 2
3, X1,X2,X3,X4,X5,X6,X7,X8, 4

[CARuler]

some sthuff in Ulams BonesV

Code: Select all

x = 346, y = 169, rule = Ulams BonesV
4.A$2.A.B$A.B.B$B.B$B.B9.A$A.B7.A.B.A$2.A7.B.B.B.A$14.B.B$8.A5.B.B$14.
A.A22$261.ABA2$260.A3BA37$323.B.B$321.B5.B$319.A9.A$319.B9.B$325.B3.B
$325.B3.A$325.B$325.B.A$325.A.B.A9.B.B$327.B.B.A11.B$329.B.B.A11.A$329.
A3.B5.A5.B$329.A3.B5.A5.B$329.A3.A11.A$343.B$339.B.B16$64.A$64.B$64.A
60$139.B.B$137.B5.B$135.B9.A$133.A3.B7.B$133.B2.2A3.B3.B$133.A.B5.A3.
A!




@RULE Ulams BonesV
@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
var a = {0,1,2}
var b = a
var c = a
var d = a
var e = a
var f = a
var g = a
var h = a
0,1,2,0,0,0,0,0,0,1
0,1,2,2,0,0,0,0,0,2
0,1,1,2,0,0,0,0,0,2

#default
1,a,b,c,d,e,f,g,h,0
2,a,b,c,d,e,f,g,h,0

[unname4798]

Variant of a variant of Ulam's Bones:

Code: Select all

#C [[ RANDOMIZE ]]
#R Ulams_BonesVV
!
@RULE Ulams_BonesVV
@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
var a = {0,1,2}
var b = a
var c = a
var d = a
var e = a
var f = a
var g = a
var h = a
var i = a
0,1,2,0,0,0,0,0,0,1
0,1,2,2,0,0,0,0,0,2
0,1,1,2,0,0,0,0,0,2
0,2,0,0,0,0,0,0,0,1
#default
i,a,b,c,d,e,f,g,h,0

[CARuler]

Regionality: 4 states. State 0 is "CGOL void", state 1 is "B34/S34 void", state 2 is a living cgol cell, and state 3 is a living B34/S34 cell. state 2 turns into state 3 when entering state 1, and the other way around as well. state 1 behaves like CGOL except in 3x3 blocks. If it is less than a 3x3, it immediately dies, but this can only happen in the first generation of a pattern. A living cell (states 2 or 3) or a void cell (0,1) behaves like the corresponding rule, so for example a cell on the boundry of state 1 but in state 0 would behave like cgol (i explained this pretty badly, but the concept is "what if rules were variant across time and space") (this can of course be generalized to any set of rules and any size blocks)

i found the description a bit confusing so heres a variant

Code: Select all

# You can save the pattern into this box with Settings/Pattern/Save or Ctrl-S.
x = 7, y = 3, rule = RegionalityV
o3b3o$3o2bo$bo!
@RULE RegionalityV
@COLORS
0   0   0   0
1  48  48  48
2 255 255 255
3 100   0 255
@NAMES
0 void
1 b34/s34 void
2 cgol
3 b34/s34
@TABLE
n_states:4
neighborhood:Moore
symmetries:permute
var a = {0,1,2,3}
var b = a
var c = a
var d = a
var e = a
var f = a
var g = a
var h = a
var i = {0,1}
var j = i
var k = i
var l = i
var m = i
var n = i
var o = i
var p = i
var q = {2,3}
var r = q
var s = q
var t = q
var u = q
var v = q
var w = q
var x = q
0,q,r,s,i,j,k,l,m,2
1,q,r,s,i,j,k,l,m,3
1,q,r,s,t,i,j,k,l,3
2,q,r,i,j,k,l,m,n,2
2,q,r,s,i,j,k,l,m,2
3,q,r,s,i,j,k,l,m,3
3,q,r,s,t,i,j,k,l,3

#defaults
2,a,b,c,d,e,f,g,h,0
3,a,b,c,d,e,f,g,h,1

[confocaloid]

It would be relatively straightforward to make a 4-state ruletable implementing the concept "what if the rules were variant across space". Meanings of the cellstates would be as requested. However, boundaries of regions would stay fixed (0/2 would always remain 0/2; 1/3 would always remain 1/3).

[...] state 1 behaves like CGOL except in 3x3 blocks. If it is less than a 3x3, it immediately dies, but this can only happen in the first generation of a pattern. [...] the concept is "what if rules were variant across time and space") [...]

The request seems to leave the possibility of region boundaries changing over time, but it is unclear when and how that should happen, and I do not understand the intended idea behind 3x3 blocks.

[LuveelVoom]

Would there be update order issues with having the regions be moving? If not, why couldn’t it be done?
About LHM2: the first interpretation is correct, yes; a cell’s history color is based on the number of gens it was occupied for, not the number of times it was occupied and unoccupied.
Also ulam’s bones came from a book about ca I was reading which mentioned that ulam and someone else who I can’t remember came up with it in a paper (not sure if the story is true but can be pretty easily checked) and the paper had a pattern called the dogbone, so I thought ulam’s bones was a fitting name. Does it have any spaceships?

Also, regionalityV has a small gun family involving a glider hitting a block and causing an over-unity reaction, which, when the block is placed in the proper place 4 times, creates a gun; on mobile atm so can’t send but it took me like 5 min to find so shouldn’t be hard

[confocaloid]

Would there be update order issues with having the regions be moving? If not, why couldn’t it be done? [...]

I think that could be done, once it's clear just how the regions are supposed to move, but I don't understand the quoted parts.
"state 2 turns into state 3 when entering state 1" is unclear, since a single cell cannot at the same time turn into state 3 and enter state 1.
"state 1 behaves like CGOL..." seems to contradict the meaning of state 1 as "B34/S34 void".
"... except in 3x3 blocks. If it is less than a 3x3, ..." is unclear, what is the underlying idea behind those blocks?

[...] state 2 turns into state 3 when entering state 1, and the other way around as well. state 1 behaves like CGOL except in 3x3 blocks. If it is less than a 3x3, it immediately dies, but this can only happen in the first generation of a pattern. [...]

[LuveelVoom]

The 34life blocks behave as CGOL except in a 3x3 pattern, so they could, for example, form a Sir Robin at 3x scale where cells inside it behave as b34/s34.

[confocaloid]

The 34life blocks behave as CGOL except in a 3x3 pattern, so they could, for example, form a Sir Robin at 3x scale where cells inside it behave as b34/s34.

So far, I do not understand the intended idea. It is possible that I might be missing something obvious here. Some illustrative examples (of what is the desired behaviour / what are the desired update rules) could help here.

[WhiteHawk]

Maybe this already exists.

I would like a rule with 3 live states, one which just simulates life, another which simulates life except it can be turned on if surrounded by eight live cells, and a third state which can be kept on if surrounded by eight live cells. In essence, a specialized Life-Pedestrian Life-EightLife 3-way simulator.

[LuveelVoom]

meta life, four states: 0 is void, 1 is life, 2 is 3-4 life, and 3 is life+3-4. 3-4 behaves normally in the background and doesn’t interact with life (hence the third state), but when 6 life cells are around void or life it becomes 3-4 life or state 3, and when 6 3-4 cells are around void or 3-4 life it becomes life or state 3. State 3 cells count for both but are otherwise just there to allow cells of two types to pass over each other.

[confocaloid]

meta life, four states: 0 is void, 1 is life, 2 is 3-4 life, and 3 is life+3-4. 3-4 behaves normally in the background and doesn’t interact with life (hence the third state), but when 6 life cells are around void or life it becomes 3-4 life or state 3, and when 6 3-4 cells are around void or 3-4 life it becomes life or state 3. State 3 cells count for both but are otherwise just there to allow cells of two types to pass over each other.

There is an internal contradiction in the request, between the part "3-4 behaves normally in the background and doesn’t interact with life" and the later parts that require interactions between the "3-4 life" universe and the CGoL universe.

There is also rather confusing ambiguity in how 'life' or '3-4 cells' is used, since apparently either of that might be intended to mean either a single specific cellstate or a pair of two distinct cellstates.

I do not know yet what is the intended way of resolving those issues.
However, I will assume the following:

• There are two interacting two-state universes "on top of each other".
• Universe 1 follows rules that are "similar" to B3/S23 (with some exceptions stated below), with cellstates encoded as the lower bit (= state mod 2).
• Universe 2 follows rules that are "similar" to B34/S34 (with some exceptions stated below), with cellstates encoded as the higher bit (= state div 2).
• If a cell is currently dead in universe 2 and has precisely 6 alive neighbours in universe 1, then the cell will become alive in universe 2 one tick later. (This rule lets universe 1 affect universe 2.)
• If a cell is currently dead in universe 1 and has precisely 6 alive neighbours in universe 2, then the cell will become alive in universe 1 one tick later. (This rule lets universe 2 affect universe 1.)

Code: Select all

x = 93, y = 93, rule = Test_related_to_post198039
31.A29.A$30.3A27.3A$32.A27.A28$.A89.A$2A89.2A$.2A87.2A28$.2A87.2A$2A
89.2A$.A89.A28$32.A27.A$30.3A27.3A$31.A29.A!
#C [[ ZOOM 2 ]]

@RULE Test_related_to_post198039

https://conwaylife.com/forums/viewtopic.php?p=198041#p198041

@TREE

num_states=4
num_neighbors=8
num_nodes=183
1 0 0 0 0
2 0 0 0 0
1 0 1 0 1
2 0 2 0 2
3 1 3 1 3
1 1 1 1 1
2 2 5 2 5
3 3 6 3 6
1 2 2 2 2
2 0 0 8 8
1 2 3 2 3
2 0 2 8 10
3 1 3 9 11
1 3 3 3 3
2 2 5 10 13
3 3 6 11 14
4 4 7 12 15
2 5 0 5 0
3 6 17 6 17
2 5 0 13 8
3 6 17 14 19
4 7 18 15 20
2 8 8 8 8
2 8 10 8 10
3 9 11 22 23
2 10 13 10 13
3 11 14 23 25
4 12 15 24 26
2 13 8 13 8
3 14 19 25 28
4 15 20 26 29
5 16 21 27 30
3 17 1 17 1
3 17 1 19 9
4 18 32 20 33
3 19 9 28 22
4 20 33 29 35
5 21 34 30 36
2 8 8 0 0
2 8 10 0 2
3 22 23 38 39
2 10 13 2 5
3 23 25 39 41
4 24 26 40 42
2 13 8 5 0
3 25 28 41 44
4 26 29 42 45
5 27 30 43 46
3 28 22 44 38
4 29 35 45 48
5 30 36 46 49
6 31 37 47 50
1 2 2 0 0
2 0 52 0 52
3 1 53 1 53
2 0 52 8 8
3 1 53 9 55
4 32 54 33 56
3 9 55 22 22
4 33 56 35 58
5 34 57 36 59
2 8 8 0 52
3 22 22 38 61
4 35 58 48 62
5 36 59 49 63
6 37 60 50 64
1 1 0 1 0
2 0 0 66 66
2 0 2 66 5
3 38 39 67 68
2 2 5 5 5
3 39 41 68 70
4 40 42 69 71
2 5 0 5 66
3 41 44 70 73
4 42 45 71 74
5 43 46 72 75
3 44 38 73 67
4 45 48 74 77
5 46 49 75 78
6 47 50 76 79
1 3 2 1 0
2 0 52 66 81
3 38 61 67 82
4 48 62 77 83
5 49 63 78 84
6 50 64 79 85
7 51 65 80 86
2 52 0 52 0
3 53 88 53 88
2 52 0 8 8
3 53 88 55 90
4 54 89 56 91
3 55 90 22 22
4 56 91 58 93
5 57 92 59 94
2 8 8 52 0
3 22 22 61 96
4 58 93 62 97
5 59 94 63 98
6 60 95 64 99
2 52 0 81 66
3 61 96 82 101
4 62 97 83 102
5 63 98 84 103
6 64 99 85 104
7 65 100 86 105
2 66 66 0 0
2 66 5 0 2
3 67 68 107 108
2 5 5 2 5
3 68 70 108 110
4 69 71 109 111
2 5 66 5 0
3 70 73 110 113
4 71 74 111 114
5 72 75 112 115
3 73 67 113 107
4 74 77 114 117
5 75 78 115 118
6 76 79 116 119
2 66 81 0 52
3 67 82 107 121
4 77 83 117 122
5 78 84 118 123
6 79 85 119 124
7 80 86 120 125
2 81 66 52 0
3 82 101 121 127
4 83 102 122 128
5 84 103 123 129
6 85 104 124 130
7 86 105 125 131
8 87 106 126 132
3 88 1 88 1
3 88 1 90 9
4 89 134 91 135
3 90 9 22 22
4 91 135 93 137
5 92 136 94 138
3 22 22 96 38
4 93 137 97 140
5 94 138 98 141
6 95 139 99 142
3 96 38 101 67
4 97 140 102 144
5 98 141 103 145
6 99 142 104 146
7 100 143 105 147
3 101 67 127 107
4 102 144 128 149
5 103 145 129 150
6 104 146 130 151
7 105 147 131 152
8 106 148 132 153
3 107 108 1 3
3 108 110 3 6
4 109 111 155 156
3 110 113 6 17
4 111 114 156 158
5 112 115 157 159
3 113 107 17 1
4 114 117 158 161
5 115 118 159 162
6 116 119 160 163
3 107 121 1 53
4 117 122 161 165
5 118 123 162 166
6 119 124 163 167
7 120 125 164 168
3 121 127 53 88
4 122 128 165 170
5 123 129 166 171
6 124 130 167 172
7 125 131 168 173
8 126 132 169 174
3 127 107 88 1
4 128 149 170 176
5 129 150 171 177
6 130 151 172 178
7 131 152 173 179
8 132 153 174 180
9 133 154 175 181

[LuveelVoom]

There is an internal contradiction in the request, between the part "3-4 behaves normally in the background and doesn’t interact with life" and the later parts that require interactions between the "3-4 life" universe and the CGoL universe.

There is also rather confusing ambiguity in how 'life' or '3-4 cells' is used, since apparently either of that might be intended to mean either a single specific cellstate or a pair of two distinct cellstates.

I do not know yet what is the intended way of resolving those issues.
However, I will assume the following:

• There are two interacting two-state universes "on top of each other".
• Universe 1 follows rules that are "similar" to B3/S23 (with some exceptions stated below), with cellstates encoded as the lower bit (= state mod 2).
• Universe 2 follows rules that are "similar" to B34/S34 (with some exceptions stated below), with cellstates encoded as the higher bit (= state div 2).
• If a cell is currently dead in universe 2 and has precisely 6 alive neighbours in universe 1, then the cell will become alive in universe 2 one tick later. (This rule lets universe 1 affect universe 2.)
• If a cell is currently dead in universe 1 and has precisely 6 alive neighbours in universe 2, then the cell will become alive in universe 1 one tick later. (This rule lets universe 2 affect universe 1.)

Yes, this interpretation is correct. I’m not the best explainer, sorry. Maybe HighLife or some other life-like CA would be better than 3-4? Or even seeds for more sporadic behavior? The current rule looked very explosive.

[confocaloid]

[...] Maybe HighLife or some other life-like CA would be better than 3-4? Or even seeds for more sporadic behavior? The current rule looked very explosive.

Keeping the same "exception" rules, soups tend to explode even when B34/S34 is replaced by B3/S23 (making the ruleset symmetric with respect to the operation of exchanging the two universes).

It looks like soups tend to explode, even if B3/S13 or B3/S12 is used (instead of B34/S34). I think the following is the result of using B3/S13 (this pattern settles, but try random initial patterns instead):

Code: Select all

x = 93, y = 93, rule = Test_post198039
31.A29.A$30.3A27.3A$32.A27.A28$.A89.A$2A89.2A$.2A87.2A28$.2A87.2A$2A
89.2A$.A89.A28$32.A27.A$30.3A27.3A$31.A29.A!

@RULE Test_post198039

@TREE

num_states=4
num_neighbors=8
num_nodes=194
1 0 0 0 0
1 0 0 2 2
2 0 0 1 1
1 0 1 0 1
1 0 1 2 3
2 0 3 1 4
2 1 1 0 0
2 1 4 0 3
3 2 5 6 7
1 1 1 1 1
1 1 1 3 3
2 3 9 4 10
2 4 10 3 9
3 5 11 7 12
1 2 2 2 2
2 0 0 14 14
1 2 3 2 3
2 0 3 14 16
3 6 7 15 17
1 3 3 3 3
2 3 9 16 19
3 7 12 17 20
4 8 13 18 21
2 9 0 10 1
2 10 1 9 0
3 11 23 12 24
2 9 0 19 14
3 12 24 20 26
4 13 25 21 27
2 14 14 0 0
2 14 16 0 3
3 15 17 29 30
2 16 19 3 9
3 17 20 30 32
4 18 21 31 33
2 19 14 9 0
3 20 26 32 35
4 21 27 33 36
5 22 28 34 37
3 23 2 24 6
3 24 6 26 15
4 25 39 27 40
3 26 15 35 29
4 27 40 36 42
5 28 41 37 43
2 0 0 0 0
2 0 3 0 3
3 29 30 45 46
2 3 9 3 9
3 30 32 46 48
4 31 33 47 49
2 9 0 9 0
3 32 35 48 51
4 33 36 49 52
5 34 37 50 53
3 35 29 51 45
4 36 42 52 55
5 37 43 53 56
6 38 44 54 57
1 2 2 0 0
2 0 59 1 14
2 1 14 0 59
3 2 60 6 61
2 0 59 14 14
3 6 61 15 63
4 39 62 40 64
2 14 14 0 59
3 15 63 29 66
4 40 64 42 67
5 41 65 43 68
2 0 59 0 59
3 29 66 45 70
4 42 67 55 71
5 43 68 56 72
6 44 69 57 73
1 1 0 1 0
2 0 0 75 75
2 0 3 75 9
3 45 46 76 77
2 3 9 9 9
3 46 48 77 79
4 47 49 78 80
2 9 0 9 75
3 48 51 79 82
4 49 52 80 83
5 50 53 81 84
3 51 45 82 76
4 52 55 83 86
5 53 56 84 87
6 54 57 85 88
1 3 2 1 0
2 0 59 75 90
3 45 70 76 91
4 55 71 86 92
5 56 72 87 93
6 57 73 88 94
7 58 74 89 95
2 59 0 14 1
2 14 1 59 0
3 60 97 61 98
2 59 0 14 14
3 61 98 63 100
4 62 99 64 101
2 14 14 59 0
3 63 100 66 103
4 64 101 67 104
5 65 102 68 105
2 59 0 59 0
3 66 103 70 107
4 67 104 71 108
5 68 105 72 109
6 69 106 73 110
2 59 0 90 75
3 70 107 91 112
4 71 108 92 113
5 72 109 93 114
6 73 110 94 115
7 74 111 95 116
2 75 75 0 0
2 75 9 0 3
3 76 77 118 119
2 9 9 3 9
3 77 79 119 121
4 78 80 120 122
2 9 75 9 0
3 79 82 121 124
4 80 83 122 125
5 81 84 123 126
3 82 76 124 118
4 83 86 125 128
5 84 87 126 129
6 85 88 127 130
2 75 90 0 59
3 76 91 118 132
4 86 92 128 133
5 87 93 129 134
6 88 94 130 135
7 89 95 131 136
2 90 75 59 0
3 91 112 132 138
4 92 113 133 139
5 93 114 134 140
6 94 115 135 141
7 95 116 136 142
8 96 117 137 143
3 97 2 98 6
3 98 6 100 15
4 99 145 101 146
3 100 15 103 29
4 101 146 104 148
5 102 147 105 149
3 103 29 107 45
4 104 148 108 151
5 105 149 109 152
6 106 150 110 153
3 107 45 112 76
4 108 151 113 155
5 109 152 114 156
6 110 153 115 157
7 111 154 116 158
3 112 76 138 118
4 113 155 139 160
5 114 156 140 161
6 115 157 141 162
7 116 158 142 163
8 117 159 143 164
3 118 119 45 46
3 119 121 46 48
4 120 122 166 167
3 121 124 48 51
4 122 125 167 169
5 123 126 168 170
3 124 118 51 45
4 125 128 169 172
5 126 129 170 173
6 127 130 171 174
3 118 132 45 70
4 128 133 172 176
5 129 134 173 177
6 130 135 174 178
7 131 136 175 179
3 132 138 70 107
4 133 139 176 181
5 134 140 177 182
6 135 141 178 183
7 136 142 179 184
8 137 143 180 185
3 138 118 107 45
4 139 160 181 187
5 140 161 182 188
6 141 162 183 189
7 142 163 184 190
8 143 164 185 191
9 144 165 186 192

Edit: here is the result of using B3/S3 instead of B34/S34, which might happen to be more interesting:

Code: Select all

x = 221, y = 32, rule = Test_post198039
46.A$47.A$45.3A21.B15.B.B$67.2B.3B10.2B.3B15.B.2B$67.B4.B10.B18.2B.2B
$68.2B.B12.5B13.B$68.B.2B12.B2.B15.4B101.A$103.B2.2B101.A$207.3A9.A$
218.A$218.3A$56.2B$56.2B3$2A$.2A58.B$.A59.2B$62.B4$66.B$66.B.B$65.B.B
$67.B4$73.B$72.2B$74.B!

@RULE Test_post198039

@TREE

num_states=4
num_neighbors=8
num_nodes=179
1 0 0 0 0
2 0 0 0 0
1 0 1 0 1
2 0 2 0 2
3 1 3 1 3
1 1 1 1 1
2 2 5 2 5
3 3 6 3 6
1 2 2 2 2
2 0 0 8 8
1 2 3 2 3
2 0 2 8 10
3 1 3 9 11
1 3 3 3 3
2 2 5 10 13
3 3 6 11 14
4 4 7 12 15
2 5 0 5 0
3 6 17 6 17
2 5 0 13 8
3 6 17 14 19
4 7 18 15 20
2 8 8 0 0
2 8 10 0 2
3 9 11 22 23
2 10 13 2 5
3 11 14 23 25
4 12 15 24 26
2 13 8 5 0
3 14 19 25 28
4 15 20 26 29
5 16 21 27 30
3 17 1 17 1
3 17 1 19 9
4 18 32 20 33
3 19 9 28 22
4 20 33 29 35
5 21 34 30 36
3 22 23 1 3
3 23 25 3 6
4 24 26 38 39
3 25 28 6 17
4 26 29 39 41
5 27 30 40 42
3 28 22 17 1
4 29 35 41 44
5 30 36 42 45
6 31 37 43 46
1 2 2 0 0
2 0 48 0 48
3 1 49 1 49
2 0 48 8 8
3 1 49 9 51
4 32 50 33 52
2 8 8 0 48
3 9 51 22 54
4 33 52 35 55
5 34 53 36 56
3 22 54 1 49
4 35 55 44 58
5 36 56 45 59
6 37 57 46 60
1 1 0 1 0
2 0 0 62 62
2 0 2 62 5
3 1 3 63 64
2 2 5 5 5
3 3 6 64 66
4 38 39 65 67
2 5 0 5 62
3 6 17 66 69
4 39 41 67 70
5 40 42 68 71
3 17 1 69 63
4 41 44 70 73
5 42 45 71 74
6 43 46 72 75
1 3 2 1 0
2 0 48 62 77
3 1 49 63 78
4 44 58 73 79
5 45 59 74 80
6 46 60 75 81
7 47 61 76 82
2 48 0 48 0
3 49 84 49 84
2 48 0 8 8
3 49 84 51 86
4 50 85 52 87
2 8 8 48 0
3 51 86 54 89
4 52 87 55 90
5 53 88 56 91
3 54 89 49 84
4 55 90 58 93
5 56 91 59 94
6 57 92 60 95
2 48 0 77 62
3 49 84 78 97
4 58 93 79 98
5 59 94 80 99
6 60 95 81 100
7 61 96 82 101
2 62 62 0 0
2 62 5 0 2
3 63 64 103 104
2 5 5 2 5
3 64 66 104 106
4 65 67 105 107
2 5 62 5 0
3 66 69 106 109
4 67 70 107 110
5 68 71 108 111
3 69 63 109 103
4 70 73 110 113
5 71 74 111 114
6 72 75 112 115
2 62 77 0 48
3 63 78 103 117
4 73 79 113 118
5 74 80 114 119
6 75 81 115 120
7 76 82 116 121
2 77 62 48 0
3 78 97 117 123
4 79 98 118 124
5 80 99 119 125
6 81 100 120 126
7 82 101 121 127
8 83 102 122 128
3 84 1 84 1
3 84 1 86 9
4 85 130 87 131
3 86 9 89 22
4 87 131 90 133
5 88 132 91 134
3 89 22 84 1
4 90 133 93 136
5 91 134 94 137
6 92 135 95 138
3 84 1 97 63
4 93 136 98 140
5 94 137 99 141
6 95 138 100 142
7 96 139 101 143
3 97 63 123 103
4 98 140 124 145
5 99 141 125 146
6 100 142 126 147
7 101 143 127 148
8 102 144 128 149
3 103 104 1 3
3 104 106 3 6
4 105 107 151 152
3 106 109 6 17
4 107 110 152 154
5 108 111 153 155
3 109 103 17 1
4 110 113 154 157
5 111 114 155 158
6 112 115 156 159
3 103 117 1 49
4 113 118 157 161
5 114 119 158 162
6 115 120 159 163
7 116 121 160 164
3 117 123 49 84
4 118 124 161 166
5 119 125 162 167
6 120 126 163 168
7 121 127 164 169
8 122 128 165 170
3 123 103 84 1
4 124 145 166 172
5 125 146 167 173
6 126 147 168 174
7 127 148 169 175
8 128 149 170 176
9 129 150 171 177

Edit 2: here is the result of using B3/S (instead of B34/S34) for universe 2:

Code: Select all

x = 139, y = 81, rule = Test_post198039
2B$2B19$66.A$64.A.A$65.2A12.A$79.A.A$79.2A8$72.B2$71.B.B2$70.B.B.B2$
69.B.B.B.B41$137.2C$137.2C!

@RULE Test_post198039

@TREE

num_states=4
num_neighbors=8
num_nodes=178
1 0 0 0 0
2 0 0 0 0
1 0 1 0 1
2 0 2 0 2
3 1 3 1 3
1 1 1 1 1
2 2 5 2 5
3 3 6 3 6
1 2 2 0 0
2 0 0 8 8
1 2 3 0 1
2 0 2 8 10
3 1 3 9 11
1 3 3 1 1
2 2 5 10 13
3 3 6 11 14
4 4 7 12 15
2 5 0 5 0
3 6 17 6 17
2 5 0 13 8
3 6 17 14 19
4 7 18 15 20
2 8 8 0 0
2 8 10 0 2
3 9 11 22 23
2 10 13 2 5
3 11 14 23 25
4 12 15 24 26
2 13 8 5 0
3 14 19 25 28
4 15 20 26 29
5 16 21 27 30
3 17 1 17 1
3 17 1 19 9
4 18 32 20 33
3 19 9 28 22
4 20 33 29 35
5 21 34 30 36
3 22 23 1 3
3 23 25 3 6
4 24 26 38 39
3 25 28 6 17
4 26 29 39 41
5 27 30 40 42
3 28 22 17 1
4 29 35 41 44
5 30 36 42 45
6 31 37 43 46
2 0 8 0 8
3 1 48 1 48
2 0 8 8 8
3 1 48 9 50
4 32 49 33 51
2 8 8 0 8
3 9 50 22 53
4 33 51 35 54
5 34 52 36 55
3 22 53 1 48
4 35 54 44 57
5 36 55 45 58
6 37 56 46 59
1 1 0 1 0
2 0 0 61 61
2 0 2 61 5
3 1 3 62 63
2 2 5 5 5
3 3 6 63 65
4 38 39 64 66
2 5 0 5 61
3 6 17 65 68
4 39 41 66 69
5 40 42 67 70
3 17 1 68 62
4 41 44 69 72
5 42 45 70 73
6 43 46 71 74
1 3 2 1 0
2 0 8 61 76
3 1 48 62 77
4 44 57 72 78
5 45 58 73 79
6 46 59 74 80
7 47 60 75 81
2 8 0 8 0
3 48 83 48 83
2 8 0 8 8
3 48 83 50 85
4 49 84 51 86
2 8 8 8 0
3 50 85 53 88
4 51 86 54 89
5 52 87 55 90
3 53 88 48 83
4 54 89 57 92
5 55 90 58 93
6 56 91 59 94
2 8 0 76 61
3 48 83 77 96
4 57 92 78 97
5 58 93 79 98
6 59 94 80 99
7 60 95 81 100
2 61 61 0 0
2 61 5 0 2
3 62 63 102 103
2 5 5 2 5
3 63 65 103 105
4 64 66 104 106
2 5 61 5 0
3 65 68 105 108
4 66 69 106 109
5 67 70 107 110
3 68 62 108 102
4 69 72 109 112
5 70 73 110 113
6 71 74 111 114
2 61 76 0 8
3 62 77 102 116
4 72 78 112 117
5 73 79 113 118
6 74 80 114 119
7 75 81 115 120
2 76 61 8 0
3 77 96 116 122
4 78 97 117 123
5 79 98 118 124
6 80 99 119 125
7 81 100 120 126
8 82 101 121 127
3 83 1 83 1
3 83 1 85 9
4 84 129 86 130
3 85 9 88 22
4 86 130 89 132
5 87 131 90 133
3 88 22 83 1
4 89 132 92 135
5 90 133 93 136
6 91 134 94 137
3 83 1 96 62
4 92 135 97 139
5 93 136 98 140
6 94 137 99 141
7 95 138 100 142
3 96 62 122 102
4 97 139 123 144
5 98 140 124 145
6 99 141 125 146
7 100 142 126 147
8 101 143 127 148
3 102 103 1 3
3 103 105 3 6
4 104 106 150 151
3 105 108 6 17
4 106 109 151 153
5 107 110 152 154
3 108 102 17 1
4 109 112 153 156
5 110 113 154 157
6 111 114 155 158
3 102 116 1 48
4 112 117 156 160
5 113 118 157 161
6 114 119 158 162
7 115 120 159 163
3 116 122 48 83
4 117 123 160 165
5 118 124 161 166
6 119 125 162 167
7 120 126 163 168
8 121 127 164 169
3 122 102 83 1
4 123 144 165 171
5 124 145 166 172
6 125 146 167 173
7 126 147 168 174
8 127 148 169 175
9 128 149 170 176

[LuveelVoom]

The 34life blocks behave as CGOL except in a 3x3 pattern, so they could, for example, form a Sir Robin at 3x scale where cells inside it behave as b34/s34.

So far, I do not understand the intended idea. It is possible that I might be missing something obvious here. Some illustrative examples (of what is the desired behaviour / what are the desired update rules) could help here.

Scrap the 3x3 idea; I realized it wouldn’t work if two blocks differently aligned collide. What I’m asking for now is similar to RegionalityV except that the 3-4 life regions change their boundaries by operating under CGOL rules.

[confocaloid]

[...] What I’m asking for now is similar to RegionalityV except that the 3-4 life regions change their boundaries by operating under CGOL rules.

Well, I think one really would need to provide substantially more details, about how exactly things should work.
(When and how the boundaries should change?)

If you investigate a typical RuleLoader ruletable, you'll find an ordered sequence of "if-then" rules there (in the "@TABLE" section), like this:

• If <condition-1> is met then the state of the cell will be <cellstate-1> in the next generation, otherwise...
• If <condition-2> is met then the state of the cell will be <cellstate-2> in the next generation, otherwise...
• If <condition-3> is met then the state of the cell will be <cellstate-3> in the next generation, otherwise...
• ...

(although written in a different syntax). Each <condition-N> is only allowed to tell something about the current states of (some or all) neighbours of a cell and/or the current state of the cell itself.

Even though it is not necessary to state requests here in this specific form, a request should nevertheless be precise and unambiguous enough so that it can in principle be translated into an ordered sequence of if-then rules like this.

[get_Snacked]

a MAP rule for Life but with B2a in only one orientation.

[confocaloid]

a MAP rule for Life but with B2a in only one orientation.

I think these are all possibilities:

Code: Select all

MAPARYXfh5ofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
MAPARYXfhZofugW6H7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
MAPARYXfhZofugWaH7oaIDogBZofuhogOiA6IDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7o6IDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAA6IDogIAAgACAAIAAAAAAAA
MAPAVYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
MAPAxYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
MAPERYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA

Code: Select all

x = 8, y = 2, rule = MAPARYXfh5ofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
7bo$2o5bo!

[get_Snacked]

a MAP rule for Life but with B2a in only one orientation.

I think these are all possibilities:

Code: Select all

MAPARYXfh5ofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
MAPARYXfhZofugW6H7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
MAPARYXfhZofugWaH7oaIDogBZofuhogOiA6IDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7o6IDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
MAPARYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAA6IDogIAAgACAAIAAAAAAAA
MAPAVYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
MAPAxYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA
MAPERYXfhZofugWaH7oaIDogBZofuhogOiAaIDogIAAgAAWaH7oaIDogGiA6ICAAIAAaIDogIAAgACAAIAAAAAAAA

how did you find those so fast? is there a MAP string maker i don't know of?