Kyle
43cb258877
Make ghoststone conductive.
2013-02-07 08:30:15 -08:00
khonkhortisan
a5a4f2b65c
Merge pull request #69 from khonkhortisan/master
...
Keep vertical wire base from self-intersecting
2013-02-04 20:02:27 -08:00
Kyle
c23295409b
Keep vertical wire base from self-intersecting
...
on the bottom.
2013-02-04 15:25:36 -08:00
khonkhortisan
1da390d263
Merge pull request #50 from khonkhortisan/master
...
fix t-junction selectionbox when on (was node-sized)
2012-09-10 15:50:25 -07:00
Kyle
cee2574ff2
fix t-junction selectionbox when on
2012-09-10 15:48:06 -07:00
Kyle
d3b1c43ee1
crossing wire moved into mesecons
2012-09-07 13:18:53 -07:00
Kyle
6aa330e85c
depend on mesecons_delayer's all_rules instead of getting both insulated
...
and microcontroller rules
2012-09-05 10:09:53 -07:00
Kyle
9fbc4b4587
went back to large nodeboxes which agree with inventory image
2012-09-04 21:22:29 -07:00
Kyle
17fc6ac1f0
FACEDIR! (among other things)
2012-09-04 21:16:32 -07:00
Kyle
e65c5ca9dc
nodeboxes now show which sides connect
2012-09-03 11:50:43 -07:00
Kyle
b0142a7429
flat inventory image for easy gate identification
2012-09-01 23:27:23 -07:00
Kyle
845c275121
registering the on receptor makes placing a mesecon on the out port of
...
the gate update the circuitry after it
2012-09-01 22:06:25 -07:00
Kyle
0f7a87538d
(oops) forgot the "out" connection
2012-09-01 18:59:10 -07:00
Kyle
6f1296198c
simplified effector rules
2012-09-01 18:53:31 -07:00
Kyle
dc3fc4deb5
cut set_gate in half
2012-09-01 18:26:15 -07:00
Kyle
9af83593ac
added recipes
2012-09-01 17:07:00 -07:00
Kyle
efd06143b1
gates overheat
2012-09-01 16:10:23 -07:00
Kyle
b44f443fb2
nodeboxes
2012-09-01 13:48:16 -07:00
Kyle
f93930a478
gate output works
2012-09-01 13:07:18 -07:00
Kyle
6147c385cc
initial gates commit, logic behind gates works, more work to do.
2012-09-01 01:23:15 -07:00
Kyle
c228861c1f
recipe for blue lightstone from fiber, missing texture
2012-08-25 01:33:48 -07:00
khonkhortisan
68b99fed76
display µc programming like a sign
...
I had a grid that mapped buttons to pixels so pressing a button displayed a letter. I had one programming that was a positive match so the pixel turned on, and another programming that was negative and just passed the signal on to the next pixel. If I had to right-click on each µc to see its programming, it would take me longer to find a problem. If I can see the programming just by looking at it, I could find a typo much easier.
I'm not sure about the \n \n\r thing.
2012-08-21 10:35:34 -07:00