Tags
Creators
Details
Licensed GPL-3.0-only
Published 8 months ago
All versions
1.6.0N-fabric
Release
journeymode-1.6.0N-fabric-1.21.12 months ago 10
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
🚀 Complete Mod Reconstruction & Porting
- Experimental Recovery & Revamp: Previous experimental builds of both NeoForge and Fabric were broken due to the introduction of a complex multi-module architecture. We have completely revamped and reconstructed both loader projects back from the
1.4.0codebase, which was the last verified stable build before introducing multi-module setups. - 100% Bug-Free Native JARs: Both the Fabric 1.21.1 and NeoForge 1.21.1 mods are now compiled natively and work perfectly without any runtime bugs or crashes.
- Native NBT Saved Data Persistence: User player data is no longer saved in an external JSON file. Progress and unlocks are persisted natively inside standard level NBT attachments, resolving server portability and synchronization issues.
- Fabric 1.21.1 Native Port: Fully implemented the Fabric version inside the
Fabric/directory with 100% feature-parity. - Enforced Gradle Mappings Isolation: Re-configured Gradle scripts to run official Mojang mappings (
mappings loom.officialMojangMappings()) natively alongside Fabric Loader0.19.2, ensuring perfect compile-time type-safety. - Safe Container Mixins: Ported screen mixins (
HandledScreenMixin.java) to inject cleanly on top ofAbstractContainerScreenin the Mojmap environment. - dimension-swap Immune Core: Fabric player unlock attachments utilize a robust static JVM map tracking handler inside
GlobalDataHandler.java, keeping player data fully safe across dimension boundaries or deaths without relying on heavy platform serialization systems.
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:OMRJLjO7:E7wBKQ57"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OMRJLjO7:E7wBKQ57"
}

