double wireworld

[ssaamm]

I have finally formulated a way to make wireworld much more compact, and I call it (un-creatively), "double wireworld". It's as simple as having a second type of wire, and an "always on" cell. I made my first rule table creating it, too, and I think I did a pretty good job on it. Heresha go.

Code: Select all

#double wireworld
#made to make wireworld smaller and more complicated

#wire 1 is like the regular wireworld standard
#wire 2 is like it, but it only will light if there is 2 or 3 touching it
#the 7th one (white) always counts as on

n_states:8
neighborhood:Moore
symmetries:rotate8reflect
var a={3,6,7}
var b={3,6,7}
var c={3,6,7}

var d={0,1,2,3,4,5,6,7}
var e={0,1,2,3,4,5,6,7}
var f={0,1,2,3,4,5,6,7}
var g={0,1,2,3,4,5,6,7}
var h={0,1,2,3,4,5,6,7}
var i={0,1,2,3,4,5,6,7}
var j={0,1,2,3,4,5,6,7}
var k={0,1,2,3,4,5,6,7}

var s={0,1,2,4,5}
var t={0,1,2,4,5}
var u={0,1,2,4,5}
var v={0,1,2,4,5}
var w={0,1,2,4,5}
var x={0,1,2,4,5}
var y={0,1,2,4,5}
var z={0,1,2,4,5}


#when wire 1 touches 1 or 2 sparks, it becomes spark 1
1,a,d,u,v,w,x,y,z,3
1,a,t,b,v,w,x,y,z,3
1,a,t,u,b,w,x,y,z,3
1,a,t,u,v,b,x,y,z,3

#when wire 2 touches 2 or 3 sparks, it becomes spark 2
4,a,b,d,v,w,x,y,z,6
4,a,t,b,v,d,x,y,z,6
4,a,t,u,b,w,d,y,z,6
4,a,b,u,c,w,x,y,z,6
4,a,b,u,v,c,x,y,z,6

#spark 1 always becomes tail 1
3,d,e,f,g,h,i,j,k,2

#spark 2 always becomes tail 2
6,d,e,f,g,h,i,j,k,5

#tail 1 always becomes wire 1
2,d,e,f,g,h,i,j,k,1

#tail 2 always becomes wire 2
5,d,e,f,g,h,i,j,k,4

Code: Select all

color=0 050 050 050
color=1 255 128 000
color=2 000 128 255 
color=3 128 255 255
color=4 000 255 128
color=5 255 000 128 
color=6 255 128 255
color=7 255 255 255

it was just a blast working with those bound variables here. But I could get by. And while we're on the subject, are there any tables that actually make use of those bound variables, or is it just something widely despised?

[Axaj]

This is not bad at all. I have a few recommendations though: first of all, replace that always-on state with a crossover, or something that will allow such. Otherwise, this rule is mostly useless. Also, it's best to post a few sample patterns as well to make sure everyone names the rule table file the same thing! On the topic of bound vs unbound variables, I have proposed to have an option to declare it, but it has not been implemented yet. And yes, they do have some (while little) use.