Mindustry V8 Wrap-Up: What Changed from Build 160 Onward?

If you haven’t played Mindustry in a while, you may have noticed that the game has already moved into the Build 160 series.

Build 160 is a bit more important than the version number makes it look. Ankue has confirmed that Build 160 is the final V8 update focused mainly on new features. After this, V8 will mostly receive bug fixes, stability improvements, and compatibility updates, while active development gradually shifts toward V9.

So Build 160 feels less like a huge content drop and more like a final cleanup pass for V8. There is no new planet, no massive new tech tree, but quite a lot has changed across target testing, servers, logic, Mods, units, and balance.

We Finally Have a Proper Target Dummy

One of the most immediately useful additions in Build 160 is the new Target Dummy.

In simple terms, it is a dedicated target for testing DPS, or damage per second. Before this, if you wanted to test how much damage a turret, unit, or Mod weapon could really deal, you usually had to spawn enemies in sandbox mode, use units as punching bags, or build your own testing setup.

Now you can simply place a Target Dummy and start shooting.

For players who enjoy testing turret damage, comparing defenses, or building optimized schematics, this is a genuinely useful addition. The next time someone argues about whether a turret is weak or overpowered, at least there is now something better than “it feels strong.”

The funny part is that the thing designed to help players test bugs ended up becoming one of the buggiest additions in the entire 160 series.

After release, Target Dummies had issues where they could be spawned like normal units, loaded into payloads, cause multiplayer disconnects when configured, receive overdrive effects, and more. Ankue spent several follow-up releases chasing these issues down.

So the Target Dummy went from being a testing tool to becoming the thing that needed the most testing.

Multiplayer Servers Can Do a Lot More Now

If you mostly play single-player, this section may not feel especially dramatic. But for players who spend time on community servers, Build 160 gives server owners a lot more room to experiment.

Previously, most server plugin interfaces were fairly simple. You would open a menu and get a few buttons for voting, teleporting, shops, game modes, and so on.

Build 160 expands this significantly. Servers can now show much more complete custom interfaces, including text, images, buttons, and custom layouts.

In practical terms, things like shops, quest screens, rankings, event pages, mode selectors, and player panels can now look far more like proper game interfaces instead of basic plugin menus.

Servers can also send dynamic visual content and make larger map changes more efficiently.

You do not really need to care about the technical details. The important part is simple:

Large community servers can now build much more complex experiences than before.

In the past, plugins mostly added extra functions on top of Mindustry. Now, some servers can start using Mindustry as the foundation for entirely custom game modes.

Logic Players Got Another Box of Toys

Build 160 also includes quite a few changes to logic.

First, the logic editor now supports localization, making it friendlier for players using different languages.

There are also several smaller improvements. Logic markers can now work as light sources, string handling has been expanded, memory cells can store more kinds of data, and tools for status effects, sound control, and scripted map events have all been improved.

Most regular campaign players will probably never notice any of this.

But for the kind of players who use processors to build automation systems, unit control setups, displays, calculators, or even small games, this is basically another toolbox full of new parts.

At this point, Mindustry logic has long since moved beyond simple things like checking whether a conveyor is carrying items.

If you are willing to spend enough time on it, you can build calculators, games, automated factories, map systems, and all kinds of strange creations.

Every time logic gets updated, there is always a group of players who somehow make you wonder whether you are even playing the same game.

Mod Players Should Run Into Fewer Version Problems

Build 160 also improves the experience for Mod users.

If the game disables Mods after a failed launch or compatibility problem, there is now an easier way to restore them instead of turning everything back on manually.

Reinstalling Mods also gives players more control over which version they install.

The more important change arrived later in Build 160.5: Mod releases can now be selected according to the player’s Mindustry version.

For example, a Mod author can publish a release specifically marked for V8 Build 160, such as [v160]. Players using 160.x can then be directed toward the correct compatible release instead of automatically grabbing the newest one.

This may not sound exciting right now, but it will matter a lot once V9 becomes widely used.

V8 and V9 versions of the same Mod will probably exist side by side for quite a while. Without proper version handling, the most common conversation would probably be:

“Why does the game crash when I install this Mod?”
“You downloaded the V9 version.”
“Where is the V8 one?”
“Scroll down to the third release…”

Now the game can do a little more of that work for you.

Small Changes That Actually Feel Good to Use

Build 160 also includes a bunch of changes that are not exciting enough to headline an update, but they make the game noticeably nicer to use.

The server browser can now sort servers by player count, making it easier to find active servers. Maps can be sorted by their last modified date, which is surprisingly useful if you edit a lot of maps.

Keybinds can now be properly cleared instead of forcing you to assign another key just to free one up.

Items inside bridge conveyors are easier to inspect, mirror lines in the map editor can be dragged directly, and automatic bridge placement has also been improved.

There are multiplayer synchronization improvements as well, mainly aimed at reducing units suddenly stuttering, snapping, or moving strangely.

These are the kinds of changes that only get one line in a changelog, but once you get used to them, going back to an older version immediately feels wrong.

Nova Got a Proper Buff

On the combat side, Nova is one of the clearest winners in Build 160.

Its health increased from 120 to 200, and its boost movement speed was improved as well. Its firing rate was slightly reduced, but its attacks now have penetration, and its healing behavior has also been improved.

Before this, Nova often felt like a unit that looked useful and then disappeared the moment something serious started shooting back.

Now it can actually stay in the fight for a while.

But Nova is not the biggest balance change in this update.

High-Tier Units Put On Body Armor

Build 160 increased the armor of a large number of advanced units, and some of these buffs are pretty substantial.

Scepter: 10 → 20
Vela: 9 → 16
Arkyid: 6 → 14
Antumbra: 9 → 17
Quad: 8 → 10
Reign: 18 → 30
Corvus: 9 → 14
Toxopid: 13 → 22
Eclipse: 13 → 22
Oct: 18 → 20
Navanax: 18 → 20

The standout here is clearly Reign, which jumps all the way from 18 armor to 30.

This actually matters for defense design. Higher armor makes low-damage, high-fire-rate weapons much less effective.

So if you still use some old defense setups built around lots of low-damage turrets, it may be worth testing them again in Build 160.

Before, the idea may have been:

“Enough bullets will eventually kill it.”

Now it may turn into:

“There are definitely a lot of bullets, so why is the health bar barely moving?”

Copper Conveyors Took Off, Then Got Pulled Back Down

Copper conveyors have had a funny couple of versions.

In Build 159, their speed jumped from 4.2 to 6.5, which made early-game logistics feel much faster.

Then Build 160 arrived, and Ankue apparently decided that the buff had gone a little too far, so the speed was reduced from 6.5 to 5.

It is still faster than the old 4.2 value, so this is not a full revert.

The simplest way to put it is:

The buff stayed, but the turbo button got removed.

For campaign play and early factories, copper conveyors still feel better than they used to.

Erekir Payload Logistics Got Better Too

Payload logistics on Erekir also received improvements.

Several payload-related structures are now cheaper to build, and some parts of payload transport and launching have been sped up.

Anyone who has spent enough time building large Erekir factories knows how quickly payload logistics can turn into a traffic jam.

These buffs should make larger production lines and unit factories a little less frustrating to manage.

It is not the kind of change that looks exciting in a screenshot, but during an actual campaign run, it can matter a lot more than another flashy turret.

Ripple and Titan Now Prefer Shooting Into Crowds

Ripple and Titan also received targeting behavior changes.

They are now more likely to target groups of enemies rather than wasting area damage on isolated targets.

That makes a lot of sense.

If several enemies are packed together and your splash-damage turret decides to shoot the one lonely unit standing off to the side, it is hard not to question its life choices.

With this change, these turrets should make better use of their area damage against clustered enemies.

It does not directly increase their damage numbers, but in real battles, smarter target selection can matter just as much.

Spectre, Meltdown, and a Few Others Turn a Little Slower

A few late-game Serpulo turrets had their rotation speed slightly reduced, including:

Spectre, Meltdown, Foreshadow, Swarmer, and Cyclone.

This does not mean their damage was heavily nerfed. They simply take a little longer to rotate and track targets.

Against slow, heavy units, the difference will probably be minor.

Against fast air units or enemies that constantly force the turret to switch targets, it may be more noticeable.

Some of these turrets used to whip around so fast that you almost expected the base to unscrew itself.

Now they are slightly more relaxed about it.

Build 160.1 to 160.4: Why Is the Target Dummy Still Bugged?

After Build 160 released, Ankue quickly followed up with several smaller patches.

Build 160.1 dealt with Target Dummies being spawned incorrectly, being carried as payloads, and several Mod, particle, API, and audio-related crashes.

Build 160.2 fixed issues such as keybind clearing not saving properly, duplicate weather entries in rules, and some logic interface problems on vertical displays.

Then Build 160.3 arrived, and the Target Dummy was back again.

Changing its settings in multiplayer could disconnect or crash clients, and it could even receive overdrive effects.

Ankue opened that update with:

The target dummy bugs continue.

Build 160.4 fixed more of them.

At that point, it started to feel less like players were testing the Target Dummy and more like the Target Dummy was testing Ankue.

Build 160.5: Mod Compatibility and a Lot of Cleanup

Build 160.5 was one of the larger follow-up patches.

It fixed issues involving chain lightning, logic number parsing, logic markers, processor drawing caches, high-speed production blocks failing to output items in time, and map description text wrapping.

The desktop player list was widened, and high refresh rate behavior on iPhones was also addressed.

The previously mentioned version-aware Mod release selection was added in this update as well.

And yes, the Target Dummy showed up again.

This patch fixed problems involving large Target Dummies being placed too close together and huge collision areas causing pathfinding problems.

At this point, the Target Dummy had successfully become a recurring character in the Build 160 patch notes.

Build 160.6: Mostly Fixing Multiplayer and Unit Weirdness

Build 160.6 focused heavily on stability and multiplayer issues.

Units could stutter while chasing moving targets, commanding too many units at once could disconnect clients, naval units could get stuck on water-based doors, and rare physics crashes could occur on servers.

It also fixed logic parameter issues, Mod class-loading deadlocks, sandbox softlocks caused by switching team cores, and healing projectiles choosing the wrong targets.

The “command too many units and disconnect” bug was especially painful for anyone who enjoys selecting an entire army and sending it forward at once.

You prepare the final assault.

The enemy core survives.

Your client does not.

Not exactly the outcome you had in mind.

Build 160.6 also added more support for Mod data patches, clearly preparing for future compatibility needs as V9 development continues.

V8 Is Basically Wrapped Up Now

Overall, Build 160 is not the kind of update where you open the game and immediately say, “What happened? Why is everything new?”

It feels more like the final polish pass for V8.

Sandbox players finally have a proper Target Dummy for testing damage. Servers can build much richer custom interfaces. Logic keeps getting more powerful. Mod compatibility is already being prepared for the future V8 and V9 split. High-tier units are tougher, meaning some older defense setups may need another look.

Then, starting from Build 160.1, the focus clearly shifts toward bug fixing, stability, and compatibility.

So if you just want to play campaign, build factories, make maps, or join servers, V8 is now in a very mature state.

As for the next genuinely big step, the direction is already obvious:

Next stop, V9.

Coverage: Build 160 and later 160.x updates.
If V8 continues receiving maintenance releases, we will keep tracking the changes that actually matter to players.