Links
Tags
Creators
Details
1.4.0
Compatibility
Required content
Changes
Skyfront — 1.4.0 a full drone-warfare add-on for Superb Warfare, moved to Minecraft 1.20.1 and Forge.
Added
- Mavic 3 Pro — recon quadcopter with a camera-app interface, smooth zoom up to 8× and droppable ordnance (RGO, M18 smoke, C4). Range 500 blocks.
- Mavic 3T — thermal version: bodies, engines, explosions and smoke glow on its camera. Range 1000 blocks.
- P1-SUN — interceptor with a contact-fused warhead, rate (acro) flight and a Betaflight-style OSD; also comes with a thermal camera.
- FPV drone — kamikaze carrying a PG-7VM, Yasin TBG or mortar shell; GPS Betaflight OSD, analog video with interference, props and warhead in view, brick stand for take-off.
- Molniya — fixed-wing strike drone with an INAV-style OSD and wind gusts.
- Launch rail — the Shahed and the Molniya now take off from it.
- Route planning — the terminal plans Shahed routes with waypoints on a terrain map.
- RC transmitter and gamepad support, with calibration and switch mapping.
- Burnt debris — downed drones and the Shahed break into pieces that fly up to 100 blocks from a high blast.
/skyfront config reload— applies config changes live and syncs them to all players.
Changed
- Moved to Minecraft 1.20.1 / Forge. Superb Warfare is now required.
- Commands moved from
/shahedto/skyfront. - Config moved to
config/skyfront-common.toml, with a section for every drone. - Downed drones fall realistically: planes spiral in, quads tumble.
Performance
- Drones are flown with client-side prediction against an authoritative server — no input lag for the pilot.
- Long-range links up to 1000 blocks stream the terrain around the drone to its pilot.
- Debris is simulated on the clients from a single packet instead of by the server.
Note: not compatible with 1.2.0 worlds or configs — start fresh after updating.
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:ATisIhZ7:wQ5BWZ8z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ATisIhZ7:wQ5BWZ8z"
}![[SBW] Skyfront](https://cdn.modrinth.com/data/ATisIhZ7/25d70aba38f54ee251087f140eae34ad712e0cbf_96.webp)

