Tags
Creators
Details
2.5.0-beta-neoforge+1.21.1
Compatibility
Changes
Beta 2.5.0 is available for Minecraft 1.21.1 on both the Fabric and Neoforge platforms
Native Builds for both platforms!
This is the first multi-platform release, removing the requirement for Sinytra Connector on Neoforge and reducing bugs and incompatibility issues on that platform.
New Additions
- Added the "Levita Harness", crafted using Levita Beads and Flaxweave and allows you to anchor yourself at a y level to help with building and crossing gaps
- Added Flaxweave Boots that have inherent feather falling, powder snow walking, and skulk sensor immunity
- Added an exclusive enchantment "Rending" (I-III) for the Bloomed Blade which has a chance to grant additional souls when collecting a new mob
- Added Ominous bottles to Birdcage loot tables and added Ominous Trial wave rewards including a new exclusive Moa breed
- Added Breezes as uncommon natural spawns in Paradise
- Added Levita Arrows can be crafted (and looted) which have inverted gravity
- Enhanced Levita Rails to support floating up and down slopes to allow for more creative uses
- Also added a new rare room to the Palace to showcase the rails
Fixes
- Fixed several incompatibilities with other mods that prevented loading, locked up, or caused crashes including Wilder Wild and Atmospheric
- Fixed the Glazed Gold Upgrade Recipe not duplicating correctly
- Fixed issues with Calcite Flower Pots
- Various other minor fixes on the Neoforge version, fixed by now being a native version
- Fixed items placed in tree taps and incubators only facing one way, and not rotating with the player's facing
Other Changes
- Added the
paradise_lost:is_paradise_lostbiome tag for ease of use in addons or modpacks
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:IKpsG0nF:ORj1WxSK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IKpsG0nF:ORj1WxSK"
}

