Tags
Creators
Details
2.0-BETA-FINAL
Compatibility
Changes
Castle Siege 2.0 BETA-FINAL Changelogs
We're excited to introduce the latest updates in Castle Siege 2.0 BETA-FINAL! This release brings a slew of new features, improvements, and fixes to enhance your gameplay experience.
New Features & Enhancements
- Leaderboard Placeholders: We've added three powerful placeholders for leaderboards:
%cs_top_10_wins%,%cs_top_10_kills%, and%cs_top_10_deaths%. Integrate them seamlessly with plugins like HolographicDisplays to showcase top players. - BossBar Support: By default, each arena now features a BossBar displaying the King's health. Easily toggle this feature on or off in
config.ymlto suit your server's preferences. - Customizable Arena Selector: Arena lore is now fully customizable, giving you greater control over the look and feel of your Castle Siege experience.
- New Placeholders: Two new placeholders are at your disposal –
%cs_arena_type%for arena type and%cs_kd%for player KDR, offering deeper stats integration. - Hardcore Mode Flexibility: Configure each arena independently with Hardcore mode (
hardcore:trueinarenas.yml). Players won't respawn in Hardcore mode, adding an extra layer of intensity.
Improvements & Fixes
- 1.21.5 Compatibility: We've ensured Castle Siege 2.0 BETA-3 works flawlessly on PaperMC 1.21.5 – tested and confirmed.
- Dependency Updates: Under-the-hood updates to keep everything running smoothly.
Important Note
Given the significant config changes, we recommend deleting config.yml, arenas.yml, and messages.yml and reconfiguring them to ensure all new features integrate properly.
What's Next?
This marks our BETA FINAL release. Upcoming updates will focus on performance optimizations and bug fixes, paving the way for the official 2.0 launch. Post-launch, we'll dive into exciting content updates – think kits featuring mobs like Ghasts for Attackers and Horses or Catapults for Defenders!
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:qciYBDg7:cqi7yN7E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qciYBDg7:cqi7yN7E"
}

