
BlockSiege
BlockSiege is a Paper plugin focused on destructible block-based privates, configurable member management, and custom siege TNT. It combines territory protection, private durability, raid progression, and multilingual server support in one system.
Links
Tags
Creators
Details
1.0.1-Global
Compatibility
Changes
BlockSiege 1.0.1 — Compatibility Update
BlockSiege 1.0.1 is focused on compatibility, stability, and cleaner cross-core support.
This update continues the global rework introduced in 1.0.0 and makes the plugin more reliable across different server software and Minecraft versions.
What's new in 1.0.1 Improved platform compatibility
This version was prepared for wider support across Bukkit-compatible server software.
Supported software target:
Spigot
Paper
Purpur
Expanded Minecraft version support
This version is intended for:
Minecraft 1.20.5 - 1.21.11
Better API compatibility
Several parts of the codebase were adjusted to reduce dependency on Paper-specific behavior and improve compatibility with broader server implementations.
Stability improvements
fixed compatibility-related build issues
improved handling of version-sensitive API usage
cleaned up parts of the plugin for more reliable startup and runtime behavior
Safer release baseline
This update is designed as a cleaner and more universal base for future BlockSiege releases.
Main plugin features
block-based private system
private protection with PvP-only exception for outsiders
custom TNT system
private GUI
border display
private limits
destruction logging
anti-spam TNT protection
Notes
Folia is not supported yet
this version is aimed at standard Bukkit-compatible server cores
recommended for servers running modern 1.20.5+ environments
Short version for release card
1.0.1 is a compatibility-focused update for BlockSiege. This release improves support for Spigot, Paper and Purpur and targets Minecraft 1.20.5-1.21.11. It also includes API compatibility fixes, stability improvements, and cleanup for a more reliable release base.
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:YyF4kAlb:klwknQ4P"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YyF4kAlb:klwknQ4P"
}
