1.2
Compatibility
Changes
Changelog
All notable changes to VaultChatProvider will be documented here.
[1.2] — Initial Release
✨ Added
-
Added Vault Chat provider implementation.
-
Added support for custom prefixes.
-
Added support for custom suffixes.
-
Added configurable groups.
-
Added Vault integration for other plugins to retrieve:
- Player prefixes
- Player suffixes
- Player groups
-
Added configuration-based chat formatting.
-
Added standalone operation without requiring LuckPerms.
-
Added lightweight and simple configuration.
🔌 Integration
- Registers VaultChatProvider as the server's Vault Chat provider.
- Allows Vault-compatible plugins to retrieve chat-related player information.
📦 Compatibility
- Built for Paper servers.
- Requires Vault.
- No external permissions plugin is required.
Version: 1.2
Status: Initial Release
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:592QMg96:vuWznCa9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:592QMg96:vuWznCa9"
}

