Tags
Creators
Details
spigot-1.1
Compatibility
Changes
-
Rewritten from scratch.
-
Any (spigot) version before this is now marked as LEGACY. Villager hoppers and villagers should be converted automatically. For more details, check out: Updating from a legacy version
-
Picked up villagers are no longer “stored” by teleporting them under the world.
-
Picked up villagers’ NBT data is now written directly onto the item and retrieved when placing down. This will fix most performance issues that were apparent when using the legacy version.
-
Villagers can now be dispensed from dispensers (1.21+)
-
Picked up villagers now display certain property tags, such as owner, anchor and trading status.
-
A list of your trading partners will now be shown on the “Add Partner” button description.
-
Added separate “clickvillagers.place” permission for placing back villagers.
-
Overhauled messages:
- Use actionbar messages for common actions to avoid cluttering chat
- Villager hoppers have a more readable title
- Shorter button descriptions and more line breaks for readability
-
Added new particles and sound effects to almost every action.
- Picking up and placing back villagers has new particle and sound effects.
- Anchoring villagers has new particle and sound effects.
- Villager hoppers now have distinct placing/breaking sounds.
- Changing biomes have a new sound effect.
- Editing villagers now has a slightly lower pitch than the regular chest sound.
-
Added back buttons to submenus.
-
Fixed update checker. #23
-
Specify version when a new update is available.
-
Villager hoppers are no longer saved in a file, but the world itself.
-
Villager hoppers now only pick up villagers that are right above them.
-
Switched to JSON for messages and separate language files.
-
Switched to JSON for partner data.
-
Switched to ClickGUI for in-game menus.
-
Anchoring is made more consistent.
-
Rehauled configuration options:
- Removed “enable-x” config options, use permissions to disable features completely.
- Added a lot more configuration options, check “config.yml” in the plugins/ClickVillagers folder.
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:BITzwT7B:fLcvIQmJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BITzwT7B:fLcvIQmJ"
}

