Links
Tags
Creators
Details
0.2.3
Compatibility
Changes
BurlanT Changelog
This documents all notable changes to BurlanT.
This Changelog has been written by... Pizzlad!
Dynmap Has Been Updated! (Reinstall)
You might have to backup your config file and delete it to fix town upkeep!
Version 0.2.3
Features
-
Per-Town and Per-Nation Upkeep/Income Toggles:
- Added
upkeep_enabledandincome_enabledflags to towns; nations getupkeep_enabled. - New admin commands:
/badmin town toggle <upkeep|income> <TownName> [on|off|toggle|view]/badmin nation toggle upkeep <NationName> [on|off|toggle|view]
- Income and upkeep tasks now respect these flags.
- Added
-
Data Version 3 Migration:
- Automatic migration of
towns.jsonandnations.jsonto add the new flags with safe defaults (true).
- Automatic migration of
-
Config Versioning with Comment-Preserving Updates:
- Introduced
config_versionwith a version-and-rewrite updater. - On update, the plugin backs up
config.yml, writes the new default (keeping all comments), and overlays user values. - Map sections like
globalResources.incomeandglobalResources.oremerge new defaults without overwriting user values. - User lists like
mining.source-blocksare preserved as-is.
- Introduced
-
Upkeep Item Consistency and Messages:
- Fixed upkeep messages to display the configured upkeep item for towns and nations.
- Resolved stale command references on config reload by re-registering command executors and listeners.
-
Backups Enhanced:
config.ymlis now included in automatic backups.
Fixes
- Corrected YAML structure in default
config.ymlto prevent parsing issues. - Ensured reload rebinds commands and listeners to fresh managers after config changes.
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:hr3UB2Ca"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:m9hjldZe:hr3UB2Ca"
}

