Tags
Creators
Details
0.8.0-beta.6
Compatibility
Required content
Changes
MH Warfare — Changelog
0.8.0 Beta 6
Beta 6 is a major UAV, fiber-optic control, radar, Remote View, multiplayer stability and combat-effects update. It introduces the Khizhak 13 REBOFF fiber-optic FPV drone, the Lys-3M radar system, expanded Ground Station functionality, improved Chuyka 4.0 behavior, optional night-vision camera upgrades, improved long-range drone presentation, physical fiber interaction and new explosion effects.
Khizhak 13 REBOFF
- Added the Khizhak 13 REBOFF fiber-optic FPV drone.
- Added physical fiber-optic cable deployment during flight.
- Added finite fiber spool capacity.
- Added 5 km, 10 km, 15 km and 20 km fiber spools.
- Fiber usage is based on the actual travelled cable route.
- Returning toward the operator does not restore already deployed fiber.
- Added dedicated fiber spool geometry and presentation.
- Added physical cable connection between the operator and the drone.
- Added fiber-link state to drone control interfaces.
- Added dedicated fiber-optic FPV behavior.
- Improved Khizhak flight and camera presentation during sharp turns.
- Improved cable payout presentation between normal gameplay and Remote View.
Fiber-optic control system
- Fiber-optic control is independent from normal RF communication.
- Electronic warfare and RF interference do not degrade an intact fiber connection.
- Fiber connections do not use RF fallback after the cable is severed.
- Losing the physical fiber connection immediately removes drone control.
- Motor inputs are removed after fiber loss and the aircraft continues with physical flight and gravity.
- Existing camera damage, power loss and component damage can still interrupt the video feed.
- Added clear connected, disconnected and broken fiber states.
Physical fiber cable
- Fiber cable now follows a persistent physical route through the world.
- Cable can settle onto terrain instead of remaining as a straight beam.
- Added retained cable bends and route corners.
- Improved cable settling and terrain interaction.
- Improved cable interpolation and payout smoothness.
- Improved cable endpoint alignment with the operator and drone.
- Improved cable attachment to the correct spool position on the aircraft.
- Improved cable rendering in both the normal world and Remote View.
- Broken cable sections remain temporarily in the world before fading.
- Detached cable remnants continue using bounded physical settling.
- Improved cable persistence across world saves and reloads.
Fiber cable interaction and damage
- Players can physically cut accessible fiber cable sections.
- Fiber belonging to other players can also be cut.
- Cutting requires maintaining interaction with a visible nearby section of cable.
- Infantry bullets can physically sever fiber cable.
- Bullet-to-fiber collision follows the actual projectile trajectory.
- Bullets cannot cut cable through a wall or another object hit first.
- Fiber cable can be destroyed by contact with lava.
- Cable damage does not force-load surrounding terrain.
- Severing the cable immediately disconnects both physical ends.
- An already armed airborne Khizhak can retain its existing impact-fuse behavior after cable loss and detonate on a real surface impact.
Long-range fiber presentation
- Greatly increased visible fiber-cable range.
- Fiber can remain visible at distances of up to approximately 2640 blocks.
- Added bounded long-range fiber history for already observed cable sections.
- Added distance-based cable rendering detail to protect client FPS.
- Straight distant cable sections can be simplified while important bends remain preserved.
- Increased route-corner detail for more natural cable wrapping and direction changes.
- Improved cable visibility without increasing server cable-search distance or forcing additional chunks to load.
- Physical cable simulation and client rendering remain independently bounded.
Night-vision camera upgrades
- Added optional Night-Vision Camera Upgrade support for selected FPV platforms.
- Wild Hornets now support an optional night-vision camera upgrade.
- Khizhak 13 REBOFF now supports an optional night-vision camera upgrade.
- Molniya-1 now supports an optional night-vision camera upgrade.
- Normal daytime video remains available without installing an additional day camera.
- Supported upgraded drones can switch between DAY and NIGHT VISION modes.
- Camera upgrade mass is included in the assembled aircraft configuration.
- Existing compatible saved configurations remain supported.
- Improved synchronization of active video-sensor mode in multiplayer and Remote View.
Molniya-1
- Improved Molniya-1 performance with heavy payloads.
- Added load-aware propulsion compensation for heavy configurations.
- Heavy payloads no longer reduce forward-flight performance as severely.
- Existing maximum speed, battery consumption and physical flight behavior remain preserved.
- Improved Remote View smoothness during aggressive banked and sharp-turn flight.
Lys-3M radar
- Added the Lys-3M radar.
- Added a physical deployable radar entity.
- Added animated radar antenna rotation.
- Added radar health and damage.
- Added radar power and fuel management.
- Radar can be refueled using redstone.
- Added radar repair using iron.
- Radar state is preserved when packed and deployed again.
- Destroyed or heavily damaged radar systems stop operating.
- Added owner and allied-team access rules.
- Radar detects supported UAV targets using a rotating server-authoritative scan.
- Added terrain masking and line-of-sight terrain checks.
- Unknown terrain is not treated as automatically transparent.
- Small UAV detection range is approximately 8 km.
- Larger low-flying aircraft detection range is approximately 12 km.
- Radar rotation speed is approximately 20 degrees per second, giving an approximately 18-second full scan.
- Improved physical antenna rotation smoothness.
- Improved Ground Station radar-sweep smoothness.
- Radar scanning uses bounded workload limits to protect server performance.
Ground Station radar
- Added a dedicated RADAR tab to the Ground Station.
- Added Lys-3M radar stations to the shared tactical map.
- Added detected-aircraft contacts.
- Radar contacts represent the last successful scan instead of continuously exposing live target coordinates.
- Old contacts fade when they are no longer detected.
- Added friendly drone identification for player-owned aircraft.
- Improved radar-map presentation at large map scales.
- Radar terrain processing does not generate a massive surrounding terrain area.
- Multiple accessible radar stations can contribute information to the Ground Station.
Ground Station flight routes
- Expanded high-altitude route support for long-range fixed-wing UAVs.
- FP-1 Ground Station routes can reach approximately Y 2000.
- Geran-2 routes can reach approximately Y 4000.
- UJ-25 routes can reach approximately Y 6000.
- Geran-3 routes can reach approximately Y 9100.
- Improved altitude editing for high-altitude route planning.
- Client route editing and server validation now use matching aircraft-specific altitude limits.
- Strike-point behavior remains terrain-relative.
Chuyka 4.0
- Improved Chuyka 4.0 held-camera performance.
- Reduced unnecessary Remote View terrain workload while using Chuyka as a held detector.
- Improved multiplayer behavior while monitoring analogue FPV video.
- Passive Chuyka monitoring no longer replaces the player's normal-world entity-tracking position.
- Nearby players, mobs, dropped items and other entities continue updating normally while Chuyka video is active.
- Improved video stability while rapidly switching hotbar slots.
- Improved Remote View session startup and shutdown behavior.
- Improved synchronization between the viewed drone body and camera.
- Improved Wild Hornets and Khizhak camera presentation during aggressive movement.
- Chuyka can display the synchronized DAY / NIGHT VISION state of supported drones.
- Improved Lys-3M visibility through Chuyka Remote View.
- Fixed Lys-3M disappearing and reappearing while viewed through Chuyka.
Shader compatibility
- Improved Chuyka compatibility with external shader packs.
- Added runtime compatibility handling for Iris, Oculus and OptiFine-style shader environments.
- Chuyka uses a bounded secondary-world rendering rate while external shaders are active.
- Added adaptive rendering limits for expensive shader passes.
- Improved framebuffer and viewport restoration after Remote View rendering.
- Reduced unnecessary full-screen post-processing during shader-compatible Chuyka rendering.
- Improved Chuyka screen and LED presentation during shader rendering.
- Normal FPV and non-shader behavior remain preserved.
Remote View
- Improved Remote View stability for FPV and passive camera systems.
- Improved synchronization of primary drone body and camera presentation.
- Improved handling of entities using explicit Remote View snapshots.
- Fixed competing Remote View tracking paths for the Lys-3M radar.
- Lys-3M now uses one stable Remote View lifecycle.
- Fixed radar flickering and repeated disappearance/reappearance in direct FPV cameras.
- Improved passive Chuyka Remote View behavior without affecting normal player tracking.
- Improved session cleanup when opening and closing remote video feeds.
- Reduced entity churn caused by rapid Remote View session changes.
- Existing server-authoritative drone simulation remains preserved.
Long-range drone visibility
- Improved transition between normal entity rendering and long-range drone proxies.
- Fixed high-altitude UAVs becoming invisible while flying almost directly above a player.
- Geran-2 and other supported long-range aircraft remain visible during the transition between nearby and distant rendering.
- Long-range proxies now remain active until the actual normal-world aircraft has really been rendered.
- Improved long-range presentation without increasing server tracking or chunk-loading distance.
- Existing bounded long-range proxy limits remain in place to protect performance.
Drone explosions and glass damage
- Drone explosions can now shatter nearby windows and glass.
- Glass-breaking distance varies depending on the actual drone or payload explosion profile.
- Larger and stronger explosive payloads can break glass farther away.
- Smaller payloads and battery-related explosions have weaker effects.
- Solid walls and terrain reduce blast pressure reaching windows behind them.
- Multiple obstacles further reduce the effective glass-breaking range.
- Glass panes provide less protection than solid walls.
- Added support for vanilla and compatible modded glass and glass panes.
- Glass-breaking uses a bounded pressure-propagation system instead of scanning every block around an explosion.
- The system only processes already loaded terrain and does not create additional chunk-loading demand.
Drone components and organization
- Fiber spools are now organized with other drone components.
- Launch-booster components are now organized in the drone-components category.
- Existing registry IDs, saved aircraft and assembly compatibility remain unchanged.
- Improved optional camera-upgrade organization for supported FPV aircraft.
Multiplayer and synchronization
- Added synchronized physical fiber-link state.
- Added synchronized radar information for Ground Station users.
- Added synchronized drone video-sensor mode.
- Improved Remote View entity synchronization.
- Improved passive-camera behavior in multiplayer.
- Improved long-range aircraft presentation for non-host players.
- Improved synchronization during transitions between normal and distant aircraft rendering.
- Existing physical drone simulation remains server-authoritative.
Performance and scalability
- Fiber simulation uses bounded per-tick processing.
- Long-range fiber rendering uses a bounded client history and render budget.
- Distant cable sections use level-of-detail simplification.
- Fiber systems do not force-load terrain along the entire cable.
- Radar scanning uses bounded candidate, terrain and ray-processing budgets.
- Radar terrain checks avoid large synchronous terrain generation.
- Chuyka held-video rendering uses reduced Remote View terrain demand.
- External-shader Chuyka rendering uses adaptive frame-rate limits.
- Long-range drone visibility improvements do not increase server entity-tracking distance.
- Glass destruction uses bounded pressure rays and loaded chunks only.
- Existing projectile, Remote View and drone chunk-loading protections remain preserved.
Release and compatibility
- Updated the public version to 0.8.0-beta.6.
- Updated the general MH Warfare mod description.
- Removed outdated Beta 5 release text from the in-game mod description.
- Preserved existing player-facing test utilities and microphone-test controls.
- Preserved the Alexa Spatium (Experimental) designation.
- Install the same MH Warfare version on every client and server.
- A compatible GeckoLib version is required on all clients and servers.
Summary of the biggest Beta 6 additions
- Khizhak 13 REBOFF.
- Physical fiber-optic FPV control.
- 5 / 10 / 15 / 20 km fiber spools.
- Physical cable payout, terrain settling and persistent route bends.
- Player, bullet and lava fiber severing.
- Long-range fiber presentation up to approximately 2640 blocks.
- Improved fiber route-corner detail and rendering performance.
- Optional night-vision camera upgrades.
- Improved Molniya-1 heavy-payload flight.
- Lys-3M radar.
- Ground Station RADAR map and radar contacts.
- Expanded high-altitude Ground Station flight routes.
- Major Chuyka 4.0 performance and multiplayer improvements.
- Improved shader-pack compatibility.
- Improved Remote View entity stability.
- Fixed Lys-3M Remote View flickering.
- Fixed high-altitude drones disappearing above players.
- Added obstacle-aware window and glass destruction from drone explosions.
- Broad multiplayer, rendering and performance improvements.
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:eXfx5j7T"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jHNuLxp4:eXfx5j7T"
}

