Links
Tags
Creators
Details
All versions
0.2.1
Release
Burlan Territories 0.2.1last year 35
Uploaded by
Compatibility
Minecraft: Java Edition
1.21–1.21.8
1.20.x
1.19.x
1.18.x
Platforms
Paper
Purpur
Changes
BurlanT Changelog
This documents all notable changes to BurlanT.
This Changelog has been written by... Pizzlad!
Version 0.2.1
Features
- Core Territory Management:
- Added a new
/town corecommand, allowing town leaders (or ranks with theSET_COREpermission) to change their town's core territory. - Implemented a configurable cooldown to prevent frequent changes.
- Added
/badmin town core <TownName>for administrators to set the core territory for any town.
- Added a new
- Wilderness & Unclaimed Land Protection:
- Introduced a new
world-protectionsection inconfig.yml. - Administrators can now separately configure permissions for
place,break,interact, andchestactions in both the wilderness (chunks with no territory) and in unclaimed territories.
- Introduced a new
- Administrator Bypass Mode:
- Introduced a new
/badmin bypasscommand, allowing administrators with the appropriate permission to toggle a bypass mode. - When enabled, bypass mode lets administrators ignore all town and plot protections, including restrictions on building, breaking blocks, opening chests, and interacting with entities.
- Introduced a new
- Data Versioning & Migration:
- Added a data versioning system to automatically manage and upgrade data files (
towns.json,nations.json,players.json, etc.). Will be used for future updates.
- Added a data versioning system to automatically manage and upgrade data files (
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:m9hjldZe:PPBhLSZg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:m9hjldZe:PPBhLSZg"
}

