Tags
Creators
Details
Licensed ARR
Published last year
Updated 3 days ago
All versions
2.0.1
Release
Machina Wards 2.0.15 months ago 84
Compatibility
Minecraft: Java Edition
1.21–1.21.8
Platforms
Paper
Purpur
Changes
MachinaWards Changelog
v2.1.0
- Minecraft 26.1 compatibility (Spigot, Paper, Purpur 26.1+)
- api-version updated to 26.1
- Sound resolution migrated to Registry.SOUNDS — existing config values unchanged
- getOfflinePlayer(String) deprecation resolved
v2.0.1
- Critical: Entry messages were never saved or loaded from the database
- High: Ward members could perform owner-only GUI actions (rename, flags, add/remove members, trust changes)
- Medium: Shop purchase silently consumed money if inventory was full — overflow now drops at player's feet
- Low: Pending rename/add-member chat state leaked on player disconnect
- Low: Breaking a ward block returned the raw material instead of the ward item
- Low: Remove notification used wrong config key (notify_on_add → notify_on_remove)
v2.0
- Trust level system (VISITOR / MEMBER) with per-member GUI management
- Ward Intelligence for Super Wards (creeper alert, mob kills, player death, explosion log)
- Full Adventure API integration (titles, action bars, hex color support)
- Ward flags: Allow PVP, Allow Mob Damage
- Extended protection: bucket pour, entity placement, vehicle destroy, block spread, spawner eggs (Purpur)
- Ward pickup via sneak+right-click with confirmation window
- Entry message per ward with color codes and placeholders
- Compass navigation, nearby ward listing, ownership transfer
- MySQL backend with SQLite→MySQL migration command
- Chunk-indexed spatial lookup, owner index, short ID index
- Particle task, configurable sounds, world/height restrictions
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:SX98EKcZ:8gGhtTv1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SX98EKcZ:8gGhtTv1"
}

