
vBestiary
Create an immersive bestiary system for your server. Players unlock creatures by defeating them, allowing them to view mob stats, drop tables, and detailed information as they progress. Fully compatible with custom mobs through MythicMobs support.
Tags
Creators
Details
1.1.2
Compatibility
Changes
1.1.2
- Replaced the old YAML progress storage with SQL storage.
- Added SQLite as the default progress storage backend.
- Added optional MySQL storage for servers that want external database storage.
- Added a shared SQL storage layer using HikariCP.
- SQLite now stores the database and WAL/SHM sidecar files inside the
data/folder. - Aligned the database configuration block with the standard vPlugins
database:format. - Added configurable MySQL pool size.
- Added an admin command to migrate progress data from SQLite to MySQL.
- Improved async progress loading error handling.
- Progression categories now stay hidden from the index until the player discovers the first mob in that category.
- Added a category unlock notification for the first discovered mob in a progression category.
- Database libraries are loaded through the server library loader to keep the plugin jar small.
1.1.1
- Added a public vBestiary API for external plugin integrations.
- Added API access to discovered mob counts, total configured mobs, discovered mob IDs, specific mob discovery checks, and category completion checks.
- Added support for the
anycategory selector in the API so integrations can read progress across all categories. - Prepared the API for optional integrations such as vJourney achievements without making vBestiary a required dependency.
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:ZP0eGPfi:MVCcrl0h"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZP0eGPfi:MVCcrl0h"
}
