1.1.0
Compatibility
Required content
Changes
1.1.0
A big feature update focused on logistics, base-building and customisation, plus a fifth combat robot, a rideable tank, a fully illustrated manual, complete Simplified Chinese localization, and a large round of bug fixes.
New robots & units
- Crusher — a heavy melee robot that leaps at foes and slams the ground on landing for area damage and knockback.
- Build Drone & Builder Bay — deploy a bay and let the drone build for you from a supply chest.
Machines, deployables & décor
- Shield Pylon — a placeable that raises a protective dome; enemies are pushed out while you and your allies pass through.
- Painting system — Oil Refinery, Paint Station, spray cans in every dye + rare colours, and a Solvent can. Recolour robots and paintable blocks.
- Décor & furniture — paintable blocks, light panel, metal grating, lamp post, work desk, chair, and industrial lanterns.
Items, tools & weapons
- Capture Pod — catch an animal with a right-click, release it with another.
- Player Tank — a rideable, coal-fuelled combat vehicle with a main gun.
- Additional field gear, weapons and watering cans.
Guide & localization
- The Engineer's Manual is now a fully illustrated guide with icons, crafting grids and 3D previews.
- Complete Simplified Chinese (zh_cn) — now fully trilingual (English / 日本語 / 简体中文).
Fixes & polish
- Reorganised the creative tab into clear groups.
- Many bug fixes: mail posts no longer get stuck or lose cargo, a boss charge no longer knocked players the wrong way, fixed a double-hit on parried rockets, the Crusher's slam respects its cooldown, shield domes persist across reloads, and more.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:ePda42no:jOEDzBv3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ePda42no:jOEDzBv3"
}

