Links
Tags
Creators
Details
Licensed LGPL-3.0-or-later
Published 9 months ago
Updated 2 weeks ago
All versions
1.4.0
Release
Maze 1.4.0 - NeoForge 26.32 weeks ago 6
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog
All notable changes to the Hardcore Dynamic Maze mod will be documented in this file.
[1.4.0] - 2026-10-04
Added
- Fullscreen maze map: press N while carrying the enabled maze map inside a maze.
- Mouse wheel zoom, W/A/S/D panning, Space to reset the view, and N/Esc to close. The game continues while the map is open.
- Maze monsters are now named Minotaur, with a Piglin Brute body texture, a horned Ravager head, and a golden axe.
- Existing maze-tagged monsters are upgraded automatically. Maze settings, saved worlds, monster limits, and legacy command arguments remain compatible.
Fixed
- Numeric count fields remain visible in narrow controls. Max buttons collapse when space is limited; the smallest controls keep an editable number field.
- Replaced the per-frame maze block scan and individual block draw calls with a shared cached GPU texture.
- Map sampling checks loaded chunks only, runs at most once per game tick, and has a 1.5 ms / 4096-sample update budget. Completed snapshots refresh every five seconds.
- Previously explored areas remain visible when their chunks unload. Unexplored areas are gray, corridors dark blue, walls light, chests gold, and the player red.
- Removed duplicate legacy Forge client/HUD registrations and isolated client registration from dedicated servers.
Compatibility
- Updated all existing Fabric, Forge, and NeoForge source modules to mod version 1.4.0.
- Old modules now also have standalone Gradle settings, avoiding incompatible Loom versions in one build.
- Ordinary zombies retain their vanilla appearance and renderer.
Requires Minecraft 26.3 / neoforge.
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:6Mjy1lPj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QxLWvwok:6Mjy1lPj"
}

