Tags
Creators
Details
Licensed GPL-3.0-only
Published last year
Updated 6 days ago
All versions
1.0.5
Release
UltimateWall 1.0.5 Region Update!6 days ago 16
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
- Added hollow square, cuboid, sphere, and cylinder wall shapes.
- Added persistent owned walls that are restored and protected after restart.
- Added region listing, renaming, deletion, and resizing.
- Added region owners, member roles, player allowlists, and permission-based allowlists.
- Added configurable wall lifetimes, lifetime renewal, and automatic expiry notifications.
- Added world exclusions for wall creation and protection.
- Added configurable protection for block placement, breaking, movement, entity movement, interactions, fluids, pistons, and explosions.
- Added region interaction protection. *Fixed overlapping-wall rejection and safe restoration that does not overwrite later block changes. *Fixed temporary walls remaining after shutdown and owned walls losing their protection after restart. *Fixed region and wall information checks across different worlds. *Fixed region records being lost when their worlds are unavailable. *Fixed placement items being spoofed by display name and missing wall-use permission checks. *Fixed invalid wall materials, shapes, sizes, flag values, and lifetime values from causing unexpected wall changes. *Fixed legacy persistent walls from replacing blocks that were present before the upgrade. *Fixed placement items disappearing when an inventory is full. *Fixed region names containing configuration path separators from corrupting saved data. *Fixed missing permission checks for wall information and region listings. *Fixed entity-pass settings and owned-wall removal permissions not applying correctly.
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:izdLgAIY:CcLnfakY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:izdLgAIY:CcLnfakY"
}

