| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
|
|
|
|
|
|
fiber
|
|
|
|
receivers
|
|
|
|
other
|
|
|
|
|
|
|
|
designed)
|
|
|
|
tweak select box
|
|
|
|
isolated wires
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
code runs on is the same that sends the code
|
|
off in mesecons:turnoff
|
|
|
|
|
|
|
|
|
|
mesecon:register_effector(onstate, offstate, rules, function get_rules) rules and function get_rules are optional. You don't have to specify both onstate and offstate (required for e.g. removestone)
|
|
|
|
|
|
cooking saplings.
|
|
|
|
|
|
turn on)
|
|
solar panel doesn't actually need a side texture.
|
|
|
|
|
|
|
|
|
|
states, to allow wires without junction bumps to be textured differently.
|
|
|
|
|
|
purposes with a minor tweak.
|
|
|
