Links
Tags
Creators
Details
2.4.0
Compatibility
Required content
Changes
Support persistent working directory and Windows shell selection. ShellCommand: add getInitialWorkingDirectory, setWorkingDirectory and parseCommand to handle cd commands (including bare cd -> home), persist changes to config, and run cd without spawning a process. Use configured workingDirectory as ProcessBuilder.directory and honor a configurable windowsShell (cmd or powershell) when launching commands. Refactor saveCommandOutput to delegate to runCommandInternal. ModConfig: add workingDirectory and windowsShell fields. ModConfigScreen: add UI option to choose Windows shell.
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:d9Zeqv5x:zMUheJmq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:d9Zeqv5x:zMUheJmq"
}

