Mindcode uses Mindustry Logic processor variables for its own variables. These variables can contain a number
(integer or real), an object or a null value. An object can be a Mindustry object, such as a block or a unit, a
Mindustry constant such as @coal, or a string such as "Text".
Variables aren't declared in Mindcode, they're created with first use. count = 10 creates a variable named
count and assigns a value of 10 to it. Variables that weren't previously written to have a value of null in
Mindustry Logic. Once set, processor variables are preserved (even across game saves/loads) until the processor code
is modified or the processor is destroyed.
Note
Mindustry Logic stores numbers as double, a 64-bit floating point value. To perform bitwise operations, such as
& or <<, the value is converted to a 64-bit integer (a Java long), the operation is performed and the result
is assigned to a double again. As a consequence, for bitwise operations the variables are able to hold only
about 52 bits or so.
Main variables are variables used in the main body of the program. The name of the variable in Mindcode is used as-is in the compiled mlog code.
Mindcode is also aware of the actual values you assign to variables. In some cases, knowing the actual value allows Mindcode to perform specific code optimizations that are only valid for the value you've assigned to the variable in the source code (see Data Flow Optimization). It also means that if you change a value assigned to a main variable in the compiled code, the modified code might not behave correctly. Only changes to values assigned to global variables are supported in the compiled code.
Local variables are function parameters or variables used in a user-defined function. For example, in a function
def foo(x)
y = x ** 2
end
both x and y are local variables, not accessible outside the function foo.
In compiled code, names of these variables are appended to a unique function prefix. Recognizing names of local variables in compiled code might be a bit cumbersome.
Global variables are common to all user functions and the main program body. Use names that don't contain any
lowercase letters, such as MAIN or _9 (this is actually not a particularly good name for a variable), to create
global variables. Variables whose name contains at least one lowercase letter are not global.
The name of global variables in Mindcode are used as-is in Mindustry code. It might be therefore useful to put assignments to important variables at the beginning of the program, so that it can be easily modified in compiled code without the need of recompilation:
COUNT = 10
WARNING = false
ITEM = @coal
print(COUNT, WARNING, ITEM)
produces
set COUNT 10
set WARNING false
set ITEM @coal
print COUNT
print WARNING
print ITEM
Unlike main variables, global variables are never optimized away from the code. This also means that their use makes the code a bit less suitable for optimization, and you should limit their use to situations where they're really needed (i.e. for variables accessed from different functions, or for compile-in parameters).
For example, the following code
def foo(x)
MAIN = x + 10
local = 10
end
MAIN = 5
local = 5
x = 0
foo(10)
print(MAIN, ", ", local)
printflush(message1)
displays 20, 5 on the message1 block in Mindustry world (from now on, we'll omit the printflush(message1) in
examples), since both x and local in the foo function are local variables and therefore distinct from x and
local in the main program body.
Using global variables as function parameters (e.g. def foo(Z) ... end) is not allowed.
Mindcode supports storing variables in external memory - memory cells or memory banks linked to the processor. These variables are stored independently of the processor and can be used to share values between processors, or to keep values even when the processor is destroyed or its code altered.
On the other hand, only numeric values can be stored in external memory. It is therefore not possible to use it to store strings, units, buildings or item types there. This -- quite restrictive -- limitation is unfortunately imposed by Mindustry Logic itself.
You can use external variables using the array access syntax:
for i in 0 .. 63
cell2[i] = cell1[i]
end
This code copies the entire contents of memory cell cell1 to cell2.
It is also possible to reference external memory indirectly:
def copy(source, target, size)
for i in 0 ... size
target[i] = source[i]
end
end
copy(bank1, bank2, 512)
You can also have Mindcode assign identifiers to external variables. For that, you need to allocate a heap within a Memory Cell or a Memory Bank. This allocation tells the Mindcode compiler where to store the external variables. A heap is simply a region of external memory. The heap is allocated using the following Mindcode:
allocate heap in cell4[50 ... 64]
This statement allocates a heap, stored in cell4, and uses memory locations 50, 51, 52, ..., 62, and 63 (note the
exclusive range). If you declare more external variables than you have allocated space for, compilation will fail
with an OutOfHeapSpaceException. In that case, allocate more space for the heap in your cell, or switch to a
Memory Bank and allocate more space to your heap.
Once the heap is allocated, you can use external variables. External variables are identified by the $
(dollar-sign) prefix:
allocate heap in cell4[32 ... 64]
$dx = 1 // this is an external variable assignment
$dy = 1
$ne_x = 90
$ne_y = 90
$target_y = $sw_x = 50
$target_x = $sw_y = 50
The above will compile to:
cell4[32] = 1
cell4[33] = 1
cell4[34] = 90
cell4[35] = 90
cell4[36] = cell4[37] = 50
cell4[38] = cell4[39] = 50
Note
External variables are allocated on a first-come, first-served basis. If you had the following code:
allocate heap in cell2[61 .. 63]
$flag = rand(10000)
$targetx = 80
$targety = 80
and changed it to:
allocate heap in cell2[61 .. 63]
$targetx = 80
$targety = 80
$flag = rand(10000)
then all addresses in the heap would be reallocated. $targetx would be stored in memory cell 61, rather than $flag.
To fix this issue, you can either reset your heap to all zeroes on startup, or destroy and re-create your memory
cell/memory bank.
When using recursive functions, some of their local variables and parameters may have to be stored on a stack. As Mindustry Logic doesn't provide a built-in stack, external memory is used instead. This places the same limitations on local variables and parameters of recursive functions as on arrays and external variables (that is, only numeric values are supported).
Stack needs to be allocated similarly to heap:
allocate stack in bank1[256...512]
When a function is not recursive, it won't store anything on a stack, even when it is called from or it itself calls
a recursive function. If your code contains a recursive function, it won't compile unless the stack is allocated.
Therefore, if your code compiles without the allocate stack statement, you don't need to worry about your
functions not supporting non-numeric variables or parameters.
When you build your Mindcode scripts, the actual Memory Cell and Memory Bank that you use may be different from the ones you use when playing the game. To that end, you also have the option of referencing your heap and stack through the use of a variable, like this:
HEAPPTR = cell3
allocate heap in HEAPPTR
$dx = 0
This will translate to:
set HEAPPTR cell3
write 0 HEAPPTR 0
Since the very first instruction of the compiled code will be the global variable assignment, you can easily change the actual cell or bank your will use, without having to do a global search & replace within the compiled code. This introduces more avenues for code sharing.
It is possible to allocate stack and heap in the same memory block, and/or in one statement:
MEMORY = bank1
allocate stack in MEMORY[0 .. 480], heap in MEMORY[481 ... 512]
Mindustry Logic processors have several built-in variables.
Their names start with the @ sign. The most common ones are:
@counter: address of the next instruction to be executed@this,@thisx,@thisy: processor executing current code and its coordinates@mapw,@maph: dimensions of the map@time,@tick,@second,@minute: current game time expressed in various units@links: number of blocks linked to the processor@ipt: instructions per tick executed by this processor@unit: currently bound unit@unitCount,@itemCount,@liquidCount,@blockCount: counts of elements of given type, can be used withlookupfunction.
Mindcode allows you to read these variables, but it is not possible to assign a value to them.
Some of them are constant during the lifetime of the processor, but others do - or at least may - change (@time,
@counter or @links).
@unit is a very special variable - it always contains the unit currently controlled by the processor. The only way
to assign a new unit to this variable is to use the ubind() function. All unit control commands are sent to this
unit. See also Using units.
My experience shows that the value of time variables (@tick, @time and so on) can actually decrease when loading a
game from a save file. Take it into account especially when programming loops that should terminate at some
predetermined time.
When a block/building (e.g. a factory, a turret or a memory cell) is linked to a processor, an object representing
the linked blocks is created. This object is named using the short name of the linked block and an integer index,
e.g. cell1, switch3 or smelter16. These objects allow the code to directly control or query linked blocks.
Names of linked blocks are reserved and cannot be used by any variable. If a variable with the same name existed
earlier, it is removed from the processor. Assignments to a variable named after a linked block are silently ignored
by the processor.
The compiler doesn't know which blocks will be linked to the processor when compiling the code. To avoid generating code that might stop working when blocks are linked to the processor, all possible names of linked blocks are specially handled:
- it is not possible to assign values to variables with these names,
- these variables are implicitly global.
The second point means that in the following code
def foo()
print("In function foo")
printflush(message1)
end
the message1 variable represents a message block linked to the processor, even when used inside a function.
The list of possible block names is quite exhaustive.
Show full list of Mindustry block names.
arcbankbatterycellcentercentrifugecompressorconduitcontainerconveyorcruciblecultivatorcyclonediodedisassemblerdisplaydistributordomedoordrilldriverduoextractorfactoryforeshadowfoundationfusegategeneratorhailincineratorjunctionkilnlancermeltdownmeltermendermessageminemixernodenucleuspanelparallaxpointpressprocessorprojectorpulverizerreactorreconstructorrippleroutersalvoscatterscorchsegmentseparatorshardsmeltersorterspectreswarmerswitchtanktowertsunamiunloadervaultwallwaveweaver
Any variable name consisting of one of these prefixes and a positive integer is a reserved for linked blocks.
- These are block names:
point3,arc7,tank999999. - These aren't:
switch(no numeric index at all),cell05(leading zero),Router15(upper-case letter),wave_1orreactor-5(the index doesn't immediately follow the block name).
Mindcode supports declaring and using constants throughout your code. Constants are declared using the const keyword:
const DEBUG = true
const HIGH_SPEED = 50
const LOW_SPEED = HIGH_SPEED / 2
const RATIO = sqrt(2)
const message = DEBUG ? "Debug" : "Release"
Constants are global, even if their names contain lower-case characters. The value assigned to them must be either a
numeric, boolean or text literal, or an expression whose value can be computed at compile time. Compile-time
evaluation uses the same rules as Mindustry Logic, i.e. const ERROR = 1 / 0 is a valid constant declaration which
creates a constant ERROR with a value of null.
If a numeric value is assigned to a constant, and it isn't possible to encode the value into an mlog literal, a compilation error occurs.
A name used for a constant cannot be used for a main, global or local variable.
Unlike variables, constants aren't kept in processor variables, and their values therefore cannot be changed in compiled code. It also means that in the following code
const DEBUG = false
...
if DEBUG
println("State: ", state)
println("Item count: ", @unit.totalItems)
end
the entire if DEBUG ... end statement will be skipped and not included in the compiled code.
Mindustry has a set of built-in icons that are represented by specific Unicode characters and are properly rendered in all the user interface elements. While it would be possible to enter a corresponding Unicode character into a String literal directly, it would be probably a bit cumbersome. To provide access to these icons, Mindcode comes with a predefined set of constants that correspond to individual icons. The constants map the symbolic icon names onto a String literal containing their corresponding Unicode character.
Printing an icon is as easy as this:
print(ITEM-LEAD, " ", vault1.lead, "\n")
print(ITEM-COAL, " ", vault1.coal, "\n")
print(ITEM-BLAST-COMPOUND, " ", vault1.blast-compound)
printflush(message1)
As has already been mentioned, names of the icons are constants and cannot therefore be used for user-defined constants or variables.
The list of all existing icons is quite huge:
Show full list of Mindustry block icons.
BLOCK-ADDITIVE-RECONSTRUCTORBLOCK-AFFLICTBLOCK-AIR-FACTORYBLOCK-ALPHA-MECH-PADBLOCK-ARCBLOCK-ARKYCITE-FLOORBLOCK-ARKYIC-BOULDERBLOCK-ARKYIC-STONEBLOCK-ARKYIC-VENTBLOCK-ARKYIC-WALLBLOCK-ARMORED-CONVEYORBLOCK-ARMORED-DUCTBLOCK-ATMOSPHERIC-CONCENTRATORBLOCK-BALLISTIC-SILOBLOCK-BARRIER-PROJECTORBLOCK-BASALTBLOCK-BASALT-BOULDERBLOCK-BASIC-ASSEMBLER-MODULEBLOCK-BASIC-RECONSTRUCTORBLOCK-BATTERYBLOCK-BATTERY-LARGEBLOCK-BEAM-DRILLBLOCK-BEAM-LINKBLOCK-BEAM-NODEBLOCK-BEAM-TOWERBLOCK-BERYLLIC-BOULDERBLOCK-BERYLLIC-STONEBLOCK-BERYLLIC-STONE-WALLBLOCK-BERYLLIUM-WALLBLOCK-BERYLLIUM-WALL-LARGEBLOCK-BLAST-DOORBLOCK-BLAST-DRILLBLOCK-BLAST-MIXERBLOCK-BLOCK-FORGEBLOCK-BLOCK-LAUNCHERBLOCK-BLOCK-LOADERBLOCK-BLOCK-UNLOADERBLOCK-BLUEMATBLOCK-BOULDERBLOCK-BREACHBLOCK-BRIDGE-CONDUITBLOCK-BRIDGE-CONVEYORBLOCK-BUILD-TOWERBLOCK-CANVASBLOCK-CARBIDE-CRUCIBLEBLOCK-CARBIDE-WALLBLOCK-CARBIDE-WALL-LARGEBLOCK-CARBON-BOULDERBLOCK-CARBON-STONEBLOCK-CARBON-VENTBLOCK-CARBON-WALLBLOCK-CELL-SYNTHESIS-CHAMBERBLOCK-CHARBLOCK-CHEMICAL-COMBUSTION-CHAMBERBLOCK-CLIFFBLOCK-CLIFF-CRUSHERBLOCK-CLIFFSBLOCK-COAL-CENTRIFUGEBLOCK-COMBUSTION-GENERATORBLOCK-COMMAND-CENTERBLOCK-CONDUITBLOCK-CONSTRUCTORBLOCK-CONTAINERBLOCK-CONVEYORBLOCK-COPPER-WALLBLOCK-COPPER-WALL-LARGEBLOCK-CORE-ACROPOLISBLOCK-CORE-BASTIONBLOCK-CORE-CITADELBLOCK-CORE-FOUNDATIONBLOCK-CORE-NUCLEUSBLOCK-CORE-SHARDBLOCK-CORE-SILOBLOCK-CORE-ZONEBLOCK-CRATER-STONEBLOCK-CRATERSBLOCK-CRAWLER-FACTORYBLOCK-CRYOFLUID-MIXERBLOCK-CRYSTAL-BLOCKSBLOCK-CRYSTAL-CLUSTERBLOCK-CRYSTAL-FLOORBLOCK-CRYSTAL-ORBSBLOCK-CRYSTALLINE-BOULDERBLOCK-CRYSTALLINE-STONEBLOCK-CRYSTALLINE-STONE-WALLBLOCK-CRYSTALLINE-VENTBLOCK-CULTIVATORBLOCK-CYANOGEN-SYNTHESIZERBLOCK-CYCLONEBLOCK-DACITEBLOCK-DACITE-BOULDERBLOCK-DACITE-WALLBLOCK-DAGGER-FACTORYBLOCK-DARK-METALBLOCK-DARK-PANEL-1BLOCK-DARK-PANEL-2BLOCK-DARK-PANEL-3BLOCK-DARK-PANEL-4BLOCK-DARK-PANEL-5BLOCK-DARK-PANEL-6BLOCK-DARKSANDBLOCK-DARKSAND-TAINTED-WATERBLOCK-DARKSAND-WATERBLOCK-DART-MECH-PADBLOCK-DART-SHIP-PADBLOCK-DATA-PROCESSORBLOCK-DECONSTRUCTORBLOCK-DEEP-TAINTED-WATERBLOCK-DEEP-WATERBLOCK-DEEPWATERBLOCK-DELTA-MECH-PADBLOCK-DENSE-RED-STONEBLOCK-DIFFERENTIAL-GENERATORBLOCK-DIFFUSEBLOCK-DIODEBLOCK-DIRTBLOCK-DIRT-WALLBLOCK-DISASSEMBLERBLOCK-DISPERSEBLOCK-DISTRIBUTORBLOCK-DOORBLOCK-DOOR-LARGEBLOCK-DRAUG-FACTORYBLOCK-DUCTBLOCK-DUCT-BRIDGEBLOCK-DUCT-ROUTERBLOCK-DUCT-UNLOADERBLOCK-DUNE-WALLBLOCK-DUOBLOCK-ELECTRIC-HEATERBLOCK-ELECTROLYZERBLOCK-EMPTYBLOCK-ERUPTION-DRILLBLOCK-EXPONENTIAL-RECONSTRUCTORBLOCK-FABRICATORBLOCK-FERRIC-BOULDERBLOCK-FERRIC-CRATERSBLOCK-FERRIC-STONEBLOCK-FERRIC-STONE-WALLBLOCK-FLUX-REACTORBLOCK-FORCE-PROJECTORBLOCK-FORESHADOWBLOCK-FORTRESS-FACTORYBLOCK-FRACTUREBLOCK-FUSEBLOCK-GHOUL-FACTORYBLOCK-GLAIVE-SHIP-PADBLOCK-GRAPHITE-PRESSBLOCK-GRAPHITIC-WALLBLOCK-GRASSBLOCK-GROUND-FACTORYBLOCK-HAILBLOCK-HEAT-REACTORBLOCK-HEAT-REDIRECTORBLOCK-HEAT-ROUTERBLOCK-HEAT-SOURCEBLOCK-HOTROCKBLOCK-HYPER-PROCESSORBLOCK-ICEBLOCK-ICE-SNOWBLOCK-ICE-WALLBLOCK-IGNAROCKBLOCK-ILLUMINATORBLOCK-IMPACT-DRILLBLOCK-IMPACT-REACTORBLOCK-IMPULSE-PUMPBLOCK-INCINERATORBLOCK-INTERPLANETARY-ACCELERATORBLOCK-INVERTED-SORTERBLOCK-ITEM-SOURCEBLOCK-ITEM-VOIDBLOCK-JAVELIN-SHIP-PADBLOCK-JUNCTIONBLOCK-KILNBLOCK-LANCERBLOCK-LARGE-CONSTRUCTORBLOCK-LARGE-LOGIC-DISPLAYBLOCK-LARGE-OVERDRIVE-PROJECTORBLOCK-LARGE-PAYLOAD-MASS-DRIVERBLOCK-LARGE-PLASMA-BOREBLOCK-LARGE-SHIELD-PROJECTORBLOCK-LASER-DRILLBLOCK-LAUNCH-PADBLOCK-LAUNCH-PAD-LARGEBLOCK-LEGACY-COMMAND-CENTERBLOCK-LEGACY-MECH-PADBLOCK-LEGACY-UNIT-FACTORYBLOCK-LEGACY-UNIT-FACTORY-AIRBLOCK-LEGACY-UNIT-FACTORY-GROUNDBLOCK-LIQUID-CONTAINERBLOCK-LIQUID-JUNCTIONBLOCK-LIQUID-ROUTERBLOCK-LIQUID-SOURCEBLOCK-LIQUID-TANKBLOCK-LIQUID-VOIDBLOCK-LOGIC-DISPLAYBLOCK-LOGIC-PROCESSORBLOCK-LUSTREBLOCK-MAGMAROCKBLOCK-MALIGNBLOCK-MASS-CONVEYORBLOCK-MASS-DRIVERBLOCK-MECH-ASSEMBLERBLOCK-MECH-FABRICATORBLOCK-MECH-RECONSTRUCTORBLOCK-MECH-REFABRICATORBLOCK-MECHANICAL-DRILLBLOCK-MECHANICAL-PUMPBLOCK-MELTDOWNBLOCK-MELTERBLOCK-MEMORY-BANKBLOCK-MEMORY-CELLBLOCK-MEND-PROJECTORBLOCK-MENDERBLOCK-MESSAGEBLOCK-METAL-FLOORBLOCK-METAL-FLOOR-2BLOCK-METAL-FLOOR-3BLOCK-METAL-FLOOR-4BLOCK-METAL-FLOOR-5BLOCK-METAL-FLOOR-DAMAGEDBLOCK-MICRO-PROCESSORBLOCK-MOLTEN-SLAGBLOCK-MOSSBLOCK-MUDBLOCK-MULTI-PRESSBLOCK-MULTIPLICATIVE-RECONSTRUCTORBLOCK-NAVAL-FACTORYBLOCK-NEOPLASIA-REACTORBLOCK-NUCLEAR-WARHEADBLOCK-OIL-EXTRACTORBLOCK-OMEGA-MECH-PADBLOCK-ORE-BERYLLIUMBLOCK-ORE-COALBLOCK-ORE-COPPERBLOCK-ORE-CRYSTAL-THORIUMBLOCK-ORE-LEADBLOCK-ORE-SCRAPBLOCK-ORE-THORIUMBLOCK-ORE-TITANIUMBLOCK-ORE-TUNGSTENBLOCK-ORE-WALL-BERYLLIUMBLOCK-ORE-WALL-THORIUMBLOCK-ORE-WALL-TUNGSTENBLOCK-OVERDRIVE-DOMEBLOCK-OVERDRIVE-PROJECTORBLOCK-OVERFLOW-DUCTBLOCK-OVERFLOW-GATEBLOCK-OXIDATION-CHAMBERBLOCK-OXIDIZERBLOCK-PARALLAXBLOCK-PAYLOAD-CONVEYORBLOCK-PAYLOAD-INCINERATORBLOCK-PAYLOAD-LOADERBLOCK-PAYLOAD-MASS-DRIVERBLOCK-PAYLOAD-ROUTERBLOCK-PAYLOAD-SOURCEBLOCK-PAYLOAD-UNLOADERBLOCK-PAYLOAD-VOIDBLOCK-PEBBLESBLOCK-PHANTOM-FACTORYBLOCK-PHASE-CONDUITBLOCK-PHASE-CONVEYORBLOCK-PHASE-HEATERBLOCK-PHASE-SYNTHESIZERBLOCK-PHASE-WALLBLOCK-PHASE-WALL-LARGEBLOCK-PHASE-WEAVERBLOCK-PINEBLOCK-PLASMA-BOREBLOCK-PLASTANIUM-COMPRESSORBLOCK-PLASTANIUM-CONVEYORBLOCK-PLASTANIUM-WALLBLOCK-PLASTANIUM-WALL-LARGEBLOCK-PLATED-CONDUITBLOCK-PNEUMATIC-DRILLBLOCK-POOLED-CRYOFLUIDBLOCK-POWER-NODEBLOCK-POWER-NODE-LARGEBLOCK-POWER-SOURCEBLOCK-POWER-VOIDBLOCK-PRESSURE-TURBINEBLOCK-PRIME-REFABRICATORBLOCK-PULSE-CONDUITBLOCK-PULVERIZERBLOCK-PUR-BUSHBLOCK-PYRATITE-MIXERBLOCK-PYROLYSIS-GENERATORBLOCK-RADARBLOCK-RAVAGEBLOCK-RED-DIAMOND-WALLBLOCK-RED-ICEBLOCK-RED-ICE-BOULDERBLOCK-RED-ICE-WALLBLOCK-RED-STONEBLOCK-RED-STONE-BOULDERBLOCK-RED-STONE-VENTBLOCK-RED-STONE-WALLBLOCK-REDMATBLOCK-REDWEEDBLOCK-REFABRICATORBLOCK-REGEN-PROJECTORBLOCK-REGOLITHBLOCK-REGOLITH-WALLBLOCK-REINFORCED-BRIDGE-CONDUITBLOCK-REINFORCED-CONDUITBLOCK-REINFORCED-CONTAINERBLOCK-REINFORCED-LIQUID-CONTAINERBLOCK-REINFORCED-LIQUID-JUNCTIONBLOCK-REINFORCED-LIQUID-ROUTERBLOCK-REINFORCED-LIQUID-TANKBLOCK-REINFORCED-MESSAGEBLOCK-REINFORCED-PAYLOAD-CONVEYORBLOCK-REINFORCED-PAYLOAD-ROUTERBLOCK-REINFORCED-PUMPBLOCK-REINFORCED-SURGE-WALLBLOCK-REINFORCED-SURGE-WALL-LARGEBLOCK-REINFORCED-VAULTBLOCK-REPAIR-POINTBLOCK-REPAIR-TURRETBLOCK-RESUPPLY-POINTBLOCK-REVENANT-FACTORYBLOCK-RHYOLITEBLOCK-RHYOLITE-BOULDERBLOCK-RHYOLITE-CRATERBLOCK-RHYOLITE-VENTBLOCK-RHYOLITE-WALLBLOCK-RIPPLEBLOCK-ROCKBLOCK-ROTARY-PUMPBLOCK-ROUGH-RHYOLITEBLOCK-ROUTERBLOCK-RTG-GENERATORBLOCK-SALTBLOCK-SALT-WALLBLOCK-SALVOBLOCK-SANDBLOCK-SAND-BOULDERBLOCK-SAND-FLOORBLOCK-SAND-WALLBLOCK-SAND-WATERBLOCK-SCATHEBLOCK-SCATTERBLOCK-SCORCHBLOCK-SCRAP-WALLBLOCK-SCRAP-WALL-GIGANTICBLOCK-SCRAP-WALL-HUGEBLOCK-SCRAP-WALL-LARGEBLOCK-SEGMENTBLOCK-SEPARATORBLOCK-SHALEBLOCK-SHALE-BOULDERBLOCK-SHALE-WALLBLOCK-SHALLOW-WATERBLOCK-SHIELD-PROJECTORBLOCK-SHIELDED-WALLBLOCK-SHIP-ASSEMBLERBLOCK-SHIP-FABRICATORBLOCK-SHIP-RECONSTRUCTORBLOCK-SHIP-REFABRICATORBLOCK-SHOCK-MINEBLOCK-SHOCKWAVE-TOWERBLOCK-SHRUBSBLOCK-SILICON-ARC-FURNACEBLOCK-SILICON-CRUCIBLEBLOCK-SILICON-SMELTERBLOCK-SLAG-CENTRIFUGEBLOCK-SLAG-HEATERBLOCK-SLAG-INCINERATORBLOCK-SMALL-DECONSTRUCTORBLOCK-SMITEBLOCK-SNOWBLOCK-SNOW-BOULDERBLOCK-SNOW-PINEBLOCK-SNOW-WALLBLOCK-SNOWROCKBLOCK-SOLAR-PANELBLOCK-SOLAR-PANEL-LARGEBLOCK-SORTERBLOCK-SPACEBLOCK-SPAWNBLOCK-SPECTREBLOCK-SPIRIT-FACTORYBLOCK-SPORE-CLUSTERBLOCK-SPORE-MOSSBLOCK-SPORE-PINEBLOCK-SPORE-PRESSBLOCK-SPORE-WALLBLOCK-STEAM-GENERATORBLOCK-STEAM-VENTBLOCK-STONEBLOCK-STONE-WALLBLOCK-SUBLIMATEBLOCK-SURGE-CONVEYORBLOCK-SURGE-CRUCIBLEBLOCK-SURGE-DUCTBLOCK-SURGE-ROUTERBLOCK-SURGE-SMELTERBLOCK-SURGE-TOWERBLOCK-SURGE-WALLBLOCK-SURGE-WALL-LARGEBLOCK-SWARMERBLOCK-SWITCHBLOCK-TAINTED-WATERBLOCK-TANK-ASSEMBLERBLOCK-TANK-FABRICATORBLOCK-TANK-RECONSTRUCTORBLOCK-TANK-REFABRICATORBLOCK-TARBLOCK-TAU-MECH-PADBLOCK-TENDRILSBLOCK-TETRATIVE-RECONSTRUCTORBLOCK-THERMAL-GENERATORBLOCK-THORIUM-REACTORBLOCK-THORIUM-WALLBLOCK-THORIUM-WALL-LARGEBLOCK-THRUSTERBLOCK-TITANBLOCK-TITAN-FACTORYBLOCK-TITANIUM-CONVEYORBLOCK-TITANIUM-WALLBLOCK-TITANIUM-WALL-LARGEBLOCK-TRIDENT-SHIP-PADBLOCK-TSUNAMIBLOCK-TUNGSTEN-WALLBLOCK-TUNGSTEN-WALL-LARGEBLOCK-TURBINE-CONDENSERBLOCK-UNDERFLOW-DUCTBLOCK-UNDERFLOW-GATEBLOCK-UNIT-CARGO-LOADERBLOCK-UNIT-CARGO-UNLOAD-POINTBLOCK-UNIT-REPAIR-TOWERBLOCK-UNLOADERBLOCK-VAULTBLOCK-VENT-CONDENSERBLOCK-VIBRANT-CRYSTAL-CLUSTERBLOCK-WALL-ORE-BERYLLIUMBLOCK-WALL-ORE-TUNGSTENBLOCK-WARHEAD-ASSEMBLERBLOCK-WATER-EXTRACTORBLOCK-WAVEBLOCK-WHITE-TREEBLOCK-WHITE-TREE-DEADBLOCK-WORLD-CELLBLOCK-WORLD-MESSAGEBLOCK-WORLD-PROCESSORBLOCK-WRAITH-FACTORYBLOCK-YELLOW-STONEBLOCK-YELLOW-STONE-BOULDERBLOCK-YELLOW-STONE-PLATESBLOCK-YELLOW-STONE-VENTBLOCK-YELLOW-STONE-WALLBLOCK-YELLOWCORAL
Show full list of Mindustry item/liquid icons.
ITEM-BERYLLIUMITEM-BLAST-COMPOUNDITEM-CARBIDEITEM-COALITEM-COPPERITEM-DORMANT-CYSTITEM-FISSILE-MATTERITEM-GRAPHITEITEM-LEADITEM-METAGLASSITEM-OXIDEITEM-PHASE-FABRICITEM-PLASTANIUMITEM-PYRATITEITEM-SANDITEM-SCRAPITEM-SILICONITEM-SPORE-PODITEM-SURGE-ALLOYITEM-THORIUMITEM-TITANIUMITEM-TUNGSTENLIQUID-ARKYCITELIQUID-CRYOFLUIDLIQUID-CYANOGENLIQUID-GALLIUMLIQUID-HYDROGENLIQUID-NEOPLASMLIQUID-NITROGENLIQUID-OILLIQUID-OXYGENLIQUID-OZONELIQUID-SLAGLIQUID-WATER
Show full list of Mindustry status and team icons.
STATUS-BLASTEDSTATUS-BOSSSTATUS-BURNINGSTATUS-CORRODEDSTATUS-DISARMEDSTATUS-ELECTRIFIEDSTATUS-FREEZINGSTATUS-INVINCIBLESTATUS-MELTINGSTATUS-MUDDYSTATUS-NONESTATUS-OVERCLOCKSTATUS-OVERDRIVESTATUS-SAPPEDSTATUS-SHIELDEDSTATUS-SHOCKEDSTATUS-SLOWSTATUS-SPORE-SLOWEDSTATUS-TARREDSTATUS-UNMOVINGSTATUS-WETTEAM-CRUXTEAM-DERELICTTEAM-MALISTEAM-SHARDED
Show full list of Mindustry unit icons.
UNIT-AEGIRESUNIT-ALPHAUNIT-ANTHICUSUNIT-ANTHICUS-MISSILEUNIT-ANTUMBRAUNIT-ARKYIDUNIT-ASSEMBLY-DRONEUNIT-ATRAXUNIT-AVERTUNIT-BETAUNIT-BLOCKUNIT-BRYDEUNIT-CATACLYSTUNIT-CLEROIUNIT-COLLARISUNIT-CONQUERUNIT-CORVUSUNIT-CRAWLERUNIT-CYERCEUNIT-DAGGERUNIT-DISRUPTUNIT-DISRUPT-MISSILEUNIT-ECLIPSEUNIT-EFFECT-DRONEUNIT-ELUDEUNIT-EMANATEUNIT-EVOKEUNIT-FLAREUNIT-FORTRESSUNIT-GAMMAUNIT-HORIZONUNIT-INCITEUNIT-LATUMUNIT-LOCUSUNIT-MACEUNIT-MANIFOLDUNIT-MEGAUNIT-MERUIUNIT-MINKEUNIT-MONOUNIT-NAVANAXUNIT-NOVAUNIT-OBVIATEUNIT-OCTUNIT-OMURAUNIT-OSCUNIT-OXYNOEUNIT-POLYUNIT-PRECEPTUNIT-PULSARUNIT-QUADUNIT-QUASARUNIT-QUELLUNIT-QUELL-MISSILEUNIT-REIGNUNIT-RENALEUNIT-RETUSAUNIT-RISSEUNIT-RISSOUNIT-SCATHE-MISSILEUNIT-SCEPTERUNIT-SEIUNIT-SPIROCTUNIT-STELLUNIT-TECTAUNIT-TOXOPIDUNIT-TURRET-UNIT-BUILD-TOWERUNIT-VANQUISHUNIT-VELAUNIT-VESTIGEUNIT-ZENITH
Show full list of Mindustry unclassified icons.
ALPHAAAACRATER