All versions
1.2
Release
Altar S2 Arc1 13 months ago 185
Compatibility
Minecraft: Java Edition
1.21.x
Platform
Paper
Changes
AltarS2 Update Changelog
Altar Security & Reliability
- Fixed an exploit that allowed renamed armor stands to be used as fake altars.
- Legendary crafting now requires a genuine altar registered by the plugin.
- Crafting is blocked when the player's inventory is full, preventing ingredients or legendary weapons from being lost.
- Fixed altar cleanup potentially removing holograms or displays belonging to nearby altars.
- Crafted altars now remove their structure block correctly.
Dragonrend Recipe
- Updated the Dragonrend recipe to require:
- 32 Amethyst Clusters
- 64 Eyes of Ender
- 32 Crying Obsidian
- 1 Dragon Heart
- 3 Netherite Ingots
- Removed Trial Keys, Weapon Handle, Heavy Core, and Dragon Head from the recipe.
- The hologram, ingredient checks, and item consumption now use the same config-based recipe.
WorldGuard Support
- Added optional WorldGuard integration through
worldguard_supportinconfig.yml. - Altar placement and removal now respect region build permissions.
- Legendary attacks and abilities now respect region PvP settings.
/altars2 reloadnow properly refreshes WorldGuard support.- Fixed protected block breaks incorrectly removing altar entities.
Gameplay Fixes
- Ancient Blade progression now only counts player kills.
- Mob kills no longer level up the Ancient Blade.
Configuration
- Unified altar recipes under one config-based source of truth.
- Recipe holograms, missing-item messages, crafting checks, and ingredient consumption now remain synchronized.
- Invalid recipe materials now produce a clear console warning and safely prevent crafting instead of causing runtime errors.
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:2kffoBjh:Fc4T5zQZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2kffoBjh:Fc4T5zQZ"
}

