2.1.6 - New UI text interfaces

Updated it to use Progammable block screen for outputs and removed deprecated code.

2.1.5 - Handled bug in grinders and drills

Thanks @ Ver' Leth for your diligence in picking at the script.

Bug: After update for allowing: grinders, drills, and welders to run off of same factory, I introduced a bug that ignored everything except welders. Whoops!

Using the mode: setting in the CustomData, you can control which blocks are running using the keywords: weld, grind, or drill.

2.1.4 - Added option to change Y start iteration.

Per request by @Nocturnal 2nd, you can now control which iteration the script starts at. Setting the value to zero (0) will effectively make the factory begin iterating horizontally at it's starting height. Default behavior is to increment vertically by one before starting the horizontal iteration.

For now the variable must be changed in the code, and can be found under the "Custom Requests" section: STARTING_Y_ITERATION. This may be moved to a configuration variable later, but to avoid another major version I have taken this route.

2.1.3 - Added debug outputs

• This update features extra outputs to the debugging menu for better tracking of behavior.

2.1.2 - Bug fix

• Thanks to @Bluebarry Cat for helping me diagnose some bugs in the new feature (again).
  
• This update features bug fixes including a lock on the last z interval that prevented the factory to continue, not turning off drills/grinders on the stop command, and other minor optimizations/bug fixes along the way.

2.1.1 - Bug fix

• Thanks to @Bluebarry Cat for helping me diagnose some bugs in the new feature.
  
• This update features bug fixes, optimizations, and removal of that annoying compiler warning ;).
  
• For fun I updated the LCD output.

2.1 - Feature Request.

• You can now skip to an specified y and z iteration.
  
  Previously if you stopped your factory in the middle of an operation and wanted to continue, you would have to start all over. This feature will move the factory to the desired y and z iterations and then automatically transition to the run command where it will continue (with the x iteration) as if it just reached the y and z iteration!
  
  Thanks to @Bluebarry Cat!
  
  Simply run with the following command:
  
  skip:y,z - NOTE: Replace y and z here with the integer iteration you wish to skip to.
  
  For example:
  
  skip:3,2
  
  This command will move your factory to Y iteration: 3 and Z iteration: 2. Once the factory reaches the desired iterations, it will trigger the "run" command automatically.

2.0 - Major update (not really, but new version is not compatible with the last so it's convention 8D )

• Compatible with grinders and welders.
  
  The "build" command has been changed to "run". For any existing builds you must clear the PB.CustomData (be sure to copy it somewhere else first if you want to save em) and allow the script to recreate it.
  
  
• Added mode configuration.
  
  If you want to take advantage of the new modes, try a setup with the Y pistons' piston-head facing down (see pictures in description and in the guide).

1.1 - Minor updates

• Accounted for small grid welders.
  
  Large grid welders have too large of a weld-range and make the script ineffective when building complex designs. Small grid welders however can only weld the area directly in front of them which makes for a much more effective 3D printer. Changes to accommodate this have been included in this update.
  
  
• Script improvements.
  
  
• Fixed other bugs along the way.

Original version.

Script can control x,y,z oriented pistons to iterate across a build area that is defined by the length of the pistons in each direction (one piston in each direction results in a 7x7x4 build area). The script will turn a welder on/off when it is welding or stopped (respectively). The script assumes that the build is a large grid, but can weld large or small grids.