Links
Tags
Creators
Details
All versions
0.1.2
Release
Burlan Territories (BurlanTowny/BurlanT) 0.1.2last year 23
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 0.1.2
This Changelog has been written by.. Pizzlad!
Features
- Block Glitch Prevention: Added a sophisticated system to prevent players from towering up using block glitches in protected claims.
- Features smart detection that checks player location, vertical movement, and head angle to ensure accuracy.
- Includes a configurable "anger level" that decays over time, preventing false positives.
- Punishments include on-screen messages, random camera spinning, and configurable potion effects.
- Mining Guide Page: Added a new
/b guidepage dedicated to explaining the custom mining system.- Dynamically displays information from the server's configuration, such as mining locations and source blocks.
Improvements
- Warzone Map Display: The minimap and
/t mapnow display captured warzone territories with relationship-based colors for the core chunks.- Allied-owned warzones appear blue.
- Neutral and enemy-owned warzones appear yellow.
- Unowned warzones remain red.
- The core chunk of a captured warzone is now marked with a unique symbol to distinguish it from a standard core chunk.
Bug Fixes
- Contestable Warzones: Fixed a critical issue where captured warzone territories could not be attacked by other towns. They are now correctly treated as contestable land, with the current owner acting as the defender.
- Warzone Flag Placement: Resolved a bug that prevented players from placing war flags in unowned warzone territories.
- Warzone Minimap Visibility: Fixed an issue where warzone territories were incorrectly displayed as unclaimed land instead of hostile territory.
- Block Glitch Prevention Bypass: Patched a loophole that allowed players to bypass the anti-glitch system by exploiting the height-tracking logic.
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:3GnxK9Xi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:m9hjldZe:3GnxK9Xi"
}

