2.0
Compatibility
Changes
🛡️ EdBlocks
The ultimate automatic block remover for BoxPvP and practice servers.
EdBlocks is a powerful, flexible plugin designed to automatically remove blocks (like Cobblestone or End Stone) placed by players after a set time. Keep your arenas clean, reduce lag, and manage your server with powerful per-world and per-permission settings.
✨ Features
- Per-World Configuration: Don't settle for one-size-fits-all. Configure different block lists, removal times, and effects for
world_pvp,world_events, or any other world. - Permission-Based Times (VIPs!): Reward your players! Grant permissions like
edblocks.vipto make their blocks last longer than default players. - Custom Removal Effects: Add professional flair! Configure custom sounds and particles to play whenever a block is automatically removed.
- Full In-Game Management: No more editing config files! Manage the plugin live with easy-to-use commands.
- Full Tab Autocompletion: All commands, sub-commands, materials, and world names are fully tab-completed.
- WorldGuard Integration: Automatically ignores blocks placed inside excluded regions (like
spawnorshop). - High Performance: Optimized with
HashSetlookups for O(1) performance. It won't slow your server down.
💻 Commands & Permissions
All commands are grouped under /edb (alias /edblocks) and require the permission edblocks.admin.
/edb help: Shows the help menu./edb reload: Reloads the configuration./edb list [world]: Lists all tracked blocks for a world (ordefault)./edb add <Material> [world]: Adds a block to the removal list./edb remove <Material> [world]: Removes a block from the removal list.
🚀 Requirements & Installation
⚠️ Requirements
- Java 17 or newer
- Spigot / Paper 1.18+ (or any fork)
- Optional: WorldGuard & WorldEdit for region exclusion.
📦 Installation
- Stop your server.
- Drop the
EdBlocks-2.0.jarinto yourplugins/folder. - Start your server to generate the new
config.yml. - Stop the server again, configure the
config.yml(especially your worlds and blocks), then start it.
Updating from 1.x to 2.0?
This is a breaking change! Your old
config.ymlis not compatible.
- Delete your old
plugins/EdBlocksfolder.- Follow the fresh installation steps above.
- Manually copy your old block lists into the new
config.ymlformat.
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:2Vh8ZA6v:tDTHJXIY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2Vh8ZA6v:tDTHJXIY"
}

