Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 4 months ago
All versions
1.1.1
Release
vJourney 1.1.15 months ago 22
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
Platforms
Paper
Purpur
Spigot
Changes
v1.1.1
- Storage: Added SQLite/MySQL player data storage using the same Paper
librariesapproach as vBestiary. SQLite stores data inplugins/vJourney/data/database.db. - Storage: Global first-completed announcement state is now stored in the database instead of
first_completed.yml. - Command: Added
/vjourney migrateto copy the active SQLite database data to the configured MySQL database, with localized aliases/tab completion forreloadandmigrate. - Config:
config.ymlnow uses inline comments and rewrites those comments in the configured language on reload without resetting current values. - Config: The bundled
exemple.ymlcategory is regenerated from the configured language template when the language changes on reload. - Compatibility: vBestiary triggers now use the English
categorykey, while the oldercategoriekey remains accepted as a compatibility alias. - Fix: PlaceholderAPI trigger and lore-refresh values are now resolved during the main-thread snapshot phase instead of the async evaluation phase.
- Fix: Advancement toasts are now emitted only on the actual grant action, preventing vBestiary/polling refreshes from showing a separate or repeated notification.
- Performance: Reduced duplicate enchant diff scans, filters command-based enchant snapshots by target player when possible, and made the first-completed announce cache thread-safe.
- Cleanup: Removed deprecated
ChatColor.stripColor()usage from enchant GUI title detection.
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:Z8gGL8iq:UM6isKqq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Z8gGL8iq:UM6isKqq"
}

