Tags
Creators
Details
0.9.2
Compatibility
Changes
[0.9.2] - Latest Release (It's all about the base)
This is a small patch that focuses on cleanup/QOL features and insuring everything works as intended. Due to how Skins are currently handled, the steve skin override falls back to using Alex/Steve skins depending on the player model, this will hopefully be handled better next update.
Added
- Cleaner version handling/project status handling: Project status and versioning are now handled dynamically
- The player will get notified if a newer version is available for the plugin
- Under the hood cleanup for dynamic project status display and project versioning/version checking
- Pre-discussion elimination notice: Eliminations are now announced as titles 10 seconds before teleporting to discussion
- Uses the MessageUtils title pipeline, matching other UI
- Applies blindness and heavy slowness during the 10s hold, cleared on teleport
- Works alongside seat teleports and discussion timers
- Nickname support: Voting papers, elimination titles, and hologram reveals now use display names with UUID-backed targeting to remain compatible with nick plugins (Dantizzle)
- Debug force start:
/matchbox debugstart <session>lets admins start a game with fewer than the configured minimum players (still enforces spawn/seat validity)
Fixed
- Steve skin override:
cosmetics.use-steve-skinsnow reapplies Steve skins for gameplay while restoring players’ original skins during discussion (no more partial overrides), currently falls back to Alex skin; will be fixed in the next update (Dantizzle) - Location listing clarity:
/matchbox listspawnsand/matchbox listseatspawnsnow display all configured entries and mark any with missing/not-loaded worlds instead of reporting none exist
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:umketzP5:kHRCnO58"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:umketzP5:kHRCnO58"
}

