Tags
Creators
Details
1.0.3
Compatibility
Changes
๐ ๏ธ HAR Remaster (v1.0.3) - The Bugfix & Polish Update
This update brings critical bug fixes to the dimension routing system and adds much-needed polish to the hardcore experience. Updating to this version is highly recommended for all server owners.
โจ What's New & Improved
- Universal Seed Synchronization: When a new hardcore world is generated, the plugin now injects the exact same random master seed into the Overworld, Nether, and The End. This guarantees vanilla-like biome parity and structure generation across all 3 dimensions.
- Upgraded Boss Checklist: The
/checklistcommand UI has been visually improved! It now uses sleek green checkmarks (โ) and red crosses (โ) instead of generic question marks for better readability.
๐ Bug Fixes
- Fixed Dimension Portal Routing: Fixed a critical bug where building a Nether or End portal inside the hardcore world would incorrectly teleport players to the server's default lobby dimensions (
world_nether). Portals now correctly generate obsidian frames and forcefully route players into the properhc_world_netherandhc_world_the_enddimensions. - Fixed Lobby Invincibility Exploit: As a result of the portal fix, players can no longer become invincible or avoid world wipes by hiding in the lobby's nether.
- Fixed Timer Skipping on Admin Reset: Fixed a bug where using the
/h resetadmin command failed to wipe the internal timer. Previously, this caused the next run to completely skip the 10-second starting countdown and resume the old timer. - Fixed Dragon Victory Glitch: Fixed a glitch where defeating the Ender Dragon would instantly reset the timer to 0, which accidentally punished players with the 10-second lobby countdown (Slowness/Mining Fatigue) while they were still in The End trying to celebrate their victory.
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:hiX1phAJ:uD9lspTR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hiX1phAJ:uD9lspTR"
}

