Tags
Creators
Details
Licensed LGPL-3.0-only
Published last year
Updated last week
All versions
2.7.9
Release
BetterStructures 2.7.9last week 3,715
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.4โ1.21.11
Platforms
Paper
Purpur
Spigot
Changes
BetterStructures 2.7.9:
- [Fix] Modular dungeons generate naturally again as players explore. Since 2.7.1 almost all of them were skipped; now only spawn protection or a WorldGuard region over the dungeon's area stops one.
- [Fix] Areas pregenerated with /bs pregenerate or Chunky get structures and dungeons again.
- [Fix] On Paper, structure pastes no longer stall in chunks with no player nearby, which blocked every later paste.
- [Fix] Treasure files no longer fail to load at startup when another plugin loads at the same time, which left barrels empty.
- [Fix] Dyed shulker boxes now get loot like plain shulker boxes.
- [Tweak] /bs pregenerate stats now count structures once they finish pasting and show how many are still waiting.
- [Tweak] BetterStructures now says clearly when the installed WorldEdit build is what breaks schematic loading, and schematic errors name the installed file.
- [Tweak] The setup menu's update buttons now explain restart-free updates, and content that isn't released yet says so instead of failing to download.
- [Fix] On Windows, saving a config file that an antivirus or file indexer briefly holds open no longer fails.
- [Fix] Content package updates now archive files the new version no longer ships.
- [Fix] /nightbreak plugins now installs missing plugins into plugins/, so they load on the next start.
- [Fix] Restart-free updates no longer keep the old copy of BetterStructures in memory while a WFC world is open.
Optional dependencies
Any compatible version
Any compatible version
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:KYXglN2M:Cl94qSi8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KYXglN2M:Cl94qSi8"
}

