All versions
1.17.0
Release
Bloxy's Structures 1.17.02 years ago 270
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
- Increased amount of flying structures, including more variety in Flying Islands, Flying Houses, and Floating Sentinels
- Increased build height to acommodate the increase in flying structures to 512
- Right-click actions for Bloxy's Scythe and Darkness Arm have now been rebined to a keybind, default key is "R"
- You can now call back Bloxy's Scythe while it's flying by pressing the previously mentioned keybind, the default is "R"
- Bloxy's Scythe attack damage reduced to 7
- Darkness Arm has been renamed to Arm of Shadows
- Improved and Buffed Arm of Shadows' shockwave attack, dealing damage and pushing entties outwards based on distance
- Cooldown between item ability uses for Bloxy's Scythe and Arm of Shadows
- Added new Illager Structures
- Added new Cowlin Structures
- Added new ambient Stone Monoliths
- Added Battletower structure with 40+ different possible rooms
- Added the Treemoo, a new cow variant like the Mooshroom cow but has Sapplings instead of Mooshrooms, can be sheared. Can also right-click with bone-meal to regenerate their sappling or wait for them to grow back
- Fossils can now generate
- Added Giant Frogs, Giant Goats, Giant Rabbits, Giant Chickens
- Giant Pigs, Giant Sniffers and Giant Cows are now their vanilla mob counterpart but scaled with the help of Attributes
- Optimized Underground structures to use Trial Spawners, resulting in less entities for better performance.
- Replaced Adventure Realm Trial Chamber with Vanilla Trial Chamber
- Nerfed Inferno Shield fire duration from 5s to 3s
- Inferno Hydra wings now have animations.
- Ported mod over to NeoForge 1.21.1
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:vo7reSUa:oTTFcQCD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vo7reSUa:oTTFcQCD"
}

