1.3.0
Compatibility
Changes
Changelog All notable changes to the Hardcore Dynamic Maze mod will be documented in this file.
[1.3.0] - 2026-07-10 Added Maze Map System: Added a "Map" toggle switch to Page 1 of the Maze Control Panel. When enabled, players entering a maze will automatically receive a specialized Maze Map item that acts like a compass (displays a mini-map layout of the maze when held). The Maze Map is automatically cleared from the player's inventory upon leaving the maze boundaries. Enhanced Customization (Page 2): Added Center Room Size button (allows adjusting the center room dimensions between 3x3 and 20x20). Added Rooms Count button (allows adding up to 99 secondary rooms to the maze generator). GUI Restructuring (Page 4): Dedicated Page 4 added to the Maze Control Panel to house layout settings (Gui Scale, Background Opacity, Panel Width, Panel Height) to prevent main controls from being cramped. Fixed Wall & Floor Colors: Fixed an issue where the Wall Color and Floor Color options were ignored during maze generation, resulting in default white walls and blue floors. GUI Layout Crowding: Fixed crowded elements in the Maze Control Panel. Technical & Compatibility Full build support across 9 target platforms: Forge: 1.16.5, 1.18.2, 1.19.4, 1.20.1 Fabric: 1.16.5, 1.18.2, 1.19.4, 1.20.1 NeoForge: 1.20.1 Backported ClientHUD and rendering systems to older versions (using PoseStack/MatrixStack and GuiComponent/AbstractGui as appropriate per Minecraft version API). Implemented Mixin injection on LivingEntity for older Fabric targets (1.16.5 and 1.18.2) to support player damage/armor interactions and respawn hooks without depending on modern ServerLivingEntityEvents.
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:QxLWvwok:BBHEQrsT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QxLWvwok:BBHEQrsT"
}

