Tags
Creators
Details
1.2
Compatibility
Required content
Changes
AntiClaim Plugin - Wand System Edition
๐ What This Is
A Minecraft Spigot/Paper plugin that prevents GriefPrevention claims from being created too close to each other. Includes a WorldEdit-style wand tool for creating bypass regions.
โจ Features
๐จ Wand Tool - Golden Axe for visual region selection
๐ฑ๏ธ Click-Based Selection - Left/right click for positions
๐พ Auto-Save - Regions automatically saved to config.yml
๐ Multi-World Support - Works in any world
๐ Permission Control - Granular permission system
๐ Production Ready - Fully tested and optimized
๐ฆ Self-Contained - No external dependencies needed
Creating a Region
/anticlaim wand # Get the wand
[Left-click a block] # Set Position 1
[Right-click a block] # Set Position 2
/anticlaim create spawn # Create region
Grant Permissions
/lp user <admin> permission set anticlaim.wand true
/lp user <admin> permission set anticlaim.create true
๐ฎ Commands
/anticlaim wand
/anticlaim create <name>
/anticlaim info
/anticlaim reload
๐ Requirements
Paper API or Spigot
GriefPrevention plugin
Java 17+
๐ Permissions
anticlaim.wand - Use the wand tool
anticlaim.create - Create regions
anticlaim.reload - Reload config
anticlaim.bypass - Bypass all restrictions
anticlaim.use - General command use
๐ Performance
Memory: Negligible usage
CPU: Minimal impact
Load Time: <1 second
Region Check: ~1ms per claim
๐ค Dependencies
Required:
Paper API 1.20.4+
GriefPrevention 16.18+
๐ฏ Use Cases
โ Prevent claims near spawn โ Create marketplace zones โ Setup public building areas โ Protect specific regions โ Allow free building in zones
Enjoy your wand-based region system! ๐
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:zglKCMXG:IHGCjSvz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zglKCMXG:IHGCjSvz"
}

