2.0
Compatibility
Changes
Craft CUBE Clash 2.0
Craft CUBE Clash 2.0 is a major rebuild of the original event plugin. The plugin has been rebuilt into a full event system for Minecraft PvP events with teams, custom cube arenas, event phases, combat handling, death bans, and a finale system.
Requirements
- Server Software: Paper
- Minecraft Version: 26.1.2
- Recommended Java Version: Java 25
- Optional Dependency: WorldEdit
WorldEdit is optional, but required if you want to paste team schematics automatically.
Main Features
- Full admin menu with
/cc - Planned
/adminalias - Automatic admin menu opening during setup
- Team creation and team management
- Custom team colors
- Team spawns and finale spawns
- Team schematic assignment
- Cube position generation
- WorldEdit schematic support
- Event phases: Setup, Lobby, Protection, Main Phase, Finale, Finished
- Automatic and manual phase control
- Bossbar with current phase and timer
- Lobby protection and lobby border
- No hostile mobs during setup and lobby
- PvP protection before the main phase
- Combat-tag system
- Combat-logging punishment
- Death-ban system
- Configurable ban durations
- Console unban commands
- Finale worldborder
- Winner detection
- Winner animation with titles, sounds, fireworks, and effects
- Automatic event ending after the winner is found
Version 2.0 Changes
Craft CUBE Clash 2.0 is not just a small update. The plugin was almost completely rebuilt.
The old basic event system has been replaced with a much larger and cleaner event structure. Admins can now control almost everything through menus, including teams, timers, cubes, schematics, combat settings, death bans, and finale options.
This version also adds a proper setup flow, where normal players can be blocked from joining before the event starts, while admins can prepare the event safely.
Notes
This is a Paper server plugin. Client-side menu changes, such as hiding the lower player inventory in chest menus, would require an additional NeoForge client mod and are not part of the Paper plugin itself.
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:VleGg66m:gH4LRQVf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VleGg66m:gH4LRQVf"
}

