Tags
Creators
Details
0.17.1
Compatibility
Changes
New :
Add config option for double permission check when :
-
Breaking chest (
BREAK_CHEST_NEED_INTERACT_CHEST_PERMISSION) -
Breaking furnace (
BREAK_FURNACE_NEED_BREAK_FURNACE_PERMISSION) -
Luckperms integration
- Luckperms context support + wiki page
- Upgrades can be used to unclock luckperms permission
-
New placeholders :
%tan_player_colored_town_tag_or_empty%%tan_player_colored_town_tag_or_{text to replace}%
-
If a territory max level is below 8, "MAX_LEVEL_REACHED" will be written instead of "LEVEL_LOCKED"
- Setting a territory max level to 0 will lock the upgrade menu from a territory type Set by default for Regions and Nations
Bug fixes
- Fix duplicates message when using
/tanadmin reload - Fix missing Lang files reload with
/tanadmin reload - Update discordSrv to SphereLib 0.6.1
- Fix Shift click not being blocked in TaN's GUI
- Fix blocking TerritorySettings menu from players, blocking them from leavingTODO ADD @ of creator
- Fixed BStat relocation
- Fix internal error when deleting a non-occupied fort
- fix max territory level offset in upgrade menu, allowing to upgrade 8 level above the maximum
- Fix Upgrade menu previous/next buttons not updating level bar
- Fix ability to create one private property above the max cap
- Fix landmark not automatically unclaimed if prerequisites are no longer met
- Removed all "early save" actions. This could cause errors in case of crash/force stop since only a part of the storage files where updated.
- Fix double save each time a chunk were claimed/unclaimed
Others
- Completing removal of HeadUtils.java
- Removing most of TownDataStorage singletons
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:WSg33ids"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ag2I6USg:WSg33ids"
}

