Tags
Creators
Details
All versions
1.4.0+mc26.1
Release
1.4.0 (26.1-26.2)3 months ago 23
Compatibility
Minecraft: Java Edition
26.3-snapshot-3
26.2
26.1.x
Platforms
Fabric
Quilt
Supported environments
Client-side
Required content
Any compatible version
Changes
1.4.0
Changes:
- Increased the Mappings format version to
4, which:- Does not break compatibility this time, because fv 2 and 3 mappings still load.
- Added more vanilla override actions for editing:
OVR_CUT,OVR_COPY,OVR_PASTE, andOVR_SELECT_ALL. - Added support for
strictmode (enabled when the optionalstrictboolean at the top level of the JSON is set to true) which throws exceptions to stop loading instead of logging warnings when the following recoverable errors occur:- There is a duplicate action registration (including conflicts between different actions)
- An unknown friendly keyname is specified
- An unknown action name is specified
- Action or system names have leading/trailing whitespace or have the wrong capitalization.
- Numbers that don't adhere to the RegEx
-?(0|[1-9]\d*)but would passInteger.parseInt()and therefore would be accepted not in strict mode.
- It is now a requirement that all builtin mappings load successfully in strict mode.
- Added a sharecode system for generating long encoded strings of mappings files that are easier to work with than raw JSON and the mod can automatically import for you.
- Added the following new builtin mappings sets:
builtin:emacs_windows_linux,builtin:emacs_mac, andbuiltin:readline. - Add the
/navmappings debug dumpDetailedActionsand/navmappings debug dumpMappingsStatesub-commands. - Improved the
/navmappings debug aboutCmdDeletesub-command’s generated text. - When you switch mappings, and your new 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 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. - 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. - Use a shorter description of the mod in its about info.
- Added automated testing for CMD + Delete.
- Internal code improvements.
Changes since RC 1:
- Fixed a bug where attempting to switch to mappings that were already active would fail.
- Internal code improvements.
Full changelog: https://github.com/Omegabird113/CMD_Delete/compare/1.3.1+mc26.1...1.4.0+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:R3kyz1jR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xrOWVab9:R3kyz1jR"
}

