Split

Split is a sector map in Mindustry used as a playable level target. The page collects practical notes about editing and constraints encountered when creating or modifying logic and power setups on this map. Split appears in contexts where players use the in-game logic editor and must respect global limits such as power node count and processor storage limits.

The in-game visual editor is the primary recommended workflow for beginners editing logic on Split. It provides a graphical interface with simple variable selection, a complete display of available variables, an intuitive Jump usage, and support for mobile controls. The visual editor supports importing and exporting logic via the clipboard, which lets you copy scripts between sessions or devices without manually editing text files.

There are two supported ways to author processor code when working on Split: using the in-game editor or writing code manually and pasting it into the processor. Each approach works; choose the one that best fits your workflow. The visual editor is simpler for newcomers, while manual editing can be faster for experienced users who prefer direct text manipulation.

When designing power and networked setups on Split, keep the engine limits in mind. The global power capacity is 10000, which constrains large-scale battery and capacitor designs. The maximum number of power nodes (grid nodes) allowed is 100; plan your wiring and relay placements accordingly to avoid hitting the node limit. These caps affect how you route power across the map and how many discrete powered segments you can create for logic-driven factories.

Practical points to remember:

• Use the in-game visual editor for clarity and ease when learning logic; it lists variables and simplifies control flow construction.
• Export and import logic via the clipboard to move programs between maps or devices.
• Manual text editing remains an option for complex scripts or bulk edits.
• Account for the 10000 power capacity and 100 max nodes when planning large power networks; consolidate relays or use direct connections where possible to stay under node limits.
• Test logic incrementally on Split: small, verifiable steps reduce debugging complexity when working within power/node constraints.