
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.4.0
Compatibility
Changes
1.4.0
- Added optional CraftEngine image support using the
<image:id>format. - Added CraftEngine
<shift:value>support for positioning images. - CraftEngine images are supported in configurable book text, mob images, and loot images.
- CraftEngine images are resolved before books open to preserve clickable tabs and navigation buttons.
- Added the optional
mob-details-layout-enabledlayout for servers using category mob lists. - The optional layout opens an image-only mob menu with separate STATS, DESCRIPTION, and LOOT pages.
- The optional layout mob menu displays the mob name above its image and removes the redundant image tooltip.
- Description pages display mob lore line by line, while loot pages display configured loot images and chances as a list.
- The optional layout keeps its three section buttons at the bottom of the mob image menu.
- The mob image menu includes a bottom-left button that returns to the current category mob list.
- STATS, DESCRIPTION, and LOOT pages show only their content and a button that returns to the mob image menu.
- Long DESCRIPTION content is automatically paginated while keeping the return button visible.
- STATS labels are now dynamic and can display any custom value configured with a matching key in category files.
- Legacy
health-label,damage-label, andabilities-labelbook fields are automatically migrated to their matching stat keys.
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:bq2Lr9gs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZP0eGPfi:bq2Lr9gs"
}
