Tags
Creators
Details
2.1.0-rc1
Compatibility
Changes
2.1.0 PLUGIN Release Candidate 1 for Java 1.13 - 1.21.10.
Compatible with Bukkit, Spigot, Paper, Purpur & Folia (EXPERIMENTAL)
Compatibility
- Verified compatibility with Folia (still experimental).
New Features
Modular Translation System
A complete replacement of the old Messages: block in config.yml.
- New folders:
/core/messages/origins/-> default language files/core/messages/custom/-> user overrides
- Automatic synchronization of missing keys.
- Supports:
- single messages
- lists (
lines:) - sections (
header:+lines:)
- Everything visible inside Minecraft is now translatable.
A legacy config warning will appear if the old Messages: section is still present.
Expansion System
VCT now supports first-party and custom expansions using a clean API.
- New commands:
/vct expansion info <id>/vct expansion enable <id>/vct expansion disable <id>/vct expansion reload <id>/vct expansion reloadall
- Expansions include metadata, help sections, and isolated configuration.
The new official VCT expansions are in the works, so stay tuned for our announcements! 👀
Improvements
- Major internal cleanup & refactor of the command system.
- Rewrote help menus to use the new translation structure.
- Unified message formatting across commands & expansions.
- Improved auto-updater messages and reduced duplicated logs.
- Improved structure of config loading for timers & core folders.
Bug fixes
- Fixed missing translation keys not being created on first load.
- Fixed issues with list-based translations showing incorrectly.
- Fixed rare startup errors caused by load order.
- Fixed multiple formatting inconsistencies across commands.
If you find a bug in this version, open an issue to let us know! ;)
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:N6N9gUha:5jIeBHMu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:N6N9gUha:5jIeBHMu"
}

