Tags
Creators
Details
Licensed MIT
Created 4 years ago
Updated 3 months ago
All versions
3.0.0-beta-1
Beta
VillagerInfo 3.0.0-beta-13 years ago 124
Uploaded by
Compatibility
Minecraft: Java Edition
1.19.x
Platforms
Paper
Purpur
Changes
Please note, this rewrite is in beta, the config values are subject to change until the rewrite is taken out of beta.
What's changed
- Plugin has been re-written from the ground up
- Now calling events when checking info on villagers and zombie villagers, as well as spawning and removing the highlights - this allows for other plugins to cancel these events far easier, or hook into them as needed.
- Using BlockDisplays instead of FallingBlocks for highlighting workstations
- This allows for RGB color options on the glow color
- The color can be defined individually per block type
- Fixes an issue where the falling blocks would slide down even though they weren't supposed to
- locale messages are divided into 3 categories:
villager-information-messages- The messages you will see when you get the information from a villagerinsertion-messages- Messages that are inserted into other messagesserver-messages- Errors and server feedback
- Config options have been renamed to (hopefully) be more understandable
- Adds translation key support for the
Professionfield and theitemsin a Villager's inventory (Adopted from the PR to the original plugin - Reload command now has an option to reload the config or locale seperately
Current Permissions:
vill.info:
default:true
description: Allows the player to see the information from a villager using crouch-right-clickvill.reload.*:
description: Allows the Player to use /villreload to reload all the VillagerInfo configurationsvill.reload.locale:
default:op
description: Allows the Player to reload VillagerInfo's localevill.reload.config:
default:op
description: Allows the Player to reload VillagerInfo's config
Toggle command has not yet been re-implemented
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:cG2nJsSy:m1R8kBR5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cG2nJsSy:m1R8kBR5"
}

