Tags
Creators
Details
All versions
1.4.0-rc.1+mc26.1
Beta
1.4.0 Release Candidate 1 (26.1-26.2)3 months ago 16
Compatibility
Minecraft: Java Edition
26.2
26.1.x
Platforms
Fabric
Quilt
Supported environments
Client-side
Required content
Any compatible version
Changes
1.4.0 Release Candidate 1
Changes:
- When you switch mappings, and your previous mappings fail to load, the previously active mappings will be used instead of always switching to default mappings. This comes with other stability & robustness improvements to mappings switching.
- Added a
/navmappings debug dumpMappingsStatesub-command. - Added a hard-coded warning that the builtin mappings
emacs_mac,emacs_windows_linux, andreadlineare incomplete & not fully accurate emulates of those pieces of software. - Added a verbose logging mode which promotes
TRACE/DEBUGlevel logs toINFOfor inclusion inlatest.login all environments (especially for the vanilla launcher) for easier bug reports. This mode is only enabled if thecmd_delete.allowVerboseLogsJVM argument is set totrue. - Fixed a crash that would occur when exporting or importing sharecodes on Minecraft 26.1.2 or earlier (#24).
- Fixed a bug where exporting builtin mappings' sharecodes would not work outside of a development environment.
- Fixed a bug where custom mappings JSONs that inherited nothing wouldn't load.
- Added support for forcing CMD + Delete not to crash Minecraft on certain fatal exceptions by setting the
cmd_delete.forcePreventMinecraftCrashesJVM argument totrue. Note that this may allow for undefined behavior and/or illegal states after certain types of failures, so this mode is not recommended for normal use. - Internal code improvements.
Full changelog: https://github.com/Omegabird113/CMD_Delete/compare/1.4.0-beta.3+mc26.1...1.4.0-rc.1+mc26.1
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:xrOWVab9:fTGC2nhR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xrOWVab9:fTGC2nhR"
}

