Tags
Creators
Details
0.9.0+1.21.1-fabric
Compatibility
Required content
Changes
This update is mostly a project structure overhaul to reduce duplicate code between versions & simplify the build system, with the goal of reducing the effort needed to update & support many versions.
A result of this is that from now on the mod will be updated for all* minecraft versions since 1.16.5
*Specifically there are different jars for these versions:
| Version | Fabric | Forge* | NeoForge |
|---|---|---|---|
| 1.16.5 | ✔️ | ✔️ | |
| 1.17.x | ✔️ | ✔️ | |
| 1.18.2 | ✔️ | ✔️ | |
| 1.19.x | ✔️ | ✔️ | |
| 1.20.0/1 | ✔️ | ✔️ | |
| 1.20.2/3/4 | ✔️ | ✔️ | |
| 1.20.5/6 | ✔️ | ✔️ | |
| 1.21.0/1 | ✔️ | ✔️ | |
| 1.21.2/3 | ✔️ | ✔️ | |
| 1.21.4 | ✔️ | ✔️ |
*For now I am not supporting Forge on versions where NeoForge is available, this may change in the future depending on demand
Other than restructuring, there are also a handful of fixes/additions/improvements:
- Updated for 1.21.2+
- Added 1.17 support (previously skipped)
- Refactored input handling for better compatibility with mods that add keybinds related to movement (crawling, auto walk/run, third person mods, ItemSwapper+MouseWheelie)
- Movement config now has a section that lets you configure what keys are force updated by InvMove while in inventories (only the vanilla movement keys are enabled by default to keep it safer for mod compatibility) (before this it used to force update ALL keys which caused issues with some mods)
- Option to disable movement while the recipe book is open (false by default)
- Added a couple missing screens to vanilla module (hanging signs, smithing table, some loading screens)
- A couple existing fixes are now backported (notably
readUnrecognizedConfig/Class.forNamecrashes should be fixed)
NOTE: This version is not compatible with old versions of InvMoveCompats, you will need to update it to v0.4.0+
Optional dependencies
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:REfW2AEX:4q5KJDfw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:REfW2AEX:4q5KJDfw"
}

