Cheats & Console Commands: Hidden Items, Blocks, Units Guide

Cheats in Mindustry are hidden or developer-only features and assets you can enable via the in-game console or developer mode to unlock content, access hidden blocks/fluids/items, and alter map/planet visibility. Use them to test designs, explore content not normally available in standard play, or speed up creative experimentation.

Enabling the console and Developer Mode

• Open Developer Mode and enable the console. On PC press F8 to open the console once Developer Mode is installed/activated.
• The console accepts JavaScript-like commands that change game state and expose otherwise hidden content. Exercise caution: some commands can destabilize saves or maps.

Accessing hidden planets and making planets visible/unlocked

• Planets can be unlocked and made visible through console properties on the Planets object.
  • Example commands:
    • To unlock and allow access to the planet Tantros:
      • Planets.tantros.accessible = Planets.tantros.alwaysUnlocked = true
    • To make the planet model visible:
      • Planets.tantros.accessible = Planets.tantros.visible = true
• Apply the same pattern to other planet identifiers to reveal or unlock them.

Revealing hidden blocks, items, fluids, and units

• Many blocks, items, fluids, and units are present in game data but hidden from normal gameplay. They can be enabled or spawned via the console.
• Common hidden categories include:
  • Special blocks like Ice, Red Ice, Item Source, Item Void, Liquid Tank, Liquid Router, etc.
  • Hidden fluids and items marked as "Hidden".
  • Hidden units and effects (for example, Elude or unique flares).
• Typical approach:
  • Use console commands to spawn or toggle the hidden entity by its internal name (for example, block_ice, block_red_ice, block_item_source). The exact spawn or enable syntax depends on the command you use (spawn, give, or toggling visibility flags).
• Note: these hidden entities are intentionally nonstandard—some lack full gameplay integration or are intended for debugging.

Instant transfer and special block flags

• Some blocks have internal flags that change how they behave in simulation or calculations.
  • Example: blocks can expose Boolean properties like instantTransfer, which determine whether the block does instant transfer checking. This is used internally to prevent infinite transfer loops and to affect how fluids/items propagate in calculations.
• You can view or alter such properties through the console for debugging or to change simulation behavior, but altering them may create unintended consequences.

Using cheats safely

• Back up your saves before using console commands that modify game data.
• Avoid enabling or spawning hidden content in multiplayer games unless all players agree; changes can desync or be unsupported.
• Hidden blocks and units may be incomplete; use them for testing rather than long-term survival runs.
• When editing processor code or custom logic, remember there are multiple workflows (in-game editor vs. external editing). Choose the method you prefer — both are supported.

Quick checklist of common hidden names (internal identifiers)

• block_ice
• block_red_ice
• block_item_source
• block_item_void
• block_liquid_router
• block_liquid_tank
• flares
• unit_elude
• block_tendrils (has instantTransfer boolean flag)
• planet identifiers such as tantros (use Planets.)

Use these identifiers in the console when referencing or toggling visibility/unlock flags, or when spawning items/blocks/units for testing.

This page documents readily accessible developer cheats and hidden content; treat these tools as a testing and exploration resource rather than standard gameplay features.