1.2.0
Compatibility
Changes
Morrowless 1.2.0 — V3
Morrowless V3 expands survival equipment and quiet environmental storytelling while preserving the accepted atmosphere and tuning.
Equipment and shelter
- Six backpack tiers with inventory sidebar equipment, visible worn models, persistent storage and recoverable world bags after death.
- Plank Barricades with persistent damage and monster breaching.
- Ancient Shardstone, a decorative light block.
- Veil Hide armor, Veil Fray and Veil Hide monster drops, and vanilla recipe-unlock notifications.
- Boss reward maintenance: anvil repairs for the Drowned Scythe and Widow's Veil, including the Veil's durability and replenishable uses.
Atmosphere and encounters
- Regular-monster keepsakes and associated presentation details.
- Whispering Forests, unsettling animal behavior and small environmental vignettes.
- Faded Witness discovery polish and Catacombs generation adjustments.
- Veil Dawn's accepted subtle sunrise atmosphere.
Requirements and release status
- Minecraft 1.21.1, NeoForge 21.1.242 or newer for Minecraft 1.21.1, Java 21.
- Prepared version: 1.2.0 (V3). Not yet published.
- Feature scope is closed; accepted tuning, visuals and checkpoints are preserved.
Known validation limitations
- Real two-client multiplayer checks were not performed.
- Full Forest/Night Bell audio verification remains incomplete without
ffprobe; those blocked checks are not passes. - Veil Dawn's historical cancellation remains unexplained.
- The five accepted Veil Hide texture-rule failures remain unchanged; the combined verifier is not fully green.
These are accepted known limitations for preparation, not passed checks. See the V3 regression report for the reused results and their full scope, and the release preparation record for artifact provenance.
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:68pIDMKn:tAVkUGgJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:68pIDMKn:tAVkUGgJ"
}

