RFTools · Addon guide · Advanced
RFTools Control Beginner's Guide: Processors, Crafting Stations, and Visual Programming
RFTools Control transforms standard item and fluid routing into a deterministic, visual programming playground capable of handling your most complex factory automation. In this guide, you will learn how to assemble a Processor, link remote Nodes, and build your first opcode program in the Programmer. Mastering this system allows you to execute exact-count inventory transfers and multi-step crafting sequences with zero lag or overflowing buffers.
What you need
- Processor
- Programmer
- Program Card (at least one)
- CPU Core (B500, S1000, or EX2000)
- RAM Chip (at least one)
- Network Card (optional, only needed if connecting external Nodes)
- Node (optional, for remote inventory access)
- Crafting Station (optional, for automated crafting requests)
- A continuous Forge Energy (FE) or RF power supply
- Two Chests or Fluid Tanks to test item and fluid movement
Step by step
1Set Up and Power the Hardware
Place your Processor and Programmer adjacent to each other and connect the Processor to a steady RF/FE power cable. The Programmer does not consume power itself, as it is strictly an editing desk for your Program Cards. Place two test chests directly against the North and South faces of the Processor (or place a Node against remote chests connected on the same network channel).
Tip: If you use remote Nodes instead of placing chests directly against the Processor, you must insert a Network Card into the Processor and give each Node a unique name in its GUI.
2Install CPU Cores and RAM Chips
Right-click the Processor to open its main management GUI. Shift-right-click or drag at least one CPU Core (such as the basic CPU Core B500) and one RAM Chip into the dedicated expansion slots on the left side of the interface. Without both a core to execute instructions and memory to hold variables and threads, the Processor will remain completely inert even when powered.
Tip: Check JEI or the in-game RFTools Control manual to compare the instruction-per-tick speed of higher-tier CPU Cores.
3Allocate Card Slots and Internal Buffer
Look at the central grid inside the Processor GUI, which represents its internal item slots and expansion card availability. Before inserting a Program Card, click on the internal inventory slots to assign them to specific card slots (usually colored or numbered starting from 0). Because the Processor cannot telemetry-teleport items directly from Chest A to Chest B, it must pull items into these allocated internal slots first and push them out in a second step.
Tip: Always allocate at least two or three internal slots to your active Program Card slot so multiple operations do not overwrite the same holding space.
4Create an Event Trigger in the Programmer
Open the Programmer GUI and place a blank Program Card into the slot at the lower left. On the left sidebar, navigate to the green Event nodes (triggers) and drag a 'Redstone On' or 'Timer' opcode onto the main grid. Select the Timer opcode and look at the bottom parameter list; set the interval parameter to a modest tick delay (for example, 20 ticks for once per second) so the program loops reliably without eating up all your CPU cycles.
5Chain the Fetch Items Opcode
Find the blue Action opcodes in the left sidebar and drag 'Fetch Items' directly to the right of your Timer opcode. Hover over the edge of the Timer box until an arrow connector appears, then drag it to the Fetch Items box to establish execution order. Click the Fetch Items opcode to edit its parameters at the bottom: set the inventory side to North (where your input chest sits), specify an item filter or leave it blank for any item, set the amount to a small number like 4, and set the internal target slot to 0.
Tip: When setting parameters, click the parameter row at the bottom and select 'Constant' to type a fixed number or side directly.
6Chain the Push Items Opcode
Drag a 'Push Items' opcode onto the grid directly to the right of your Fetch Items box and connect them with a flow arrow. Select the Push Items box to configure its parameters: set the target inventory side to South (your output chest), set the internal source slot to 0 (matching where Fetch Items just placed the goods), and set the amount to 4. Your visual chain now reads: Timer -> Fetch Items (from North to Internal Slot 0) -> Push Items (from Internal Slot 0 to South).
Tip: To move liquids instead of items, follow this exact same logic using the 'Fetch Liquid' and 'Push Liquid' opcodes paired with an adjacent Fluid Workbench or tank.
7Save and Deploy the Program Card
Name your program in the text box inside the Programmer GUI; the card saves your visual layout automatically as you build it. Pull the Program Card out of the Programmer, open the Processor GUI, and place the card into the Program Card slot corresponding to the internal inventory slots you allocated in Step 3. Put a stack of items into the North chest and watch them transfer four at a time into the South chest every second.
Tip: If nothing moves, type 'db' or 'log' into the Processor's built-in console window to read the exact error code thrown by your CPU.
How it works
RFTools Control separates program execution into three distinct hardware duties: triggers (Events), execution threads (CPU Cores), and physical staging (Internal Processor Slots). Unlike standard item pipes that blindly push items whenever space is available, a Processor does nothing until a green Event opcode fires. Once triggered, the Processor assigns the connected chain of opcodes to a free CPU Core as a running thread.
Every item or fluid transfer is strictly a two-stage handshake. The Processor acts as a physically grounded middleman: it must first pull items from an external inventory (either touching the Processor directly or touching a networked Node) into its own allocated internal inventory slots. Only after the item resides inside the Processor's internal buffer can the next opcode push it out to the destination. This guarantees that exact item counts are verified before reaching a machine.
As you advance to automated crafting with the Crafting Station and Workbench, the logic shifts from simple timers to 'Craft' event triggers. When you request an item in the Crafting Station, it broadcasts a signal to the Processor. The Processor's 'Event Craft' opcode catches the request, fetches the ingredients into its internal slots, pushes them into a crafting grid or smelting machine, and finally pushes the finished product back to a Crafting Card ticket.
Common mistakes
- Forgetting to allocate internal inventory slots inside the Processor GUI: Fetch and Push opcodes will instantly fail with an 'Invalid Slot' exception if the Program Card slot does not have permission to use internal storage slot 0.
- Leaving event triggers disconnected or overlapping flow arrows: Every opcode chain must start with one green Event block, and each subsequent block must have a directional arrow pointing to it.
- Confusing relative internal slot numbers with physical slot numbers: If you allocate internal slots 4 and 5 to a Program Card, the code on that card refers to them as virtual slots 0 and 1 so your programs remain portable across different card slots.
- Starving the Processor of CPU threads using 1-tick timers: Setting a repeating Timer event to 1 tick without marking the event as 'Single' will spawn dozens of simultaneous threads, locking up all CPU Cores and halting other automation tasks.
FAQ
Why does my Processor say 'No CPU available' even though I put a CPU Core inside?
Your current program has likely entered an infinite loop or a fast Timer event has spawned multiple overlapping threads. Open the Processor GUI, check the 'Single' checkbox on your Event opcode in the Programmer so only one instance can run at a time, and run the 'reset' command in the Processor console.
When do I need a Node and a Network Card?
If your chests or machines are touching the six faces of the Processor itself, you do not need them. You only need a Network Card inside the Processor and Nodes placed against distant machines when you want to control inventories across a room connected via networking blocks.
How do I automate fluid transfers with RFTools Control?
The Processor cannot hold raw fluids in its standard item slots. You must place a multi-tank block or tank adjacent to the Processor to act as the internal fluid buffer, allocate those tank slots in the Processor GUI just like item slots, and use the 'Fetch Liquid' and 'Push Liquid' opcodes.
What is the difference between CPU Core B500, S1000, and EX2000?
Higher-tier CPU Cores execute more opcode instructions per tick and consume slightly more RF/FE per operation. For simple inventory routing, a B500 is plenty; for complex mathematical evaluations and vector comparisons, upgrade to the S1000 or EX2000.
By combining a powered Processor, properly allocated internal buffer slots, and a simple Event-Fetch-Push opcode chain in the Programmer, you can automate any item or fluid workflow with pinpoint precision.