Skip to content
McJty edited this page Sep 29, 2016 · 18 revisions

Things you can do with RFTools Control

  • Make sure an inventory or storage system has at least a certain number of some item and if it goes below craft new items
  • Automatically craft items on request. Even when some of the ingredients need to be crafted as well (recursive autocrafting)
  • Automate more complicated crafting systems as long as they have a way to accept ingredients and react to redstone
  • Regulate the amount of liquid in a tank (useful for Deep Resonance lava tank which needs to be between 40 and 60%)
  • On request, generate a bunch of materials
  • Regulate power generation based on various factors. Like if there is enough charcoal in system switch to coal generators, otherwise enable backup power bank and give alarm to player
  • Regulate RCL fluid handling for Deep Resonance using the four opcodes that Deep Resonance adds
  • Regulate the timing of an Endergenic powergenerator
  • Sort items based on various factors. For example, if you have a tree form you could let a part of the logs go to furnaces for charcoal production, a part of the logs to your storage for general crafting. Similarly for the rftools spawner you can have part of the wheat that is produced go to the spawner and the rest to craft bread
  • Precisely control the amount of materials to feed into the matter beamers for the rftools spawner so that nothing is lost
  • Collection statistics and display on rftools screens: count how many items some farm produced
  • Remove a pickaxe or other tool from a auto-placer if it gets broken and repair it
  • Program mini games like memory, mastermind, ...
  • Much more...

Plans for the future

  • Network booster to extend the range of a networked processor from 17x17x17 to 33x33x33
  • Support for networked processors to communicate (send messages) to each other
  • Hand-held crafting station so you can remotely order things to be crafted
  • Hand-held processor controller so you can issue commands and do things with a processor remotely
  • More fluid support, including opcodes to move around fluids
  • Possibly integrate with the RFTools storage scanner so that you can autocraft from there
  • Support for reading TESLA power values

Tips and Tricks

  • In the programmer GUI you can use the ctrl key to select opcodes or you can ctrl-double click to select an entire sequence of opcodes. You can then use Ctrl-C (copy) or Ctrl-X (cut) that sequence and use Ctrl-V (paste) to paste it elsewhere. It will be put as a JSON string in the clipboard so this is also a way to share programs.
  • Ctrl-A in the programmer GUI will select all opcodes.
  • In the programmer GUI you can press while hovering over an opcode icon to get more information. If you do this above the icons in the left list then you get detailed information on how the icon works and what kind of parameters it supports. If you do this above the icons in the grid then it will show you the values that you set for all the parameters so that you don't have to click on it to examine that.
  • Use the 'Val' button in the programmer GUI to validate your programs. It will give errors for unreachable opcodes and errors for opcodes where there are missing parameters. Doubleclicking on an error line will highlight the opcode that is wrong.
  • Variables and slot indices start counting at 0. So the first slot that is available for your program is at index 0. Same for variables.
  • Think before you add too many cores to a processor. If there are multiple cores then multiple programs can run at the same time. And sometimes that may give weird results if your programs are not designed to run multiple times.
  • Use 'db debug' in the processor console to enable debug mode. This will halt your programs and allow you to single step through them (db s ) or show the current last value (db last). You can also resume the programs with 'db resume'
Clone this wiki locally