Links
Tags
Creators
Details
All versions
v1.3.6
Release
InsureInv 1.3.6-437bf57last month 25
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.1–1.20.6
Platforms
Folia
Paper
Purpur
Spigot
Changes
v1.3.6 — Spigot Support & MiniMessage Migration
🎉 Highlights
InsureInv now runs on Spigot, not just Paper and Folia. The messaging system has also been fully migrated to Adventure MiniMessage
✨ New Features
- Spigot compatibility — the plugin no longer rejects Spigot servers on startup.
- MiniMessage support across all plugin messages (console logs, command output, configured messages) for better text styling (gradients, hex colors, etc.).
- Add default-charge key and validation to avoid log spam.
🐛 Fixes
- Fixed a startup crash (
NoSuchMethodError) on Spigot caused by using a Paper-only plugin metadata API (getPluginMeta()); replaced with the cross-platformgetDescription()API. - Fixed missing Adventure dependencies (
adventure-api,adventure-text-minimessage) causingNoClassDefFoundErroron startup for servers without them bundled. BukkitAudiencesis now properly closed on plugin disable, preventing resource leaks across plugin reloads.
🔧 Internal / Build
- Added
adventure-platform-bukkit+BukkitAudiencesfor cross-platform Adventure support. - Removed the old i18n bundle (PDC-based + flattened YAML) in favor of a simpler, unified message system.
- Synced ShadowJar relocation paths with the
tech.qhuyy.insureinvpackage. - Added
run-paperGradle plugin for local testing against Minecraft 1.21.11. - Trimmed ShadowJar output size by excluding unnecessary
META-INFfiles.
⚠️ Notes
- This release is backward-compatible with existing Paper and Folia setups — no config changes needed for those platforms.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| InsureInv-1.3.6.jar | Sources jar | 160.91 KiB |
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:V8AkmJh1:GXuch36H"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:V8AkmJh1:GXuch36H"
}

