1.3.0
Compatibility
Changes
What's New in 1.3.0 ποΈ Village Claiming System
/diplomacy claim <name> β Create your own village anywhere in the world! /diplomacy unclaim β Release your claimed village Configurable radius (16β128 blocks, default 48) Player-placed block tracking for custom village areas
π‘οΈ Guard Villagers Full Integration
Complete Guard Villagers mod compatibility Guards react to your village reputation upon entry with personalized messages Guards act as witnesses β earn extra reputation when you kill hostile mobs near them Configurable attack penalties (default -5) and kill penalties (default -100) for guards Witness bonus for mob kills near guards (default +3) New [guard_villagers] config section with 4 options
π¦ Quilt Loader Support
Now available for Quilt (Minecraft 1.20.1) Fabric jar is dual-compatible β works on both Fabric and Quilt loaders Seamless integration with your preferred modded environment
βοΈ New Configuration Options
enableEntryMessages β Toggle village entry/exit banners on or off [guard_villagers] section β attackGuard, killGuard, witnessBonus, welcomeMessage All penalties and bonuses now properly read from config files
π§Ή Code Optimization & Cleanup
Removed unused code, imports, and dead fields across the entire mod Added null safety annotations for cleaner builds Streamlined build scripts and removed legacy empty files Removed NeoForge module (not available for Minecraft 1.20.1) Updated .gitignore for professional repository structure
π Bug Fixes
Custom village names now display correctly in entry/exit messages Village detection radius no longer too large for custom claimed villages Guard attack/kill penalties now use config values instead of hardcoded numbers Fixed guardvillagers compatibility to use reflection (no compile-time dependency)
β Support the mod on Ko-fi! π’ Questions or suggestions? Leave a comment here or message me on Discord: Cesoti
This update is fully localized in English and Spanish.
Optional dependencies
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:nL13t6rJ:UJxoq0af"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nL13t6rJ:UJxoq0af"
}

