Tags
Creators
Details
1.0.0
Compatibility
Required content
Changes
LibreBuild. First Release
I'm excited to introduce LibreBuild! The purpose of this project is to bring Schematic Placement to all players, not just administrators. But how does it work?
- Administrators can easily create and load schematics using the WorldEdit API. They can also give themselves or other players a blueprint of any schematic stored in the WorldEdit/schematics folder.
- Players can place these schematics using the blueprint they have been given.
Can users grief with this implementation? No, users should not be able to grief. LibreBuild includes an additional layer of protection. Before a blueprint is placed, the plugin checks the schematic’s size and verifies whether it intersects with a protected WorldGuard region.
Are there any permissions? Yes! Currently, there are two permissions: 1.
librebuild.item.use→ Default: true. Allows players to place schematics using a blueprint. 2.librebuild.command.admin→ Default: OP. Grants access to all plugin commands (non-administrators should not have this permission).
Which language are supported? Currently, LibreBuild supports the following languages: English (en), Spanish (es), French (fr), Russian (ru), and Dutch (de). However, you can add your own .yml file and set it as the target language. Alternatively, you can simply edit the existing language.yml file to customize the translations as you like.
This plugin aims to bring back an old game mechanic: the ability to purchase houses and structures, so players don’t have to rely solely on their building skills to own a beautiful home or a well-designed structure.
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:KRBbA3Dr:UBvWaDCK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KRBbA3Dr:UBvWaDCK"
}

