1.5.5
Compatibility
Changes
Description: The Team Claims update brings a powerful Team Claim System to AdvancedTeams! Now, teams can secure chunks to create protected zones and safely store resources, shielded from interference by other players. This update, crafted with the sweat of my brow, delivers game-changing territory management for enhanced team play and strategy! ️✨
Features: Chunk Claiming: Teams can now use /teams claim claim to secure chunks and mark their territory! Upon claiming, flame particles appear at chunk borders for 15 seconds, signaling the area is protected.
Claim Settings GUI: Leaders and Managers can customize access and protection levels for each claimed chunk with /teams claim settings, including options for block breaking, mob interaction, and door access control. ⚙️
Flexible Unclaiming: With /teams claim unclaim, teams can release a claimed chunk to make it available for others.
Claim Particles: Teams can now toggle claim borders on or off using /teams claim particles! When activated, flame particles appear at the borders of claimed chunks for 15 seconds, signaling that the area is protected.
Configurable: The claim system can easily be toggled on or off in config.yml for full server control! New Commands: Player Commands /teams claim create - Claim the chunk the player is currently in for the team. /teams claim delete - Unclaim the chunk the player is currently in. /teams claim settings - Open a GUI for claim settings (block breaking, mob interaction, door access). Each feature is designed to empower teams with new, secure ways to collaborate and defend their hard-won space!
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:DNgR1EpX:SVdFJU4g"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DNgR1EpX:SVdFJU4g"
}

