Generalized Wire Automata

[twinb7]

After seeing WireWorld and a variant Bliptile I thought it would be interesting to explore a family of wire automata that all share similar properties.

-All family members have 3 states: A wire, an electron head, and an electron tail.
-An electron head always becomes an electron tail.
-An electron tail always becomes a wire.
-A wire becomes an electron head if it is surrounded by an exact number of neighbors.

The rule is formatted (neighbors)(neighborhood) (V=Von Neumann, M=Moore, H=Hexagonal, T=triangular...)

WireWorld is then 12M. Bliptile is 1V.


Edit: The convention for state numbering-
State 1: Electron head
State 2: Electron tail
State 3: Wire

[c0b0p0]

Here is 1H (perhaps the easiest-to-engineer rule!).

Code: Select all

@RULE 1H

@TABLE




n_states:4

neighborhood:hexagonal
symmetries:permute


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

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

var c={0,1,2,3}

var d={0,1,2,3}

var e={0,1,2,3}

var f={0,1,2,3}

var g={0,2,3}

var h={0,2,3}

var i={0,2,3}

var j={0,2,3}

var k={0,2,3}

var l={0,2,3}

1,a,b,c,d,e,f,2

2,a,b,c,d,e,f,3

3,g,h,i,j,k,1,1

Here is a near diode, with two near logic gates.

Code: Select all

x = 34, y = 3, rule = 1H
6.3C$A7C.24CA$7.2C!

Code: Select all

x = 22, y = 8, rule = 1H
A14C$14.C$A18C2$A13C$14.C$A14C$15.7C!

[twinb7]

More 1H patterns.

Code: Select all

x = 58, y = 38, rule = 1H
10.A3C4.4C$13.4C4.4C$13.C7.C10.C.C2.C2.2C$14.C7.C9.C.C.C.C.C.C$33.C2.
C.C.2C$32.C.C.C.C.C.C$14.A3C14.C.C2.C2.C.C$17.3CA$17.C$18.C11$3.2C19.
2C14.2C2.3C2.C2.2C2.2C$3.C.C18.C.C13.C.C2.C2.C.C.C.C.C$3.2C.3C15.C2.C
12.C.C2.C2.C.C.C.C.2C$3.C.C3.C13.2C3.C11.C.C2.C2.C.C.C.C.C$A3C.C2.2C
10.A3C.C3.C10.2C2.3C2.C2.2C2.2C$3.C.5C14.2C2.2C$3.C2.C3.C13.C2.2C.5C$
4.3C4.4C10.3C.2C3$3.2C19.2C$3.C.C18.C.C$3.2C.3C15.C2.C$3.C.C3.C13.2C
3.C$4C.C2.2C10.4C.C3.C$3.C.5C14.2C2.2C$3.C2.C3.C13.C2.2C.4CA$4.3C4.3C
A10.3C.2C!

[Sphenocorona]

You may want to change the name to "Wire1H" or something to prevent Golly having confusion with standard outer-totalistic rules like B/S1H.

Also, I'm pretty sure this is the smallest working diode in 1H:

Code: Select all

x = 12, y = 11, rule = 1H
4.3C$4.C2.C$5C.2C$4.4C$8.3CA2$4.3C$4.C2.C$A4C.2C$4.4C$8.4C!

Alternate form for Wire1H name:

Code: Select all

x = 12, y = 11, rule = Wire1H
4.3C$4.C2.C$5C.2C$4.4C$8.3CA2$4.3C$4.C2.C$A4C.2C$4.4C$8.4C!

[twinb7]

In that case we'll do just that, prefacing the rules with 'Wire'.

Wire1H.rule...

Code: Select all

@RULE Wire1H

@TABLE
n_states:4
neighborhood:hexagonal
symmetries:permute

var a={0,1,2,3}
var b={0,1,2,3}
var c={0,1,2,3}
var d={0,1,2,3}
var e={0,1,2,3}
var f={0,1,2,3}
var g={0,2,3}
var h={0,2,3}
var i={0,2,3}
var j={0,2,3}
var k={0,2,3}
var l={0,2,3}

1,a,b,c,d,e,f,2
2,a,b,c,d,e,f,3
3,g,h,i,j,k,1,1

@COLORS
0 48 48 48
1 0 0 255
2 255 255 255
3 255 0 0

And that diode is wonderful and I'm so glad it exists

[c0b0p0]

@twinb7: Advancing one of the signals is sufficient to make an OR gate, as shown below.

Code: Select all

x = 16, y = 12, rule = 1H
ACBA3C$6.4CAB3CA$6.C$7.C$7.C$7.C$7.C$7.C$7.C$7.C$7.C$7.C!

Using Sphenocorona's diode, here is a NOT gate. 1H has now been proven Turing-complete.

Code: Select all

x = 31, y = 18, rule = 1H
20.3C$20.C2.C$BA19C.2C$20.4C$20.C.9C$20.C9.C$20.C9.C$20.C9.C$20.C9.C$
20.C8.2C$20.C8.2C$20.C9.A$20.C$20.C$20.C$20.C$20.C$20.C!

[twinb7]

Not quite so simple, c0b0p0.
Notice the different output timings... This shouldn't be incredibly complicated to fix but is still a problem. I'll work on it.

Code: Select all

x = 26, y = 12, rule = 1H
4C5.A3C5.A3C$3.4CA4.5C4.4CA$3.C8.C8.C$4.C8.C8.C$4.C8.C8.C$4.C8.C8.C$
4.C8.C8.C$4.C8.C8.C$4.C8.C8.C$4.C8.C8.C$4.C8.C8.C$4.C8.C8.C!

Code: Select all

x = 26, y = 12, rule = Wire1H
4C5.A3C5.A3C$3.4CA4.5C4.4CA$3.C8.C8.C$4.C8.C8.C$4.C8.C8.C$4.C8.C8.C$
4.C8.C8.C$4.C8.C8.C$4.C8.C8.C$4.C8.C8.C$4.C8.C8.C$4.C8.C8.C!

Second, the NOT gate needs to be fixed in a few ways. Look a bit closer at it.

Here is a working one:

Code: Select all

x = 30, y = 9, rule = Wire1H
CBA$C2.C$C3.6C$.C2.C4.7CAB10CAB$2.3C4.C$9.C$9.C$9.C$9.C!

EDIT:
What would be really useful to me now would be an A AND NOT B gate... It would let me make basically everything else left in a compact method.

[flipper77]

EDIT:
What would be really useful to me now would be an A AND NOT B gate... It would let me make basically everything else left in a compact method.

Using the same method I used to make a Bliptile OR gate, here's a Wire1H OR gate, as well as an A AND NOT B gate just because you asked for it:

Code: Select all

x = 41, y = 18, rule = Wire1H
B13.B13.B$.C13.A13.A$2.4C10.4C10.4C$3.C.6CAB4.C.7CB4.C.6CAB$4.3C11.3C
11.3C$7.C13.C13.C$7.C13.C13.C$7.C13.C13.C2$.B12.B13.B$2.4C9.A3C10.A3C
$3.C.5CAB4.C.6CB5.C.5CAB$3.4C9.4C10.4C$3.C3.C8.C3.C9.C3.C$3.C2.2C8.C
2.2C9.C2.2C$4.4C9.4C10.4C$8.C12.C13.C$9.C12.C13.C!

[twinb7]

@flipper77

I managed to make my own A AND NOT B gate, slightly larger than your own:

Code: Select all

x = 17, y = 17, rule = Wire1H
2$.A3.3C$.C3.C2.C$.C.3C.2C$.C.C.4C$2.2C5.C$5.3C2.6C$5.C2.C.C.C$.CBA2C
.2C.3C$5.4C.C$.BAC5.2C2$.A2C!

The three disconnected wires demonstrate that the B input can be any of three different phases.

Using it I made an A AND B gate with A AND NOT (A AND NOT B).

Code: Select all

x = 35, y = 17, rule = Wire1H
2C$C.C$C.C5.2C$C.C5.C.C$A.C5.C.C$3.6C.C6.3C$4.C6.C5.C2.C$3.A.C2.3C.C
2.3C.2C$4.C.C.C2.C.C.C.4C$5.C.2C.2C.C.C5.C$6.C.4C2.2C.3C2.13C$6.C5.C
4.C2.C.C.C$6.C.3C2.5C.2C.3C$6.C.C2.C.C.C.4C.C$7.2C.2C.3C5.2C$8.4C.C$
12.2C!

This can be made smaller with your similarly smaller ANDNOT gate.
NOW H1 is turing-complete.


EDIT: Smaller AND gate.

Code: Select all

x = 15, y = 8, rule = Wire1H
8.3C$8.C2.C$A6C.C.2C$7.2C.5C$2.AC2.2C2.C.C$4.C.7C$4.C.C.C$5.4C!

[wirehead]

I've also been trying to generalize wire-like automata too before I joined this forum (about an hour ago). However, my classification is a bit more general and also includes rules such as LLLL, NoTimeAtAll and Flow6: The rules are:

1. State 0 (the background) always remains the background. This forbids patterns from expanding and eliminates construction rules such as WWEJ3 (but as that is an extension of Wireworld, a universal-construction GWCA would naturally also be an extension).
2. If there are multiple types of wire, the multiple subsets of states S1, S2, S3... Sn are partitioned such that all sets are mutually disjoint from each other.
3. No cell in a state s1 where s1 is in S will ever transition to a state s2 not in S -- that is, a cell in some wire type will always remain the same wire type.
4. Each subset S can each be partitioned into n subsets of types (T), where n = 1, 2, 3 or 4.
5. If a cell in state p which is in Tk, changes state to a new state q, then q must be in T(k+1 mod n). Alternatively, if x and y are states out of the same T set, a cell cannot transition from x to y without going through one or more additional states.

I'm having trouble being able to generalize this into a rule-string format. Does anyone have ideas on this?

EDIT: yikes, this is a really, really, stale thread. Maybe I should have started a new one.

[breaker's glider gun]

I've also been trying to generalize wire-like automata too before I joined this forum (about an hour ago). However, my classification is a bit more general and also includes rules such as LLLL, NoTimeAtAll and Flow6: The rules are:

1. State 0 (the background) always remains the background. This forbids patterns from expanding and eliminates construction rules such as WWEJ3 (but as that is an extension of Wireworld, a universal-construction GWCA would naturally also be an extension).
2. If there are multiple types of wire, the multiple subsets of states S1, S2, S3... Sn are partitioned such that all sets are mutually disjoint from each other.
3. No cell in a state s1 where s1 is in S will ever transition to a state s2 not in S -- that is, a cell in some wire type will always remain the same wire type.
4. Each subset S can each be partitioned into n subsets of types (T), where n = 1, 2, 3 or 4.
5. If a cell in state p which is in Tk, changes state to a new state q, then q must be in T(k+1 mod n). Alternatively, if x and y are states out of the same T set, a cell cannot transition from x to y without going through one or more additional states.

I'm having trouble being able to generalize this into a rule-string format. Does anyone have ideas on this?

EDIT: yikes, this is a really, really, stale thread. Maybe I should have started a new one.

1 rules out flow6.

[wirehead]

1 rules out flow6.

Whoops, meh bad. I forgot that Flow6 was a UC rule. What I was really thinking of was the feature in Flow6 where wire crossings are trivial because the wire will not turn to head if it has head or tail in the 2a configuation.

Code: Select all

x = 7, y = 7, rule = Flow6
4A$A2.A$A2.B$3AE3A$3.A2.A$3.A2.A$3.4A!

[PHPBB12345]

Here is Wire12H:

Code: Select all

@RULE Wire12H

@TABLE
n_states:4
neighborhood:hexagonal
symmetries:permute
var a={0,1,2,3}
var b={0,1,2,3}
var c={0,1,2,3}
var d={0,1,2,3}
var e={0,1,2,3}
var f={0,1,2,3}
var g={0,2,3}
var h={0,2,3}
var i={0,2,3}
var j={0,2,3}

1,a,b,c,d,e,f,2
2,a,b,c,d,e,f,3
3,1,a,g,h,i,j,1

@COLORS
0  48  48  48
1   0 128 255
2 255 255 255
3 255 128   0

Diode:

Code: Select all

x = 20, y = 7, rule = Wire12H
7.3C$A8C.8C$8.3C2$9.3C$2.A7C.9C$10.3C!

OR:

Code: Select all

x = 36, y = 28, rule = Wire12H
A11C$12.2C$12.14C$13.C.C$14.3C$15.2C$17.C$7.A10C3$5.A11C$17.2C$17.14C
$18.C.C$19.3C$20.2C$22.C$12.11C3$10.12C$22.2C$22.14C$23.C.C$24.3C$25.
2C$27.C$17.A10C!

XOR:

Code: Select all

x = 31, y = 27, rule = Wire12H
6.3C$A7C.2C$7.3C.2C$12.9C$8.3C.2C$2.A7C.2C$9.3C4$11.3C$5.A7C.2C$12.3C
.2C$17.9C$13.3C.2C$7.8C.2C$14.3C4$16.3C$10.8C.2C$17.3C.2C$22.9C$18.3C
.2C$12.A7C.2C$19.3C!

ANDNOT:

Code: Select all

x = 57, y = 51, rule = Wire12H
A11C$12.2C.2C.3C$12.4C.3C.2C$13.C.C3.3C.2C$14.3C7.13C$15.2C3.3C.2C$
17.C.3C.2C$7.A10C.C.3C$18.C.C$18.C.C$19.2C10$10.A11C$22.2C.2C.3C$22.
4C.3C.2C$23.C.C3.3C.2C$24.3C7.13C$25.2C3.3C.2C$27.C.3C.2C$17.11C.C.3C
$28.C.C$28.C.C$29.2C10$20.12C$32.2C.2C.3C$32.4C.3C.2C$33.C.C3.3C.2C$
34.3C7.13C$35.2C3.3C.2C$37.C.3C.2C$27.A10C.C.3C$38.C.C$38.C.C$39.2C!

AND:

Code: Select all

x = 73, y = 53, rule = Wire12H
12.2C.2C.2C$11.2C.2C.2C.2C2.3C$A11C10.4C.2C$12.2C.2C.3C4.3C.2C$12.4C.
3C.2C7.23C$13.C.C3.3C.2C.3C.2C$14.3C7.4C.2C$15.2C3.3C.2C.3C$17.C.3C.
2C$7.A10C.C.3C$18.C.C$18.C.C$19.2C8$22.2C.2C.2C$21.2C.2C.2C.2C2.3C$
10.A11C10.4C.2C$22.2C.2C.3C4.3C.2C$22.4C.3C.2C7.23C$23.C.C3.3C.2C.3C.
2C$24.3C7.4C.2C$25.2C3.3C.2C.3C$27.C.3C.2C$17.11C.C.3C$28.C.C$28.C.C$
29.2C8$32.2C.2C.2C$31.2C.2C.2C.2C2.3C$20.12C10.4C.2C$32.2C.2C.3C4.3C.
2C$32.4C.3C.2C7.23C$33.C.C3.3C.2C.3C.2C$34.3C7.4C.2C$35.2C3.3C.2C.3C$
37.C.3C.2C$27.A10C.C.3C$38.C.C$38.C.C$39.2C!

Wire Crossing:

Code: Select all

x = 58, y = 51, rule = Wire12H
16.3C$14.4C.2C$10.3C.C2.3C.2C$A11C.2C7.14C$11.3C.2C.3C.2C$16.4C.2C$12.
3C.2C.3C.2C$2.A11C.2C7.14C$13.3C.C2.3C.2C$18.4C.2C$21.3C10$26.3C$24.4C
.2C$20.3C.C2.3C.2C$10.A11C.2C7.14C$21.3C.2C.3C.2C$26.4C.2C$22.3C.2C.3C
.2C$12.12C.2C7.14C$23.3C.C2.3C.2C$28.4C.2C$31.3C10$36.3C$34.4C.2C$30.
3C.C2.3C.2C$20.12C.2C7.14C$31.3C.2C.3C.2C$36.4C.2C$32.3C.2C.3C.2C$22.
A11C.2C7.14C$33.3C.C2.3C.2C$38.4C.2C$41.3C!

[breaker's glider gun]

Here is Wire12H:

Code: Select all

@RULE Wire12H

@TABLE
n_states:4
neighborhood:hexagonal
symmetries:permute
var a={0,1,2,3}
var b={0,1,2,3}
var c={0,1,2,3}
var d={0,1,2,3}
var e={0,1,2,3}
var f={0,1,2,3}
var g={0,2,3}
var h={0,2,3}
var i={0,2,3}
var j={0,2,3}

1,a,b,c,d,e,f,2
2,a,b,c,d,e,f,3
3,1,a,g,h,i,j,1

@COLORS
0  48  48  48
1   0 128 255
2 255 255 255
3 255 128   0

Diode:

Code: Select all

x = 20, y = 7, rule = Wire12H
7.3C$A8C.8C$8.3C2$9.3C$2.A7C.9C$10.3C!

OR:

Code: Select all

x = 36, y = 28, rule = Wire12H
A11C$12.2C$12.14C$13.C.C$14.3C$15.2C$17.C$7.A10C3$5.A11C$17.2C$17.14C
$18.C.C$19.3C$20.2C$22.C$12.11C3$10.12C$22.2C$22.14C$23.C.C$24.3C$25.
2C$27.C$17.A10C!

XOR:

Code: Select all

x = 31, y = 27, rule = Wire12H
6.3C$A7C.2C$7.3C.2C$12.9C$8.3C.2C$2.A7C.2C$9.3C4$11.3C$5.A7C.2C$12.3C
.2C$17.9C$13.3C.2C$7.8C.2C$14.3C4$16.3C$10.8C.2C$17.3C.2C$22.9C$18.3C
.2C$12.A7C.2C$19.3C!

ANDNOT:

Code: Select all

x = 57, y = 51, rule = Wire12H
A11C$12.2C.2C.3C$12.4C.3C.2C$13.C.C3.3C.2C$14.3C7.13C$15.2C3.3C.2C$
17.C.3C.2C$7.A10C.C.3C$18.C.C$18.C.C$19.2C10$10.A11C$22.2C.2C.3C$22.
4C.3C.2C$23.C.C3.3C.2C$24.3C7.13C$25.2C3.3C.2C$27.C.3C.2C$17.11C.C.3C
$28.C.C$28.C.C$29.2C10$20.12C$32.2C.2C.3C$32.4C.3C.2C$33.C.C3.3C.2C$
34.3C7.13C$35.2C3.3C.2C$37.C.3C.2C$27.A10C.C.3C$38.C.C$38.C.C$39.2C!

AND:

Code: Select all

x = 73, y = 53, rule = Wire12H
12.2C.2C.2C$11.2C.2C.2C.2C2.3C$A11C10.4C.2C$12.2C.2C.3C4.3C.2C$12.4C.
3C.2C7.23C$13.C.C3.3C.2C.3C.2C$14.3C7.4C.2C$15.2C3.3C.2C.3C$17.C.3C.
2C$7.A10C.C.3C$18.C.C$18.C.C$19.2C8$22.2C.2C.2C$21.2C.2C.2C.2C2.3C$
10.A11C10.4C.2C$22.2C.2C.3C4.3C.2C$22.4C.3C.2C7.23C$23.C.C3.3C.2C.3C.
2C$24.3C7.4C.2C$25.2C3.3C.2C.3C$27.C.3C.2C$17.11C.C.3C$28.C.C$28.C.C$
29.2C8$32.2C.2C.2C$31.2C.2C.2C.2C2.3C$20.12C10.4C.2C$32.2C.2C.3C4.3C.
2C$32.4C.3C.2C7.23C$33.C.C3.3C.2C.3C.2C$34.3C7.4C.2C$35.2C3.3C.2C.3C$
37.C.3C.2C$27.A10C.C.3C$38.C.C$38.C.C$39.2C!

Wire Crossing:

Code: Select all

x = 58, y = 51, rule = Wire12H
16.3C$14.4C.2C$10.3C.C2.3C.2C$A11C.2C7.14C$11.3C.2C.3C.2C$16.4C.2C$12.
3C.2C.3C.2C$2.A11C.2C7.14C$13.3C.C2.3C.2C$18.4C.2C$21.3C10$26.3C$24.4C
.2C$20.3C.C2.3C.2C$10.A11C.2C7.14C$21.3C.2C.3C.2C$26.4C.2C$22.3C.2C.3C
.2C$12.12C.2C7.14C$23.3C.C2.3C.2C$28.4C.2C$31.3C10$36.3C$34.4C.2C$30.
3C.C2.3C.2C$20.12C.2C7.14C$31.3C.2C.3C.2C$36.4C.2C$32.3C.2C.3C.2C$22.
A11C.2C7.14C$33.3C.C2.3C.2C$38.4C.2C$41.3C!

Bit(EXTEMELY reducible probably)

Code: Select all

x = 16, y = 17, rule = Wire12H
8.4C$8.C3.C$2.3C3.C4.C$BA2C.4C5.C$3.3C2.2C5.C$9.C.3C.C$10.2C.3C$12.3C
2$8.4C$8.C3.C$2.3C3.C4.C$BA2C.4C5.C$3.3C2.2C5.C$9.C.3C.B$10.2C.2CA$12.
3C!

[Sarah]

whoops

Code: Select all

x = 17, y = 9, rule = Wire12H
$8.BACB$8.C3.A$2.CAC3.A4.C$.CAB.BACB5.B$3.CAC2.BA5.A$9.A.ACB.C$10.CB.
BCB$12.ACB!

[Yoel]

WireWorld generalizations have been already discussed by blah and others. Wire2 in your terminology would be 2M. I don't see any reason to limit such rules to this very tiny subset though. Any rule, including CGOL, can be wired the same way, although typically people discuss rules that allow easy c/1 signals and at least one extra generation, which naturally determines signal direction. Nothing prevents to wire higher generation rules like StarWars as well. WireWorld is simply tamed /12/3, in itself useless and 100% explosive.

Hexagonal, triangular, etc. may be novel though, never saw this before!

Your Wire12H looks very aesthetically pleasing to me.

[breaker's glider gun]

BWAHAHA (this doesn't fit, but I thought it up:)

Code: Select all

x = 7, y = 10, rule = Wire12H+holders
2.4AB$2.C$2.C$2.C$.2C$2CGC$C.2C$C.C.C$2.C.C$4.C!

TINY diode:

Code: Select all

x = 14, y = 3, rule = Wire12H+holders
BA3CKCG5C2$.5CKCG3CAB!

(only works for size 1)

also, can I have help on this "megaproject?"

Code: Select all

@RULE Wire12allpermutations

@TABLE
n_states:13
neighborhood:Moore
symmetries:Rotate4Reflect
var H1 = 
var T1 = 
0,   0000
1,   W1111
2,   W1110
3,   W1101
4,   W1100
5,   W1011
6,   W1010
7,   W1001
8,   W1000
9,   W0111
10, W0110
11, W0101
12, W0100
13, H1111
14, H1110
15, H1101
16, H1100
17, H1011
18, H1010
19, H1001
20, H1000
21, H0111
22, H0110
23, H0101
24, H0100
25, T1111
26, T1110
27, T1101
28, T1100
29, T1011
30, T1010
31, T1001
32, T1000
33, T0111
34, T0110
35, T0101
36, T0100

[wirehead]

BWAHAHA (this doesn't fit, but I thought it up:)

Code: Select all

x = 7, y = 10, rule = Wire12H+holders
2.4AB$2.C$2.C$2.C$.2C$2CGC$C.2C$C.C.C$2.C.C$4.C!

where is the rule Wire1H+holders ?

Also, not trying to make this thread even more confusing, but I have an idea for another notation: things like this can be made using a modified hensel string that lists the specific states after each transition, so for this one, and using states 0-4 only, it would be B1/S-[3]/3H. Can't make the full string until I see the behavior of the rest of the rule.

[breaker's glider gun]

where is the rule Wire1H+holders ?

Done!

Code: Select all

x = 8, y = 16, rule = Wire1H+holders
5.C$5.C$5.C$5.C$4.2C$BA5C$5.C3$6.B$6.A$6.C$6.C$5.2C$.7C$6.C!

[wirehead]

where is the rule Wire1H+holders ?

Done!

Code: Select all

x = 8, y = 16, rule = Wire1H+holders
5.C$5.C$5.C$5.C$4.2C$BA5C$5.C3$6.B$6.A$6.C$6.C$5.2C$.7C$6.C!

Ok, I found the rule table, but can someone explain the behavior of this rule? It looks like there are multiple "flavors" of wire but I can't figure out the transition rules.

[breaker's glider gun]

where is the rule Wire1H+holders ?

Done!

Code: Select all

x = 8, y = 16, rule = Wire1H+holders
5.C$5.C$5.C$5.C$4.2C$BA5C$5.C3$6.B$6.A$6.C$6.C$5.2C$.7C$6.C!

Ok, I found the rule table, but can someone explain the behavior of this rule? It looks like there are multiple "flavors" of wire but I can't figure out the transition rules.

So basically, the green slows down the tail, and the yellow slows down the head.

Also, I've edited it so that 2 heads can "bust through" a yellow cell, and two tails can do the same to green cells:

Code: Select all

x = 17, y = 14, rule = Wire12H+holders
3.CGC$BA3C.5C3$5.CGC$2.5C.3CAB3$7.CKC$4.BA3C.5C3$9.CKC$6.5C.3CAB!

Code: Select all

x = 11, y = 2, rule = Wire12H+holders
3.4C$BA5CK3C!

[wirehead]

So basically, the green slows down the tail, and the yellow slows down the head.

Also, I've edited it so that 2 heads can "bust through" a yellow cell, and two tails can do the same to green cells:

Code: Select all

x = 17, y = 14, rule = Wire12H+holders
3.CGC$BA3C.5C3$5.CGC$2.5C.3CAB3$7.CKC$4.BA3C.5C3$9.CKC$6.5C.3CAB!

I like it... The green cells make the electrons longer, and the yellow make them shorter.