Logic Processor

The Logic Processor is the programmable brain used for on-map scripting and automation in Mindustry. It serves as a versatile, general-purpose processor that balances progression, efficiency, speed and size, making it suitable for a wide range of tasks from early automation to complex late-game control. Logic Processors interact with the rest of the logic ecosystem — switches, displays, message blocks and memory banks — and run instruction scripts that control buildings, units and visual output.

Processors operate on a tick system where one second equals 60 ticks; instruction throughput is measured per second and per tick and varies between processor tiers. Different processor types trade off raw instruction throughput, instruction-per-tick density, link range and required inputs (for example, advanced processors may require coolant to operate). Logic Processors are commonly used as the central unit in setups that need moderate-range links, reliable instruction execution and compact footprint.

The Logic Processor is used in these practical roles: driving animated displays via draw instructions and draw-flush operations; implementing precise counters and event handling through arithmetic and conditional instructions; sending and receiving textual data using print/print-char and print-flush mechanics; reading and writing persistent or distributed data via memory banks with read/write instructions; and acting as boolean switches that can be toggled by user clicks or by script logic. It is also used to build advanced unit controllers that issue movement, attack and formation orders.

Practical usage and strategy notes:

• Place processors within link range of the blocks they must control; larger processors provide greater link ranges, so choose the processor tier to match network size.
• Remember the tick model: scripts execute a limited number of instructions each tick. Keep hot loops minimal and spread work across ticks if you need steady performance.
• Use Memory Banks to persist large datasets or to share state between distant processors; write with Write and retrieve with Read instructions.
• Use Displays together with Draw and Draw Flush to show in-game information. Canvas and modular displays offer differing sizes and palettes depending on the display type.
• Use message blocks (print/print-char and print-flush) when you need to transmit or combine string data between logic components.
• For boolean interactions or user input, use switch blocks which act as clickable toggles; some switches are map-editor-only and cannot be removed.
• When building advanced unit controllers, test orders incrementally and guard against blocking waits that consume instruction budget.
• If using end-game processors, be aware that some require coolant or additional inputs; plan infrastructure accordingly.

The Logic Processor is the hub of scripted automation; choosing the appropriate processor tier and structuring scripts to respect tick/instruction limits yields the most reliable and efficient systems.