Tags
Creators
Details
1.0.6.6
Compatibility
Changes
CS-Augmentations 1.0.6.6
Same description, we just changed our versioning scheme
Uh not sure whats even in this update, I remember we never released some content, it was never actual content though it was just experimental ideas I doubt it matters much but uh
This isn't a content update its just to let augmentation continue being in your worlds without nuking them, there will likely be a massive refactor on everything though so if your seeing this and want to try the mod, I'd probably wait instead, even if we don't make it for a few months since if you do get attached to your world it'll probably FUUCK everything up, maybe*
I forgot what happens when you aggressively change capabilities
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:l0Nan1uu:BVtAZksO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:l0Nan1uu:BVtAZksO"
}![[CS] Augmentations](https://cdn.modrinth.com/data/l0Nan1uu/84622ca4b5fb09112fd5902f12d2951f1644276a.png)

