summaryrefslogtreecommitdiff
path: root/README.txt
diff options
context:
space:
mode:
authorFaceDeer <derksenmobile@gmail.com>2017-01-06 18:40:14 -0700
committerFaceDeer <derksenmobile@gmail.com>2017-01-06 18:40:14 -0700
commit795fc6ea931d91a826f2f913019a791263b8f62b (patch)
tree88370c473212ed9306f0fffdbb8661ea63d48b9a /README.txt
parent6af67133be0524a1482e512038c5c1267b0ba1b9 (diff)
add a bit of evil black smoke, why not
Diffstat (limited to 'README.txt')
-rw-r--r--README.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/README.txt b/README.txt
index 94fc9c9..557953e 100644
--- a/README.txt
+++ b/README.txt
@@ -223,6 +223,13 @@ Pusher controller:
Tips and tricks
===============
+To more easily visualize the operation of a Digtron, imagine that its cycle of operation follows these steps in order:
+
+* Dig
+* Move
+* Build
+* Allow dust to settle (ie, sand and gravel fall)
+
If you're building a repeating pattern of nodes, your periodicity should be one larger than your largest offset. For example, if you've laid out builders to create a set of spiral stairs and the offsets are from 0 to 11, you'll want to use periodicity 12.
A good way to program a set of builders is to build a complete example of the structure you want them to create, then place builders against the structure and have them "read" all of its facings. This also lets you more easily visualize the tricks that might be needed to allow the digtron to pass through the structure as it's being built. \ No newline at end of file