Tags
Creators
Details
Licensed LGPL-3.0-only
Published 6 months ago
Updated 3 months ago
All versions
2.0.0
Release
Simply Airdrops 2.0.04 months ago 1,166
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Simply Airdrops 2.0.0 - NeoForge 1.21.1
Highlights
- Added a full NeoForge 1.21.1 port of Simply Airdrops.
- Added the flare gun as an immersive way to call airdrops.
- Added configurable airdrop spawn height, fall speed, radio consumption, and radio controller craftability.
- Added airplane sounds for radio, flare gun, and timed airdrops.
Gameplay
- Flare gun can call an airdrop, plays launch effects, creates a flare/firework particle burst, and has durability.
- Flare gun can appear in Pillager Outposts, Desert Pyramids, and Shipwreck Supply Chests.
- Timed airdrops now announce the drop location and play airplane audio when spawned.
- Red airdrop particle stream is longer and more visible.
Loot And Crates
- Fixed generated crate items not carrying their saved loot correctly on NeoForge 1.21.1.
- Fixed crate placement so filled crate items load their stored loot into the placed crate block entity.
- Fixed medic crate potions using old NBT by converting them to 1.21.1 potion components.
- Filtered known buggy TacZ attachment loot entries to reduce broken weapon crate drops.
Compatibility And Porting
- Migrated mod metadata, registries, loot modifiers, recipe conditions, config screen, block entities, and GeckoLib usage to NeoForge 1.21.1.
- Updated global loot modifiers from Forge data paths to NeoForge data paths.
- Kept 2D inventory icons for crates while retaining in-world GeckoLib crate models.
Build
- Minecraft: 1.21.1
- Loader: NeoForge 21.1.233
- Mod version: 2.0.0
Optional dependencies
Any compatible version
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:aLnr371z:V3dO4Vhq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aLnr371z:V3dO4Vhq"
}

