Creators
Details
0.1.10-alpha
Compatibility
Changes
This alpha release aligns the public repository documentation with the current distribution state and makes the declared plugin command metadata match the active registration paths.
Changes
- Synchronized the repository status and contributor runtime documentation with the current public alpha state.
- Kept the standard contributor runtime independent of MySQL, with database-backed checks available through the explicit optional mode.
- Made
/treasureReloadthe canonical reload command while retaining/gameReloadas a compatible alias. - Removed stale metadata for
/gameand/givespecialemerald, which had no active registration path. - Removed the inactive
/dbstatusregistration from the unusedMySQLManagerconstructor. - Removed the redundant case-only
/gameStartalias. - Added a command metadata contract test covering command declarations, aliases, permissions, and Java
getCommand(...)references. - Synchronized the command reference with the verified plugin metadata.
The documentation synchronization was completed in #137, and the command-contract alignment was completed in #138.
Verification
./gradlew :test --tests plugin.PluginCommandMetadataContractTest --no-daemon --console=plain./gradlew clean build --no-daemon --console=plain- All required GitHub Actions checks for #138 completed successfully.
- The built JAR metadata was verified before runtime testing.
- Clean Spigot 1.20.1 startup and restart completed successfully with database mode disabled.
- Issue #23 / PR #93 Special Emerald implementation paths remained unchanged.
Release asset
TreasureRun-0.1.10-alpha-all.jar
Special thanks
-
eugabrixz on SpigotMC reviewed the first-time setup guide and found it clear all the way through, with easy-to-follow steps and no confusing assumptions.
-
Maintainer outcome: this review provided a clear basis for keeping the current guide unchanged.
Feedback thread: https://www.spigotmc.org/threads/quick-feedback-on-a-first-time-spigot-setup-guide.722125/
Scope
- No gameplay logic or round-state implementation changes are included.
- No i18n behavior, translation wording, or language-file changes are included.
- No ResourcePack content or delivery implementation changes are included.
- The unchanged ResourcePack remains pinned to the versioned
v0.1.9-alphaasset. - Issue #107 remains open as the ongoing player-message wording review tracker.
- The Community review credit records a documentation review and does not claim a completed external playtest.
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:druDRDrE:yyX6Mf5h"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:druDRDrE:yyX6Mf5h"
}

