All versions
0.1.1
Release
JupiterAdministration 1.16 months ago 90
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
[1.1] - 2026-04-13
Added
- Multi-Version Support:
- Expanded official support to include Java 21 and Java 25.
- Official compatibility mapping for Minecraft 1.21.x and 26.1x snapshots.
- Version Compatibility Layer:
- Introduced
VersionUtilfor dynamic, version-safe Material and Attribute resolution.
- Introduced
- SpearManager Functional: Formally integrated the Golden Spear feature into the plugin startup sequence.
Changed
- API Modernization: Refactored all
ItemStackinstantiations to the modernItemStack.of()factory method. - Java Target: Modernized build to target Java 21 while ensuring full compatibility with Java 25 via
<release>flags. - Dependency Update: Updated
maven-shade-pluginto3.6.2andmaven-compiler-pluginto3.13.0for improved future-bytecode support. - Missing Permissions: Defined missing permissions in
plugin.ymlforspawn.others,heal.others, etc.
Fixed
- Spawn & Home Commands: Resolved critical issues with location retrieval and teleportation logic that prevented
/spawnand/homefrom working correctly. - SpearManager Listener Leak: Resolved a performance bug in
/jupiter spearthat caused duplicate event listeners to be registered on every use. - NullPointerException Fix: Resolved a critical crash in Mining Intelligence when
JanusMCDwas not present on the server. - JanusBridge Stability: Implemented dynamic re-hooking via
PluginEnableEvent, allowing Jupiter to connect toJanusMCDeven if it's loaded late. - Invalid Command Error: Fixed structural issues in
plugin.ymlcaused by duplicate keys. - Offline Inventory: Fixed
OfflineInventoryReaderto correctly fallback to legacyplayerdataif the new 26.1 path is not found. - Heal Logic Modernization: Refactored
/healto use the newVersionUtilfor more robust attribute lookup across versions.
Usability
- Spawn Command: Added a
TabCompleterfor/spawn [player]and updated the usage string inplugin.ymlfor better discoverability.
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:YDjeZh9n:uzzRcWF7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YDjeZh9n:uzzRcWF7"
}

