Rule request thread

[hotdogPi]

Half-generations could work. Alternate between

1. marking the duoplets with an additional state but not changing on/off status
2. evolving on/off and unmarking all duoplet-marked cells

[PiSpaceships]

I request R3 two-state isotropic rule that evolves like Life except this case (grey cells are ignored):

Code: Select all

x = 16, y = 7, rule = LifeHistory
7F$7F4.B$2F5B5.B$2F2BA2B2.4B2.A$2FBABAB5.B$2FBABAB4.B$2F5B!

[confocaloid]

Half-generations could work. Alternate between

1. marking the duoplets with an additional state but not changing on/off status
2. evolving on/off and unmarking all duoplet-marked cells

I think one would need more than that (to be able to distinguish a duoplet from a diagonal line of three alive cells, and also to be able to "see" non-duoplet bits beyond the Moore neighbourhood). The cellstates could be roughly as follows:

• (0) the cell is currently dead; need to compute more
• (1) the cell is currently alive; need to compute more
• (2) the cell's condition is (S1c|D1c); need to compute more
• (3) the cell is currently alive, but its condition is not (S1c|D1c); need to compute more
• (4) the cell belongs to a duoplet; need to wait 2 ticks
• (5) the cell is currently alive, but it does not belong to a duoplet; need to wait 2 ticks
• (6) the cell is currently dead, and there is a non-duoplet bit at most one cell away
• (7) the cell belongs to a duoplet; need to wait 1 tick
• (8) the cell is currently alive, but it does not belong to a duoplet; need to wait 1 tick
• (9) the cell is currently dead, and there is a non-duoplet bit at most two cells away; will follow the rules of CGoL in the next tick
• (10) the cell belongs to a duoplet; will follow the rules of CGoL in the next tick
• (11) the cell is currently alive, but it does not belong to a duoplet; will follow the rules of CGoL in the next tick

- and then the only allowed transitions (out of 144 = 12^2 different transitions in total) would be as follows (the remaining ones would never happen under any circumstances):

• 0->0, 0->6, 0->9; possibly also 0->1 depending on the implementation choices,
• 1->2, 1->3;
• 2->4, 2->5;
• 3->5;
• 4->7;
• 5->8;
• 6->9;
• 7->10;
• 8->11;
• 9->0, 9->1;
• 10->0;
• 11->0, 11->1;

- and I think there would be 5 ticks of time needed to emulate one tick (e.g. here are some possible sequences of consecutive transitions that a single cell could undergo):

• 1->2->4->7->10->0
• 1->2->5->8->11->1
• 1->3->5->8->11->0

Depending on how far one needs to see "non-duoplet alive cells", there could be for example 3 more cellstates and 1 more tick needed to emulate one tick.

I request R3 two-state isotropic rule that evolves like Life except this case (grey cells are ignored):

Code: Select all

x = 16, y = 7, rule = LifeHistory
7F$7F4.B$2F5B5.B$2F2BA2B2.4B2.A$2FBABAB5.B$2FBABAB4.B$2F5B!

Probably someone could emulate that via RuleLoader (with more than two cellstates, and more than one tick needed to emulate one tick).

If you want it to be implemented as a two-state cellular automaton, and if that is attempted with a fully-symmetric weighted neighbourhood, then your "exception" case would translate into the following cell condition (equivalence class of neighbourhood configurations, up to permutations preserving the sum of weights of alive neighbours),

(the cell is currently dead) AND
(there are precisely 2 alive (1,0) neighbours, out of 4) AND
(there are precisely 0 alive (1,1) neighbours, out of 4) AND
(there are 1, 2, or 3 alive (2,0) neighbours, out of 4) AND
(there are 1, 2, 3, 4, or 5 alive (2,1) neighbours, out of 8) AND
(there is at least 1 alive (2,2) neighbour, out of 4) AND
(there are at most 2 alive (3,0) neighbours, out of 4) AND
(there are at most 4 alive (3,1) neighbours, out of 8) AND
(there are at most 6 alive (3,2) neighbours, out of 8) AND
(there are at most 3 alive (3,3) neighbours, out of 4)

... or (more likely) into an even weaker cell condition that would tell even less information about current states of the cell and its neighbours.

[PiSpaceships]

Probably someone could emulate that via RuleLoader (with more than two cellstates, and more than one tick needed to emulate one tick).

Request updated:

I request multi-state isotropic rule whose non-emulated version is R3 and evolves like Life except this case (grey cells are ignored):

Code: Select all

x = 16, y = 7, rule = LifeHistory
7F$7F4.B$2F5B5.B$2F2BA2B2.4B2.A$2FBABAB5.B$2FBABAB4.B$2F5B!

[CARuler]

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!

rake

Code: Select all

x = 3, y = 2, rule = R2,C2,S10-19,50-59,B15-19,45,55-59,NW00000100000005050500010500050100052d05000000010000
bo$3o!

i have a request:
cgol but in R3 where the ant works (part of the ants wick)

Code: Select all

x = 13, y = 20, rule = B3/S23
b2o$b2o7b2o$o2bo6b2o$o2bo5bo2bo$9bo2bo2$10b2o$10b2o$9bo2bo$9bo2bo2$10b
2o$10b2o$9bo2bo$9bo2bo2$10b2o$10b2o$9bo2bo$9bo2bo!

[unname4798]

Headerless RLE:

Code: Select all

b2o$b2o7b2o$o2bo6b2o$o2bo5bo2bo$9bo2bo2$10b2o$10b2o$9bo2bo$9bo2bo2$10b
2o$10b2o$9bo2bo$9bo2bo2$10b2o$10b2o$9bo2bo$9bo2bo!





























































































































































CARuler is insane with R3.











































Don't scroll.













































Please DON'T! That's a secret!











































































[[ PASTEDELTA 0 -1 PASTET EVERY 1 1 PASTE 2o! 1 -1 PASTE 2o! 10 0 ]]

[confocaloid]

[...] i have a request:
cgol but in R3 where the ant works (part of the ants wick)

Code: Select all

x = 13, y = 20, rule = B3/S23
b2o$b2o7b2o$o2bo6b2o$o2bo5bo2bo$9bo2bo2$10b2o$10b2o$9bo2bo$9bo2bo2$10b
2o$10b2o$9bo2bo$9bo2bo2$10b2o$10b2o$9bo2bo$9bo2bo!

Here, pentadecathlon exists, but figure eight doesn't:

Code: Select all

#C the collection is preserved in 2^5572 cellular automata with the same weighted neighbourhood:
#C optional birth conditions (2756): 4-13, 16-26, 29-39, 43-52, 54-64, 66, 68-116, 121-122, 124-129, 134-142, 148-155, 160, 163-168, 170, 172-181, 183-233, 238-246, 251, 253-259, 264-272, 278-286, 291-300, 302-314, 316-350, 356-363, 369-376, 381-390, 396-405, 407-416, 418-432, 434-443, 445-457, 459-467, 476-481, 486-494, 498-506, 513-533, 535-561, 563-584, 589, 591-597, 603-611, 617-624, 630-678, 680-701, 708-714, 716, 720-727, 729, 733-742, 746-818, 820, 824-833, 836-847, 849-859, 861, 864-936, 938-939, 941-949, 951, 953-964, 967-978, 981-1080, 1082-1213, 1215-1609, 1611-1615, 1617-1726, 1728-2924
#C optional survival conditions (2816): 0-13, 15, 17-25, 27, 29-38, 41-51, 53, 55-77, 79, 81-131, 133-143, 145, 147-155, 160-169, 174-182, 184-195, 197-247, 249-259, 265-273, 279-287, 289-299, 301, 304-313, 316-352, 354-363, 367-377, 381, 383-390, 394-404, 408-415, 417-418, 421, 423-433, 435-443, 446-468, 470-481, 483, 485-494, 498-508, 510-521, 523, 526-535, 537-538, 541-550, 552-563, 565-574, 576-585, 587-598, 602-611, 614-625, 628, 630-639, 641, 643-651, 653-693, 695-716, 718-731, 733-742, 744, 747-756, 759-770, 773-845, 847-886, 888, 890-990, 992-1004, 1006-1007, 1009-1148, 1150-1395, 1397-1475, 1477-1594, 1596-2924
#C weighted neighbourhood (weights given in hexadecimal; '0D' means 13; '75' means 117):
#C 75 75 75 01 75 75 75
#C 75 -- 01 75 01 -- 75
#C 75 01 0D 0D 0D 01 75
#C 01 75 0D -- 0D 75 01
#C 75 01 0D 0D 0D 01 75
#C 75 -- 01 75 01 -- 75
#C 75 75 75 01 75 75 75
#C
#C [[ GRID THEME MCell ]]
x = 63, y = 34, rule = R3,C0,S26-51,143-168,260-285,377-402,494-519,611-636,728-753,845-870,962-987,1079-1104,1196-1221,1313-1338,1430-1455,1547-1572,1664-1689,1781-1806,1898-1923,2015-2040,2132-2157,2249-2274,2366-2391,2483-2508,2600-2625,2717-2742,2834-2859,B39-51,156-168,273-285,378,390-402,507-519,624-636,741-753,858-870,975-987,1092-1104,1209-1221,1326-1338,1443-1455,1560-1572,1677-1689,1794-1806,1911-1923,2028-2040,2145-2157,2262-2274,2379-2391,2496-2508,2613-2625,2730-2742,2847-2859,NW757575017575757500017501007575010D0D0D017501750D000D750175010D0D0D01757500017501007575757501757575
24b2o3b2o3b2o3b2o18b2o$3b3o20b2o3b2o3b2o3b2o18b2o$3b3o20b2o3b2o3b2o3b
2o18b2o$3b3o18b2o3b2o3b2o3b2o18b2o$3o$3o$3o8$2bo21b2o3b2o3b2o18b2o3b2o
$2bo23b2o3b2o3b2o18b2o3b2o$bobo22b2o3b2o3b2o18b2o3b2o$2bo21b2o3b2o3b2o
18b2o3b2o$2bo$2bo$2bo$bobo$2bo$2bo6$14b2o11bo$12bo4bo7bo3bo8bo2bo$18bo
11bo11bo18bo$12bo5bo6bo4bo7bo3bo19bo$13b6o7b5o8b4o17b3o!

Here, figure eight exists, but pentadecathlon doesn't:

Code: Select all

#C the collection is preserved in 2^6536 cellular automata with the same weighted neighbourhood:
#C optional birth conditions (3240): 3-15, 17-64, 66-116, 121-129, 133-143, 147-156, 158-168, 170-233, 238-246, 251-259, 264-272, 276-350, 356-363, 368-376, 381-390, 393-416, 418-467, 473-480, 485-493, 497, 499-506, 512-519, 521, 523-532, 535-584, 589-597, 602-610, 615-623, 628-637, 639-675, 677-701, 706-714, 719-727, 733-740, 746-754, 757-781, 783-794, 796-819, 823-832, 836-845, 849-858, 863-911, 913-937, 939-949, 953-962, 966-974, 976-977, 981-990, 992-993, 995-1003, 1005-1013, 1015-1053, 1056-1069, 1071-1080, 1082-1094, 1096-1108, 1110-1171, 1174-1183, 1185-1197, 1199-1212, 1214-1225, 1227-1433, 1435-1445, 1447-3392
#C optional survival conditions (3296): 0-51, 53-132, 134-145, 147-155, 157-259, 263-272, 276-286, 288-339, 341-352, 354, 356-363, 367-377, 382-389, 394-468, 470-480, 484, 486-493, 497-507, 511-520, 524-532, 536-546, 548-560, 562-585, 587-599, 601-610, 615-625, 627-637, 641-650, 653-662, 664-676, 678-716, 718-728, 731-740, 744, 746-754, 756, 758-767, 770-780, 782-793, 795-807, 809-834, 836-849, 851-858, 861, 864-871, 873, 876-884, 887-897, 899-976, 978-988, 990-1001, 1003-1014, 1016-1028, 1030-1093, 1096-1105, 1107-1119, 1122-1224, 1226-1236, 1238-1676, 1678-3392
#C weighted neighbourhood (weights given in hexadecimal; '0D' means 13; '75' means 117):
#C 01 75 75 01 75 75 01
#C 75 01 75 75 75 01 75
#C 75 75 0D 0D 0D 75 75
#C 01 75 0D -- 0D 75 01
#C 75 75 0D 0D 0D 75 75
#C 75 01 75 75 75 01 75
#C 01 75 75 01 75 75 01
#C
#C [[ GRID THEME MCell ]]
x = 63, y = 34, rule = R3,C0,S26-51,143-168,260-285,377-402,494-519,611-636,728-753,845-870,962-987,1079-1104,1196-1221,1313-1338,1430-1455,1547-1572,1664-1689,1781-1806,1898-1923,2015-2040,2132-2157,2249-2274,2366-2391,2483-2508,2600-2625,2717-2742,2834-2859,2951-2976,3068-3093,3185-3210,3302-3327,B39-51,156-168,273-285,390-402,494,507-519,624-636,741-753,858-870,975-987,1092-1104,1209-1221,1326-1338,1443-1455,1560-1572,1677-1689,1794-1806,1911-1923,2028-2040,2145-2157,2262-2274,2379-2391,2496-2508,2613-2625,2730-2742,2847-2859,2964-2976,3081-3093,3198-3210,3315-3327,NW017575017575017501757575017575750D0D0D757501750D000D750175750D0D0D75757501757575017501757501757501
24b2o3b2o3b2o3b2o18b2o$3b3o20b2o3b2o3b2o3b2o18b2o$3b3o20b2o3b2o3b2o3b
2o18b2o$3b3o18b2o3b2o3b2o3b2o18b2o$3o$3o$3o8$2bo21b2o3b2o3b2o18b2o3b2o
$2bo23b2o3b2o3b2o18b2o3b2o$bobo22b2o3b2o3b2o18b2o3b2o$2bo21b2o3b2o3b2o
18b2o3b2o$2bo$2bo$2bo$bobo$2bo$2bo6$14b2o11bo$12bo4bo7bo3bo8bo2bo$18bo
11bo11bo18bo$12bo5bo6bo4bo7bo3bo19bo$13b6o7b5o8b4o17b3o!

[hotcrystal0]

I'm currently creating a rule to hybridize ChainedLife with Sticky. (this ruletable is to be appropriately modified for StickyChainedLife1-5) Since the ChainedLife and Sticky ruletables are written in vastly different "styles", can someone help add the Sticky part (plus the state 2 diaphoton birth and states 2-3 state 1/5 birth from the ChainedLife series and making it compatible with ChainedLife1-5)? State 2 corresponds to Sticky state 3, State 4 corresponds to Sticky state 2, and State 6 corresponds to Sticky state 1.

Code: Select all

@RULE StickyChainedLife0

@COLORS

0 0 0 0
1 255 255 255
2 255 0 0
3 0 255 0
4 255 255 0
5 0 0 255 
6 128 128 128

@TABLE

# Original rule by Yoel Matveyev (2022). Modification by hotcrystal0 (2025)

n_states:7
neighborhood:Moore
symmetries:rotate4reflect

var i={0,4,6}
var j=i
var k=i
var l=i
var m=i
var n=i
var o=i
var p=i

var I={1,2,3,5}
var J=I
var K=I
var L=I
var M=I
var N=I
var O=I
var P=I

var R={1,5}

var a={0,1,2,3,5}
var b=a
var c=a
var d=a
var e=a
var f=a
var g=a
var h=a

var A={0,1,2,3,4,5,6}
var B=A
var C=A
var D=A
var E=A
var F=A
var G=A
var H=A
var X=A

# Life

0,I,j,K,l,M,n,o,p,1
0,i,J,k,l,m,N,o,P,1
0,I,j,k,L,m,N,o,p,1
0,i,J,K,L,m,n,o,p,1
0,I,J,K,l,m,n,o,p,1
0,I,j,K,l,m,n,o,P,1
0,I,j,k,L,m,n,O,p,1
0,I,j,k,L,M,n,o,p,1
0,I,J,k,L,m,n,o,p,1
0,I,j,k,L,m,n,o,P,1

R,I,j,K,l,M,n,o,p,1
R,i,J,k,l,m,N,o,P,1
R,I,j,k,L,m,N,o,p,1
R,i,J,K,L,m,n,o,p,1
R,I,J,K,l,m,n,o,p,1
R,I,j,K,l,m,n,o,P,1
R,I,j,k,L,m,n,O,p,1
R,I,j,k,L,M,n,o,p,1
R,I,J,k,L,m,n,o,p,1
R,I,j,k,L,m,n,o,P,1

R,I,j,K,l,m,n,o,p,1
R,i,J,k,L,m,n,o,p,1
R,I,j,k,L,m,n,o,p,1
R,I,J,k,l,m,n,o,p,1
R,i,J,k,l,m,N,o,p,1
R,I,j,k,l,M,n,o,p,1

# State 6 physics

6,I,j,K,l,M,n,o,p,2
6,i,J,k,l,m,N,o,P,6
6,I,j,k,L,m,N,o,p,6
6,i,J,K,L,m,n,o,p,6
6,I,J,K,l,m,n,o,p,5
6,I,j,K,l,m,n,o,P,5
6,I,j,k,L,m,n,O,p,6
6,I,j,k,L,M,n,o,p,0
6,I,J,k,L,m,n,o,p,6
6,I,j,k,L,m,n,o,P,5

# Photon

0,2,b,c,d,e,f,g,h,2

# Diaphoton

0,0,3,0,0,0,0,0,0,3
0,3,B,C,D,E,F,G,H,4

# Photon birth



# Diaphoton birth

0,2,C,2,D,E,F,G,H,3

# Catalyst birth

0,4,3,4,3,4,3,4,3,6


# Catalyst survival

6,i,j,k,l,m,n,o,p,6

# Clean up

2,A,B,C,D,E,F,G,H,4
3,A,B,C,D,E,F,G,H,4
4,A,B,C,D,E,F,G,H,0
6,A,B,C,D,E,F,G,H,6
X,A,B,C,D,E,F,G,H,0

[confocaloid]

[...] Since the ChainedLife and Sticky ruletables are written in vastly different "styles", can someone help add the Sticky part (plus the state 2 diaphoton birth and states 2-3 state 1/5 birth from the ChainedLife series and making it compatible with ChainedLife1-5)? State 2 corresponds to Sticky state 3, State 4 corresponds to Sticky state 2, and State 6 corresponds to Sticky state 1. [...]

It sounds like that could be solvable in a text editor (and could be easier to DIY because of better understanding of what are requirements), by

• editing a copy of https://conwaylife.com/w/index.php?titl ... ction=edit to consistently rename all variables (e.g. by adding prefix "Sticky" to every variable name), to avoid name clashes,
• then editing both the list of rules and the variable declarations in the "modified Sticky" (per above) to consistently change cellstate indices (use 6 instead of 1, 4 instead of 2, 2 instead of 3),
• then merging the variable declarations (you can simply declare all variables at the beginning, after "n_states/neighborhood/symmetries" lines),
• then merging the two lists of rules into a single list, making sure that the ordering of rules from the same origin is preserved and the overall ordering of rules matches what you want to achieve,
• then adding/removing/modifying rule lines further, if you need some additional interactions on top of that.

Are there reasons why the above wouldn't work for you?

[LuveelVoom]

This 1dca:

EDIT: wow, what is going on? it looks like a bounded replicator, but I can't tell what's going on...

Code: Select all

x = 7, y = 35, rule = B2i3-ek4ci/S2-i3-ak4ciy5ce6c
bobobo$ob3obo$bo3bo$obobobo$bo3bo$obobobo$bo3bo$obobobo$bo3bo$ob3obo$
bo3bo$obobobo$bo3bo$ob3obo$bobobo$ob3obo$bobobo$ob3obo$bobobo$ob3obo$
bo3bo$obobobo$bo3bo$ob3obo$bo3bo$obobobo$bo3bo$ob3obo$bo3bo$obobobo$b
o3bo$ob3obo$bobobo$obobobo$bobobo!

As far as I can tell, it's simulating some sort of convoluted 3-state 1D cellular automaton:
1) State 0 cells always turn to state 1 cells, unless there are a line of two or more in a row, in which case all members in the row turn to state 2 cells
2) State 1 cells always turn to state 0 cells
3) State 2 cells, which always form in a line of 2 or more according to rule 1), turn to state 1 if they're at the edges of the line, and state 0 if they're in the middle

As far as I can tell, it's not a replicator, but I could of course be wrong. Experimentation would be a lot easier with a ruletable, although I'm not sure how rules 1 and 3 would be implemented in one

[breaker's glider gun]

It seems to be striped with different rules:

Code: Select all

x = 259, y = 1, rule = T
ADBCBCBCBCBCBCBCBCBCBCBCBCBCBCBCBCACACACACACACACACACACACACACACACACACA
CACACACACACACACACACACACACACACACACACACACADACACACACACACACACACACACACACAC
ACACACACACACACACACACACACACACACACACACACACACACACACACACACACACACACACACACA
CACACACACACACACACACBCBCBCBCBCBCBCBCBCBCBCBCBCBCBCBDA!

@RULE T

@TABLE
n_states:5
neighborhood:Moore
symmetries:rotate4reflect
var a = {0, 1,2,3,4}
var a1 = a
var a2 = a
var a3 = a
var a4 = a
var a5 = a
var a6 = a
var a7 = a
var a8 = a

4, 2,0,0,0 ,1,0,0,0, 4
3, 1,0,0,0, 1,0,0,0, 4
1, 3,0,0,0, 3,0,0,0, 2
2, 4,0,0,0, 4,0,0,0, 1

#these never occur naturally:
2, 4,0,0,0, 3,0,0,0, 2 
2, 3,0,0,0, 3,0,0,0, 2
4, 2,0,0,0, 1,0,0,0, 4
#death
4, a1,a2,a3,a4, a5,a6,a7,a8, 3

[ThePlayzr]

can someone script me a GreyLifeFive? Idk how to script

[dvgrn]

can someone script me a GreyLifeFive? Idk how to script

Just as a silly pedantic note, "script" in this context would probably usually mean writing a program to write the rule table for GreyLifeFive. Writing rule tables isn't usually called "scripting" -- no programming involved. And only one rule-table line needs to be added here, along with one change to an existing line, so definitely any kind of scripting would be overkill in this case.

Context for this question: GreyLife started here (and it was really "GreyLifeEight", so to speak) -- and GreyLifeSix came along here.

Inspect the two rule tables and you'll see that to convert GreyLife(Eight) into GreyLifeSix, I only had to change

Code: Select all

var a={0,1,2}
...
0, 1,1,1,o,oa,ob,oc,od, 1
0, 1,1,1,1,1,1,1,1, 2
1, a,o,oa,ob,oc,od,oe,of, 0
1, 1,1,1,1,a,aa,ab,ac, 0
1, 2,a,aa,ab,ac,ad,ae,af, 0
2, 1,1,1,1,1,1,1,1, 0

into

Code: Select all

var a={0,1,2}
var b={0,1,2}
...
0, 1,1,1,o,oa,ob,oc,od, 1
0, 1,1,1,1,1,1,1,1, 2
1, a,o,oa,ob,oc,od,oe,of, 0
1, 1,1,1,1,a,aa,ab,ac, 0
1, 2,a,aa,ab,ac,ad,ae,af, 0
2, 1,1,1,1,1,1,a,b, 0

@Anyone-who-wants-to-understand-rule-tables-a-little-better, reasoning by analogy, what does that imply would need to change in GreyLifeSix, to turn it into GreyLifeFive? See the relevant LifeWiki tutorial for an explanation of how to easily interpret each of the above rule-table lines.

("GreyLifeFive" presumably just means that state-2 grey cells always remain grey cells unless they come to be surrounded with five state-1 live neighbors.)

[ThePlayzr]

Inspect the two rule tables and you'll see that to convert GreyLife(Eight) into GreyLifeSix, I only had to change

Code: Select all

var a={0,1,2}
...
0, 1,1,1,o,oa,ob,oc,od, 1
0, 1,1,1,1,1,1,1,1, 2
1, a,o,oa,ob,oc,od,oe,of, 0
1, 1,1,1,1,a,aa,ab,ac, 0
1, 2,a,aa,ab,ac,ad,ae,af, 0
2, 1,1,1,1,1,1,1,1, 0

into

Code: Select all

var a={0,1,2}
var b={0,1,2}
...
0, 1,1,1,o,oa,ob,oc,od, 1
0, 1,1,1,1,1,1,1,1, 2
1, a,o,oa,ob,oc,od,oe,of, 0
1, 1,1,1,1,a,aa,ab,ac, 0
1, 2,a,aa,ab,ac,ad,ae,af, 0
2, 1,1,1,1,1,1,a,b, 0

I looked at the tutorial and I am still so very very confused, please just make GreyLifeFive for me!

[dvgrn]

@Anyone-who-wants-to-understand-rule-tables-a-little-better, reasoning by analogy, what does that imply would need to change in GreyLifeSix, to turn it into GreyLifeFive?

I looked at the tutorial and I am still so very very confused, please just make GreyLifeFive for me!

Sorry, I keep a strict policy of not doing work for other people that they can perfectly well do themselves. The goal for me is not to make GreyLifeFive, but to make you less confused so that you can make GreyLifeFive.

But to do that, I probably have to understand why you're so very very confused. If you explain a little more what you're confused about, maybe I can improve the tutorial somehow.

Maybe this will help:

GreyLifeEight defines one variable, a, that means "a cell of any state" (state 0, state 1, or state 2):

Code: Select all

var a={0,1,2}

GreyLifeSix needs two different variables that mean that, a and b.

Code: Select all

var a={0,1,2}
var b={0,1,2}

Now, where did that extra variable get used in GreyLifeSix, where it wasn't needed in GreyLifeEight? Well, it's in the last line of the transition table.

The GreyLifeEight version of that last line said

Code: Select all

2, 1,1,1,1,1,1,1,1, 0

With just a little practice, you can read that easily from left to right. It means

IF the starting state is a 2, AND all eight neighbors are state 1, THEN the cell should change to state 0.

But in GreyLifeSix the line has changed to

Code: Select all

2, 1,1,1,1,1,1,a,b, 0

That means

IF the starting state is a 2, AND six neighbors are state 1 (and the other two can be any state) THEN the cell should change to state 0.

That last line for GreyLifeFive just needs to change to

IF the starting state is a 2, AND five neighbors are state 1 (and the other three can be any state) THEN the cell should change to state 0.

Reasoning by analogy, how would you say that in rule-table format?

Because variables can't be re-used in cases like this -- see "The reason why you need to use many variables instead of just one..." in the tutorial -- you'll need to define a third variable, let's say c, just like a and b, up in the variables section.

[SomePersonAlt]

Very stupid idea:

A mashup rule that includes both Bosco and Life. Don't even know if this is possible.

-SomePersonAlt (first post!!!)

[ThePlayzr]

uuhhhhh, like this?

Code: Select all

@RULE GreyLifeFive
@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
var a={0,1,2}
var b={0,1,2}
var c={0,1,2}
var aa=a
var ab=a
var ac=a
var ad=a
var ae=a
var af=a
var ag=a
var o={0,2}
var oa=o
var ob=o
var oc=o
var od=o
var oe=o
var of=o
var og=o
0,1,1,1,o,oa,ob,oc,od,1
0,1,1,1,1,1,1,1,1,2
1,a,o,oa,ob,oc,od,oe,of,0
1,1,1,1,1,a,aa,ab,ac,0
1,2,a,aa,ab,ac,ad,ae,af,0
2,1,1,1,1,1,a,b,c,0
@COLORS
0 0 0 0
1 255 255 255
2 100 100 100

And how do I use it?

Code: Select all

x = 0, y = 0, rule = GreyLifeFive
o!

[b-engine]

uuhhhhh, like this?

Code: Select all

@RULE GreyLifeFive
…

And how do I use it?

Code: Select all

x = 0, y = 0, rule = GreyLifeFive
o!

If you're planning to use it only a few times, you could append the rule table below the RLE:

Code: Select all

x = 0, y = 0, rule = GreyLifeFive
o!
@RULE GreyLifeFive
@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
var a={0,1,2}
var b={0,1,2}
var c={0,1,2}
var aa=a
var ab=a
var ac=a
var ad=a
var ae=a
var af=a
var ag=a
var o={0,2}
var oa=o
var ob=o
var oc=o
var od=o
var oe=o
var of=o
var og=o
0,1,1,1,o,oa,ob,oc,od,1
0,1,1,1,1,1,1,1,1,2
1,a,o,oa,ob,oc,od,oe,of,0
1,1,1,1,1,a,aa,ab,ac,0
1,2,a,aa,ab,ac,ad,ae,af,0
2,1,1,1,1,1,a,b,c,0
@COLORS
0 0 0 0
1 255 255 255
2 100 100 100

If you plan to use it frequently, I could help you to upload it to LifeWiki.

[islptng]

Want a hybrid rule with NORworld3 and Life.

Edit: Done by myself!

Code: Select all

x = 36, y = 26, rule = q
22.A$21.A.A$21.A.A2.A$21.A.A.A.A$21.D.A.A.A2.C$21.B.A.A.B.B.C$21.D.A.
A.C.A.C2.C$17.3AB.B2.D.D.A.D.C.C$16.A8.B.A.A.A.B.D$15.A2.2ABCD2A.A2.A
.A.A.B$13.EI2.A11.A.B.A.D$13.E3A2.AB3CD2ABD.D2.A.A$13.E5I14.A.A$13.E
9AB3CDBD3A.A5$.3A$A3.H$A3.2G$A4.G$A.3G$A.G$A$.35A!

x = 23, y = 14, rule = q
9.A$8.A.A$8.A.A2.A$8.A.A.A.A$8.D.A.A.A2.C$8.B.A.A.B.B.C$8.D.A.A.C.A.C
2.C$4.3AB.B2.D.D.A.D.C.C$3.A8.B.A.A.A.B.D$2.A2.2ABCD2A.A2.A.A.A.B$EI
2.A11.A.B.A.D$E3A2.AB3CD2ABD.D2.A.A$E5I14.A.A$E9AB3CDBD3A.A!

@RULE q

@COLORS
 0   0   0   0
 1  96  96  96
 2  96 255 255
 3 255 255 255
 4  96   0   0
 5 128   0 128
 6 255   0 255
 7   0 255 128
 8   0 128  64
 9 255   0   0
10 255 128   0
11 255 255   0
12 160 255   0

@TABLE
n_states:13
neighborhood:Moore
symmetries:rotate4reflect

var a = {0,1,2,3,4,5,6,7,8,9,10,11,12}
var b = a
var c = a
var d = a
var e = a
var f = a
var g = a
var h = a
var i = {1,4}
var I = i
var j = {2,3}
var J = j
var k = {1,2,3,4}
var K = k
var l = k
var L = k
var m = {2,4}
var n = {1,3}

var x = {0,5,6,7,8,9,10,11,12}
var y = x
var z = x

var q = {0,7,8}
var X = {6,7}
var Y = X
var Z = X
var A = {0,1,2,3,4,5,8,9,10,11,12}
var B = A
var C = A
var D = A
var E = A
var F = A

var Q = {9,10,11,12}
var r = {5,6}
var R = {2,3,10,11}

# Life -> NORworld3
1,a,7,b,c,d,e,f,g,2
2,a,7,b,c,d,e,f,g,3
2,a,8,b,c,d,e,f,g,4
3,a,8,b,c,d,e,f,g,4
4,a,8,b,c,d,e,f,g,1
4,a,7,b,c,d,e,f,g,2

# Wire -> Life
r,R,a,b,c,d,e,f,g,6
6,a,b,c,d,e,f,g,h,5

# Alternated wire
Q,0,1,0,a,b,c,d,e,9
Q,0,2,0,a,b,c,d,e,10
Q,0,3,0,a,b,c,d,e,11
Q,0,4,0,a,b,c,d,e,12
9,10,a,b,c,d,e,f,g,10
10,11,a,b,c,d,e,f,g,11
10,a,b,c,d,e,f,g,h,12
11,12,a,b,c,d,e,f,g,12
12,9,a,b,c,d,e,f,g,9
12,a,b,c,d,e,f,g,h,10

# NORworld3
k,x,a,K,y,l,z,L,b,k
1,x,i,1,I,y,a,b,c,2
2,x,i,1,I,y,a,b,c,3
2,x,k,1,K,y,a,b,c,4
3,x,i,1,I,y,a,b,c,3
3,x,k,1,K,y,a,b,c,4
4,x,i,1,I,y,a,b,c,2
i,x,j,2,J,y,a,b,c,2
j,x,i,2,I,y,a,b,c,4
1,x,i,3,j,y,a,b,c,2
2,x,i,3,j,y,a,b,c,3
2,x,k,3,K,y,a,b,c,4
3,x,i,3,j,y,a,b,c,3
3,x,k,3,K,y,a,b,c,4
4,x,i,3,j,y,a,b,c,2
i,x,j,4,k,y,a,b,c,2
j,x,J,4,k,y,a,b,c,4
1,x,k,K,l,y,a,b,c,1
2,x,k,K,l,y,a,b,c,3
3,x,k,K,l,y,a,b,c,3
4,x,k,K,l,y,a,b,c,1
4,x,1,y,a,b,c,d,e,1
4,k,1,K,a,b,c,d,e,1
4,a,x,1,y,b,c,d,e,1
i,x,2,y,a,b,c,d,e,2
i,k,2,K,a,b,c,d,e,2
i,a,x,2,y,b,c,d,e,2
2,x,3,y,a,b,c,d,e,3
2,k,3,K,a,b,c,d,e,3
2,a,x,3,y,b,c,d,e,3
j,x,4,y,a,b,c,d,e,4
j,k,4,K,a,b,c,d,e,4
j,a,x,4,y,b,c,d,e,4
2,a,b,c,d,e,f,g,h,3
4,a,b,c,d,e,f,g,h,1

# Life
7,X,Y,A,B,C,D,E,F,7
7,X,A,Y,B,C,D,E,F,7
7,X,A,B,Y,C,D,E,F,7
7,X,A,B,C,Y,D,E,F,7
7,A,X,B,Y,C,D,E,F,7
7,A,X,B,C,D,Y,E,F,7
q,X,Y,Z,A,B,C,D,E,7
q,X,A,Y,B,Z,C,D,E,7
q,A,X,B,Y,C,Z,D,E,7
q,A,X,Y,Z,B,C,D,E,7
q,X,A,Y,B,C,Z,D,E,7
q,X,Y,A,Z,B,C,D,E,7
q,X,A,B,Y,C,Z,D,E,7
q,A,X,B,C,Y,Z,D,E,7
q,A,X,Y,B,Z,C,D,E,7
q,X,Y,A,B,Z,C,D,E,7
7,a,k,b,c,d,e,f,g,8
7,a,b,c,d,e,f,g,h,0

=======
Unburying this:

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

EDIT: This pattern failed to produce Sir Robin, anyone know why?

Code: Select all

x = 305, y = 53, rule = q
24.271ABD8A$23.A$22.A2.252ABD5ABD5AB7CD5A$21.A2.A$20.A2.A2.A2.247ABCD
B4CD4AB4CD2ABD6A$19.A2.A2.A2.A$18.A2.A2.A2.A2.204ABDBCD3ABCD12ABCDBCD
2AB2CDABD3ABDBDBDBDBD5AB3CD10A$17.A2.A2.A2.A2.A$16.A2.A2.A2.A2.A2.
197ABD3ABCDBDBCD13ABDB2CDABDAB2CDABDABDBCDABCDBD2ABD5ABCD10A$15.A2.A
2.A2.A2.A2.A$14.A2.A2.A2.A2.A2.A2.192AB4CD2ABD2ABDBD3AB2CD6ABD7ABD3AB
2CD8AB2CDB2CD7ABD9A$13.A2.A2.A2.A2.A2.A2.A$E12A2.A2.A2.A2.A2.A2.A2.
189AB3CD8ABCD5ABCD5ABDB4CDBD2AB2CDBD2AB2CD8AB2CDBD16A$E14I2.A2.A2.A2.
A2.A2.A$E16A2.A2.A2.A2.A2.A2.186ABCD6ABD4ABD13ABD2ABDBDABD7AB4CDBD4AB
CD3ABCD16A$E18I2.A2.A2.A2.A2.A$E20A2.A2.A2.A2.A2.181ABCDABCDBCD4ABCD
2ABD7ABDBCDABD4ABD2AB3CD7ABDAB2CD26A$E22I2.A2.A2.A2.A$E24A2.A2.A2.A2.
176AB2CD7ABDBDBDABD2ABCDBDABCDBDABDBDBCDAB3CDABD3AB2CDBCDBD31A$E26I2.
A2.A2.A$E28A2.A2.A2.52ABCD64ABCD6ABCD28ABCD9AB3CD7ABCDBD5ABD10ABCDABD
10AB4CD6ABDBCD30A$E30I2.A2.A$E32A2.A2.49ABCDBCDBDABCD51ABCDAB2CD2ABDB
3CD24ABDB3CD2ABDBCD14AB4CDB2CD6ABCD3ABDBDABCDABD3AB3CD6ABD37A$E34I2.A
$E36A2.43ABDBDBDBDBD2AB3CD48AB3CDBD4ABD6ABD21AB3CD5ABCDBDABCD11ABDAB
3CD5ABCDBDB2CD3ABDB4CD6AB2CD43A$E38I$E79AB2CDABCD2ABDABDBD43ABD4ABD2A
BCD2ABD3ABDABD22AB4CDAB3CDBD3ABD2ABCD2ABCDAB2CD13ABD3ABD4ABD2AB2CD52A
$E38I$E36A2.39AB2CDAB3CD6ABD37ABD3AB2CDBDBD5ABDB2CD6ABD6ABD8ABCD4AB2C
D3AB2CDBDB3CD14ABD83A$E34I2.A$E32A2.A2.37AB3CD4AB2CDAB2CDBDBD2ABD15AB
D4AB2CDBCD2ABCD2ABD11AB2CDABDBCD3ABCD14AB7CDABD5ABCDBD104A$E30I2.A2.A
$E28A2.A2.A2.33ABCDAB6CD2AB4CD2ABDBDBDB2CD9AB5CD2AB4CDBD2AB2CD6ABD6AB
DBD2ABDABD3AB2CD4ABD4AB3CDB5CDB2CD2ABD4ABD103A$E26I2.A2.A2.A$E24A2.A
2.A2.A2.32AB2CD4AB4CDABD2ABCD2ABCDBD4ABCD5AB4CD11ABD2ABDBD4ABD5AB3CDB
3CD5ABD2ABDBDB2CD3AB4CD2ABCDB2CD115A$E22I2.A2.A2.A2.A$E20A2.A2.A2.A2.
A2.30AB3CD12ABD5ABCD2ABCD5AB3CDABCD6AB2CDB2CDBD3ABD12AB2CD4ABCDBDB2CD
ABDAB3CDBCD2AB2CDBD7AB2CDB2CDAB2CDBD102A$E18I2.A2.A2.A2.A2.A$E16A2.A
2.A2.A2.A2.A2.30AB2CD5ABDABD3ABCD5ABCD10AB2CDBD3ABCDAB4CD5ABDABCD21AB
6CDABD11AB4CD2ABD4ABD5ABD2ABD103A$E14I2.A2.A2.A2.A2.A2.A$E12A2.A2.A2.
A2.A2.A2.A2.32ABCDABCDB2CDBD4ABD4ABD2AB6CD6ABD2ABCDBDABD3ABCDBD4ABD7A
BD16ABD2ABCDAB4CD3AB2CD4ABCD4ABDAB5CD106A$13.A2.A2.A2.A2.A2.A2.A$14.A
2.A2.A2.A2.A2.A2.34ABCDABCDBCDBCD2ABCDAB3CD14ABCD7AB6CDBD8ABD2AB4CD5A
BD11AB4CDAB2CD4ABCDABCDBCD2AB2CDABCDBD2ABCD103A$15.A2.A2.A2.A2.A2.A$
16.A2.A2.A2.A2.A2.43ABDAB9CDABCDB2CD3ABD6ABDBD3ABD4ABD5AB5CDABD2ABCD
17AB6CD9ABDB2CDABD4ABCDABCDBD107A$17.A2.A2.A2.A2.A$18.A2.A2.A2.A2.48A
BCD5ABCD5ABD2ABDABCD9AB2CDBCDBD4AB2CD5ABCDB2CDBD36ABCDABD119A$19.A2.A
2.A2.A$20.A2.A2.A2.45AB5CD9ABD3ABCD9ABD2AB2CD3AB6CDAB2CDABCDABDB4CD
161A$21.A2.A$22.A2.49AB3CDBD2ABCDABDBD6AB2CD5ABCDBDBD9ABD13ABD3ABD
161A$23.A$24.53ABCDABDB3CD11ABCDBCDBD198A!

[mmmmmmmmm]

uuhhhhh, like this?

Code: Select all

@RULE GreyLifeFive
…

And how do I use it?

Code: Select all

x = 0, y = 0, rule = GreyLifeFive
o!

If you're planning to use it only a few times, you could append the rule table below the RLE:

Code: Select all

x = 0, y = 0, rule = GreyLifeFour
o!
@RULE GreyLifeFour
@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
var a={0,1,2}
var b={0,1,2}
var c={0,1,2}
var d={0,1,2}
var aa=a
var ab=a
var ac=a
var ad=a
var ae=a
var af=a
var ag=a
var o={0,2}
var oa=o
var ob=o
var oc=o
var od=o
var oe=o
var of=o
var og=o
0,1,1,1,o,oa,ob,oc,od,1
0,1,1,1,1,1,1,1,1,2
1,a,o,oa,ob,oc,od,oe,of,0
1,1,1,1,1,a,aa,ab,ac,0
1,2,a,aa,ab,ac,ad,ae,af,0
2,1,1,1,1,a,b,c,d,0
@COLORS
0 0 0 0
1 255 255 255
2 100 100 100

If you plan to use it frequently, I could help you to upload it to LifeWiki.

GreyLifeFour!!!!!! Also, grey cells blocks aren't gardens of Eden, one of these with a dot on the edge or any spark evolves into this.

[b-engine]

GreyLifeFour!!!!!! Also, grey cells blocks aren't gardens of Eden, one of these with a dot on the edge or any spark evolves into this.

Corrected:

Code: Select all

x = 0, y = 0, rule = GreyLifeFour
o!
@RULE GreyLifeFour
@TABLE
n_states:3
neighborhood:Moore
symmetries:permute
var a={0,1,2}
var b={0,1,2}
var c={0,1,2}
var d={0,1,2}
var aa=a
var ab=a
var ac=a
var ad=a
var ae=a
var af=a
var ag=a
var o={0,2}
var oa=o
var ob=o
var oc=o
var od=o
var oe=o
var of=o
var og=o
0,1,1,1,o,oa,ob,oc,od,1
0,1,1,1,1,0,0,0,0,2
1,a,o,oa,ob,oc,od,oe,of,0
1,1,1,1,1,a,aa,ab,ac,0
1,2,a,aa,ab,ac,ad,ae,af,0
2,1,1,1,1,a,b,c,d,0
@COLORS
0 0 0 0
1 255 255 255
2 100 100 100

[tommyaweosme]

Very stupid idea:

A mashup rule that includes both Bosco and Life. Don't even know if this is possible.

-SomePersonAlt (first post!!!)

it includes an explosive version of bosco and an almost accurate version of life. pi is superexplosive.

Code: Select all

x = 7, y = 11, rule = R5,C2,S2-3,18-19,34-35,50-51,66-67,82-83,98-99,114-115,130-131,146-147,162-163,178-179,194-195,210-211,226-227,242-243,258-259,274-275,290-291,306-307,322-323,338-339,354-355,370-371,386-387,402-403,418-419,434-435,450-451,466-467,482-483,498-499,514-515,528-927,930-931,946-947,962-963,978-979,994-995,1010-1011,1026-1027,1042-1043,1058-1059,1074-1075,1090-1091,1106-1107,1122-1123,1138-1139,1154-1155,1170-1171,1186-1187,1202-1203,1218-1219,1234-1235,1250-1251,1266-1267,1282-1283,1298-1299,1314-1315,1330-1331,1346-1347,1362-1363,1378-1379,1394-1395,1410-1411,1426-1427,1442-1443,1458-1459,1474-1475,1490-1491,1506-1507,1522-1523,1538-1539,1554-1555,1570-1571,1586-1587,1602-1603,1618-1619,1634-1635,1650-1651,1666-1667,1682-1683,1698-1699,1714-1715,1730-1731,1746-1747,1762-1763,1778-1779,1794-1795,B3,19,35,51,67,83,99,115,131,147,163,179,195,211,227,243,259,275,291,307,323,339,355,371,387,403,419,435,451,467,483,499,515,531,544-735,739,755,771,787,803,819,835,851,867,883,899,915,931,947,963,979,995,1011,1027,1043,1059,1075,1091,1107,1123,1139,1155,1171,1187,1203,1219,1235,1251,1267,1283,1299,1315,1331,1347,1363,1379,1395,1411,1427,1443,1459,1475,1491,1507,1523,1539,1555,1571,1587,1603,1619,1635,1651,1667,1683,1699,1715,1731,1747,1763,1779,1795,NW10101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101001010110101010101010100100011010101010101010010101101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010
bo$2bo$3o7$5b2o$5b2o!

[SomePersonAlt]

Very stupid idea:

A mashup rule that includes both Bosco and Life. Don't even know if this is possible.

-SomePersonAlt (first post!!!)

it includes an explosive version of bosco and an almost accurate version of life. pi is superexplosive.

Code: Select all

code removed for brevity

Nice! I did mean multistate (state 1 is life, state 2 is Bosco) but this is interesting too!

[b-engine]

Nice! I did mean multistate (state 1 is life, state 2 is Bosco) but this is interesting too!

This is impossible to recreate this in rule table format supported by LifeViewer or Golly. Rule table doesn't natively support ranges larger than 1, and range-5 emulation would take far more than 256 cell states (which is the maximum of what rule table supports). But you may be able to do that on CAViewer.

[SomePersonAlt]

Nice! I did mean multistate (state 1 is life, state 2 is Bosco) but this is interesting too!

This is impossible to recreate this in rule table format supported by LifeViewer or Golly. Rule table doesn't natively support ranges larger than 1, and range-5 emulation would take far more than 256 cell states (which is the maximum of what rule table supports). But you may be able to do that on CAViewer.

Ah, that's what I figured. Thanks!