Tags
Creators
Details
0.2.0
Compatibility
Changes
I THINK
I THINK EVERYTHING WORKS.
I would like to thank EazyVicx and TheSleepingCow for bringing these bugs up to me. They shouldn't be going on strike anymore.
- CuGO doesn't require itself to be on top of chests. If it is in range, the chest will open
- CuGO has (albeit barebones) overflow logic, specifically pertaining to items that you don't have storage for just yet. Might get stuck if it knows there's a compatible container but there's no space.
Looking for bugs & ideas. Report bugs to the GitHub, or report bugs & give ideas in the Discord. It only gets more complex from here, so I really need to know if the foundation is working nigh perfectly.
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:6mDL6SgG:oBcUsLX9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6mDL6SgG:oBcUsLX9"
}

