Tags
Creators
Details
1.0.0
Compatibility
Changes
Towns and Nations 1.0.0
New :
-
Plugin is now 1.21.11+ (previously 1.19+)
- Added copper chest protection
- Tooltips have been removed from comsetic item in GUIs
- Placing a property sign at the bottom of a block will show a hanging sign instead of a floating sign
-
Add option to rename forts
-
Reworked heldByAlly & heldByEnemy : only check when an attack is ongoing rather than the entire war.
-
Option to allow all players to join a town without approval
-
Right clicking on a fort banner will display a descriptive text
-
Display fort protection radius and fort capture time in gui
-
Better /tan map
- Replacing paper API with spigot
- UI is more coherent with plugin style
- Better display of occupied chunk
- Display fort chunks on map :hut:
- Display Landmarks on map :sparkle:
- If a chunk is protected by a fort, it will be displayed in /tan map
-
If the chunk where the territory spawn is located is unclaimed or occupied, it is unusable
-
Valid world check will not be done after the server start.
-
The check for valid worlds will now be done after all plugins are loaded
Bug fixes
- Trying a fix on a bug causing errors on certains UUID if the server is in offline mode
- Fix registering banner playing "NOT_ALLOWED" sound even if the banner have been successfully set
- Fix ability to bypass minecart and boat permission by using the secondary hand
- Fix wrong support block being protected when placing a property sign down of a block
- Fix bossbar not showing to a player that join the server in the middle of an attack
- Fix missing chunkPermissionConfig "nationPermissions"
- Fix wrong loading of Internal vault support
Others
- Small economy refactoring
- Lowering visibility of data inside DbManagers
- More work on Centralizing JsonStorages
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:Ag2I6USg:YA4EcuAv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ag2I6USg:YA4EcuAv"
}

