Tags
Creators
Details
4.2.0
Compatibility
Changes
VERSION 4.2.0 THE WAR UPDATE: 30/04/24 -Added the Forgotten Church, with an unknown new purpose… -Added three new boss battles, of higher difficulty than the Battle of Hammibal! -One can fight the Desert Fox, Rommi, and his tank divisions! -One can fight the ace Red Baron, and his massive air force! -One can fight the Admiral Mimitz, and his massive fleet! -Added Mirikmar-class Corvette, which is the new main representation of Alliance and player naval power. -Added different Tonk Turret types: HE Cannon, Autocannon, Flamethrower. These are randomly selected whenever you place a Tonk Turret. They are activated by holding a Bombimi, Dispenser, or Flamethrower in the hand slot of a Tonk Turret which is useful for those that wish to edit Tonks in Creative. -Added a new way to declare war on your friends and form teams!
-Most Mi voices have been converted to Mono and will now properly scale in 3D space, as has been requested for a long time! Not every sound effect has been tested, so I urge players to be vocal about the current state of the Mi soundscape. -Recipe for Memory of Hammibal requires only 1 Goobie essence now -Very slightly reduced technology costs for Alliance and Tubian colonies -Metallium machines now have a small chance to drop an entire Metallium Block -Made Terraform config more accurate -Buffed Trackers with +1 melee damage -Trackers have 20% less resting time and are more active -Increased Officer pick up speed for non-Seedling items -Snipers deal normal damage and should be fixed: Emergency damage limiter added -Updated Tonk Turret particles -Tonk Turrets can now easily be placed on any Mi (machine). -Tonk combat behavior changed: Will now move less when at range -Reworked damage calculation for Bombimis & variants -Removed Stance transceivers. -Forgotten Rock is now used instead of Darkbrick to craft Wardrock -Three new Wardrock variants were added for decoration purposes, including bricks, pillars, and glass. -Stripped Wood variants added for decoration purposes
-The new DECLARATION block is crafted using a mistrum sword and eight Mistrum bricks. You can place this with a sign above it to declare war on all usernames listed on the sign. Whenever your Mis spot any listed player or Mi owned by such a player, they will engage. -As long as a DECLARATION block exists, your Mis are friendly to all players. -You can type nothing on these signs to to make your Mis friendly to everyone. -You can type ALL on these signs to become hostile to all other player’s armies. -Declaration blocks are active as long as they are chunk loaded. To cover larger areas, you’ll need multiple Declaration blocks. -Of course, these blocks can be sabotaged. Guard them well!
-Divided Creative mode tabs into “Creative-only” Mi items and all other Mi items -Config health changes now work in percentages -Config now allows melee attack damage changes for all Mis against all targets, or specifically against foreign mobs, for balancing in invasion-mod-heavy modpacks -Added alternative dimension whitelist to config -Changed Terraform config format for ease of use -Removed config for co-op because of Declaration rework -Changed default config section for “They Know” to false, because player experience is more important than lore -Increased limits in the Config for people who have NASA supercomputers
-Fixed more Relicoid spawning than was intended -Fixed turning of piloted non-land vehicles -Fixed self-destructing Tonk Staff -Fixed letter of Attack strength being very subpar -Fixed Embassies not properly storing Power Level of the world -Fixed entities.EntityMi$ScanTravel.m_8056_(EntityMi.java:4833) -Fixed block.TileEntityCore.nearbyColonyPurpose(TileEntityCore.java:1419)
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:drGKHwAq:ejHzPphs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:drGKHwAq:ejHzPphs"
}

