Tags
Creators
Details
mc1.20-1.8.0-beta.4
Compatibility
Changes
1.8.0 Beta 4
In this Beta, the on/off state of the mod is saved in the per-world config. That means the on/off state will no longer reset after reloading the world, and changing the on/off state in one world will no longer affect other worlds.
The config is stored at <world root>/alternate-current.conf, and the on/off state is saved in the enabled entry. Setting its value to TRUE will turn Alternate Current on for that world, whereas FALSE will turn it off.
You can of course still change the on/off state with the /alternatecurrent command as well, and doing so will update that world's config.
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:r0v8vy1s:TGC7Ch3w"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:r0v8vy1s:TGC7Ch3w"
}

