Tags
Creators
Details
0.1.0-alpha.1
Compatibility
Changes
MH Warfare 0.1.0 Alpha 1
The first public alpha release of MH Warfare is now available.
This version introduces the core drone platforms, flight systems, remote camera technology, modular equipment, component-based damage, communication features, and initial multiplayer support.
New Drone Platforms SYCH-1 — fixed-wing reconnaissance drone Wild Hornets — high-speed FPV multirotor platform Mavic — stabilized reconnaissance quadcopter P1-SUN — high-speed unmanned aircraft Baba Yaga — heavy multirotor platform Added Platform-specific flight controls and HUD systems FPV cameras and long-range Remote View Day, night-vision, and thermal camera modes Modular drone assembly Interactive Ground Station model and interface Motors, propellers, batteries, cameras, antennas, and payload modules Component-based damage and repair systems Individual motor and component failures Battery fires and platform-specific critical failure behavior Independent payload mounting and release Autopilot functions for supported aircraft Keyboard, mouse, and joystick support Proximity voice chat Portable and long-range radio systems English, Ukrainian, and Russian localization Server configuration options Client-side visual configuration options Multiplayer and dedicated server support Compatibility Added compatibility handling for Embeddium Added compatibility handling for Oculus Added compatibility handling for Embeddium Extra Added compatibility handling for Sinytra Connector environments Fixed startup conflicts related to LevelRenderer mixins Improved Remote View entity synchronization Improved compatibility with optimized rendering environments Requirements Minecraft Java Edition 1.20.1 Minecraft Forge 47.4.x Java 17 GeckoLib Installation on both the client and server
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:jHNuLxp4:qx6ECZ8n"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jHNuLxp4:qx6ECZ8n"
}

