Automation

Preliminary thoughts on Automation.

3 Ways to Activate a Rune

 * Right click, push piston, minecart
 * This is to be as automation friendly as possible
 * Redstone signal can be translated to a piston
 * if minecart rolls over the key block, activates rune
 * Additionally, using a piston to touch another block creates a left-click event like punching or Damage Sensor.

Design Principle
Keep it Stupid Simple - We do not want a giant dictionary of runes that each have a narrow task. We want a handful of very useful, very versatile runes that take some kind of input so they can be used for a variety of tasks.

Runix should exploit as much vanilla capability as possible (redstone, pistons, enchantments) to avoid reinventing the wheel and ensure that it feels like core gameplay.

Notes from MateCraft

 * Key blocks for a redstone sensor don't do anything
 * Would you need signatures if you had Aetheric Link?
 * Do you need Many to One functionality or is One to One enough?
 * Aetheric link - two blocks => set an iron block, shows up in both locations.  Destroying one will destroy the other as well.
 * This means you can duplicate the block place event without ruining the economy
 * Just in case, place RunixFakeBlock at both locations and use the retexturing trick.
 * Pushing an Aetheric Linked block will move at both locations.  If the destination collides with a block, break the non-linked block
 * Now we have a very precise block breaker, useful for carving
 * Phoggle Sploggle Block -> State 1 State 2 or Air
 * Spleef Block behavior for Air
 * N state Toggle Blocks seem very necessary for circuits and builds

Runes

 * Aetheric Link
 * Build Master
 * Runecraft
 * FTP
 * Phase Field
 * Aether Goggles