Tags
Creators
Details
1.10.1
Compatibility
Changes
What's New
Fixed
- Shaded-JAR JDBC driver discovery. H2 and MySQL Connector/J both ship a
META-INF/services/java.sql.Driverfile. The shade previously kept only H2's, verbatim and unrelocated, soServiceLoader-based driver discovery pointed at a class name that didn't exist in the JAR for H2, and was missing entirely for MySQL. The shade plugin now merges service files viaServicesResourceTransformerand relocates their contents; the shippedjava.sql.Driverentry lists both bundled drivers under their relocated names. - MySQL connections now use the bundled driver by design.
DatabaseManagersets HikariCP'sdriverClassNameexplicitly, so the pool loads the shaded Connector/J 9.7.0 instead of silently falling back throughDriverManagerto whatever MySQL driver the server platform happens to bundle. MySQL setups now get the pinned, attested driver version regardless of server flavor.
Changed
- JAR slimmed ~36% (7.7 MB → 4.9 MB). Excluded
protobuf-javaand Connector/J's X-protocol classes (com/mysql/cj/x/**) from the shade, both exist solely for the X DevAPI, which Oracle removed upstream in Connector/J 9.0, so they were dead code (~7.4 MB uncompressed). - No more unrelocated classes in the JAR.
org.slf4j(HikariCP's transitive dependency) is now relocated undercom.goobercraft.stormtrooperx.slf4jlike every other shaded dependency, eliminating a potential classpath conflict with other plugins or the server's own slf4j. Dependency metadata that survives shading uselessly (module-info.class,META-INF/maven/**,META-INF/versions/**,META-INF/native-image/**) is stripped.
Dependencies
- Bumped
me.clip:placeholderapifrom2.12.2to2.12.3(providedscope, soft dependency, not shaded into the JAR). - Bumped
org.junit.jupiter:junit-jupiterfrom6.1.0to6.1.2(test scope).
Upgrade Notes
If upgrading from 1.10.0: Drop-in replacement. No config schema change (config-version: 3 continues to apply, no migration runs), no permission changes, no command changes.
- H2 users (default): no behavior change, just a smaller download.
- MySQL users: connections now always use the plugin's bundled Connector/J 9.7.0. If your setup was unknowingly relying on the server's own bundled MySQL driver version, this release pins you to the attested one shipped in the JAR.
Server compatibility: Unchanged - Spigot, Paper, Purpur, and Folia 1.20.4+, on Minecraft 1.18 through 26.1.x, Java 17+.
JAR verification: Built and attested via GitHub Actions with Sigstore. Verify with gh attestation verify StormtrooperX-1.10.1.jar --repo GooberCraft/StormtrooperX (requires gh 2.43.0+).
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:x4scZzGn:uwuiOn57"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:x4scZzGn:uwuiOn57"
}

