Code: Select all
x = 42, y = 20, rule = B3/S23
38b2o$36bo4bo$35bo$35bo5bo$35b6o6$17b6o$16bo5bo$15b2o6bo$2b15o6bo$3o
20bo$o22bo$2o7b4o7b4o$2b7o3b2o4b2o$13bo2b2o$13b3o!
Code: Select all
x = 42, y = 20, rule = B3/S23
38b2o$36bo4bo$35bo$35bo5bo$35b6o6$17b6o$16bo5bo$15b2o6bo$2b15o6bo$3o
20bo$o22bo$2o7b4o7b4o$2b7o3b2o4b2o$13bo2b2o$13b3o!
Code: Select all
x = 57, y = 46, rule = 345/26/5
55.A$54.3A$55.A25$ADBA$B2A$D3ADCBA$C.A.DCBA$.BA7$54.2A$54.2B$54.2C$
54.2D$52.A.A$52.B4A$52.D2A.B$52.ABDC!
The problem is that I can't think of anything that I think of any thing that solves the blinker+glider-esque issue, apart from limiting bounding box.One thing we do need to settle is whether to limit size based only on population size (with some added clause to clear up the blinker+glider)
Code: Select all
x = 24, y = 24, rule = restricted-b2s245678
.C$BA5.2A$3.BC2.BC$2.CA2B$2.BC.2B.BA$3.2CACA$4.CB2.C$.AC2.A.A$.AB.C.B
$4.A11$23.B$22.CB$21.BAB$20.3C!
Code: Select all
x = 4, y = 10, rule = B3/S23:T0,10
3bo$o2bo$2b2o$b3o$b3o$b3o$b3o$2b2o$o2bo$3bo!
Code: Select all
x = 14, y = 21, rule = B3/S23:T0,21
13bo$13bo$10bo2bo$12b2o$12b2o$10bo2bo$13bo$obob2o3bo3bo$o4bo3bo3bo$9bo
3bo$bo3bo3bo3bo$9bo3bo$o4bo3bo3bo$obob2o3bo3bo$13bo$10bo2bo$12b2o$12b
2o$10bo2bo$13bo$13bo!