1.2.0
Compatibility
Changes
Fixes:
Fixed a bug with $cd when viewing folder where it only shows the current run folder instead of actual folder.
Additions:
Added "asplayer " command to the console to minecraft bridge
Added $config command and some config however it isn't finished yet
Added $run command, you can run a script that you add after it, it runs the script using whatever you set in $config script_command. Such as if "script_command" is "powershell.exe {path}" it replaces {path} with the script path specified.
Known bugs ⚠:
when doing the $run command it starts an instance of the script_command application. You must do $stop to get out of it.
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:wTTSpHBr:dHPWOw0a"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wTTSpHBr:dHPWOw0a"
}

