Tags
Creators
Details
1.10.0
Compatibility
Required content
Changes
Full English changelog available on GitHub. Full French changelog available on our Discord.
Summary
LoxyCraft 1.10.0 adds Netherite Scrap compression blocks and introduces a new Flight Infusion Core, while also fixing several tool tag and infusion behavior issues.
Fixed
- Fixed tool and pickaxe tags on several blocks
- Fixed compressed Quartz blocks not dropping correctly when mined with a valid pickaxe
- Fixed Resistance infusion stacking beyond Resistance I
- Fixed duplicated Resistance applications being able to increase the effect level
- Fixed Creative Flight behavior after death and respawn
Added
- Added Netherite Scrap Block
- Added Compressed Netherite Scrap Blocks from x1 to x9
- Added Flight Infusion Core
- Added Creative Flight infusion for chest-slot equipment
- Added creative flight support on Netherite Chestplates and Elytra
- Added fall damage protection while wearing chest-slot equipment with the Creative Flight infusion
- Added Elytra compatibility for chest-slot infusions:
Resistance,Fire Resistance,Creative Flight, andUnbreakable
Improved
- Improved chest-slot infusion compatibility between Netherite Chestplates and Elytra
- Improved infusion handling to keep multiple chest infusions compatible on the same item
- Improved Creative Flight behavior when equipping or removing infused chest-slot equipment
Notes
- Resistance is now limited to Resistance I
- Creative Flight only works while the infused chest-slot item is equipped
- Removing the infused chest-slot item disables creative flight normally
- Fall damage protection only applies while the Creative Flight infusion is active
Optional dependencies
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:1Eb2AwPa:lf92nMMf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1Eb2AwPa:lf92nMMf"
}

