2.2
Compatibility
Changes
CraftCubeClash 2.2 — Finale Overhaul, Cube Security & Admin Improvements
CraftCubeClash 2.2 is a major gameplay and administration update focused on making the finale more tactical, improving team-cube security without restricting legitimate raids, and making event recovery and management much easier.
🏆 Finale Overhaul
-
Team beds now control finale respawns
- Each team receives a designated bed near its colored finale spawn.
- As long as the team's bed is still intact, players respawn at their team's finale spawn after dying.
- Once the bed has been destroyed, the next death eliminates that player from the finale.
- Teams cannot destroy their own finale bed, but enemy teams can.
-
Removed automatic void rescue
- Falling from the finale island now results in a normal death.
- Whether the player respawns or is eliminated is determined by their team's bed.
-
Protected the original finale island
- Blocks that belong to the original main-island schematic can no longer be mined or destroyed during the finale.
- Players can still place new blocks during the finale.
- Blocks placed by players remain breakable.
- This prevents the original arena itself from being dismantled while still allowing normal building and PvP.
-
Added
/cc revive <player|UUID>- Admins can restore a player who was eliminated because of a bug or incorrect event state.
- The command removes the finale elimination state and matching event ban.
- The player is restored to Survival mode and returned to their real team finale spawn.
- If a winner countdown had already started because of the incorrect elimination, the finale can be reopened safely.
🧊 Team Cube Anti-Exploit Protection
Team cubes remain fully raid-able through legitimate gameplay. There is no invisible wall around a cube.
Players may still:
- enter through an open door,
- break or blow open an entrance,
- create a legitimate breach,
- fight and build normally inside enemy cubes.
The new protections only target exploits that bypass the cube shell.
Ender Pearl protection
- Ender Pearls can no longer be used to clip through closed walls, doors, Bedrock shells, or other sealed parts of an enemy cube.
- Teleports into a foreign cube are checked for a genuinely passable route to the outside.
- Legitimately opened entrances remain usable.
Chorus Fruit protection
- Chorus Fruit remains usable normally.
- It can no longer teleport a player through the sealed shell of an enemy team cube.
- Legitimately accessible areas inside a cube are still valid.
Pearl Stasis Stations
- Pearl stasis chambers using bubble columns and trapdoors are supported again.
- When an Ender Pearl actually hits the trapdoor of a stasis chamber, only that exact trapdoor is ignored for the teleport collision check.
- Other solid blocks remain protected against pearl clipping.
- The trapdoor exception cannot be used to bypass a sealed enemy cube.
Bedrock protection
Bedrock belonging to a pasted team-cube schematic receives additional protection against known Bedrock-breaking techniques.
Protected cube Bedrock cannot be removed through:
- direct block breaking,
- explosions,
- piston manipulation,
- TNT/piston Bedrock-breaking setups,
- entity or block mutation events.
Other blocks inside team cubes remain normally attackable.
👥 Player Pool Improvements
- The player pool can now be edited even after the initial setup has been completed.
- Players can be added or removed through the
/ccadministration menus without rebuilding the event. - Team assignments can then be adjusted normally.
This makes last-minute player corrections much easier and avoids having to manually edit server files.
🍗 Lobby Improvements
- Players no longer lose hunger during the lobby phase.
- Food level is kept at full and saturation is automatically maintained while waiting for the event to start.
📦 Base Chunk Loading
- Base chunk plugin tickets are now reinforced every 30 seconds.
- This helps keep configured team bases and their farms loaded reliably.
/cc statusnow exposes the number of active base chunk tickets for easier diagnostics.
💾 More Readable Storage Files
Player-related UUID entries are now written together with their player name where possible.
Example:
6153d8d7-8c78-4765-8924-093b4a58da07 | PlayerName
This makes files such as team, finale, and ban data significantly easier to inspect and repair manually.
🔧 Additional Fixes
- Events configured without team-cube schematics no longer fail phase validation because of a
0/0cube state. - Existing start-flight privacy, combat-tag death attribution, private team guidance, player-pool access protection, Crystal PvP settings, End locking, and finale safety systems remain active.
- Test-server Gradle deployment no longer attempts to track mutable runtime plugin files.
Requirements
- Minecraft / Paper: 26.1.2
- Java: 25
- WorldEdit: Required when using schematic-based islands or team cubes
- Client mod: Not required
CraftCubeClash 2.2 keeps normal Survival and PvP gameplay open while moving exploit prevention and event recovery into more targeted server-side systems.
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:CEJEcIZg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VleGg66m:CEJEcIZg"
}

