Tags
Creators
Details
Licensed MIT
Published 5 years ago
Updated 5 years ago
All versions
1.10.2-0.0.50.0
Alpha
CubicWorldGen-1.10.2-0.0.50.05 years ago 102
Compatibility
Minecraft: Java Edition
1.10.2
Platform
Forge
Supported environments
Server-side
Client and server
Changes
1.10.2-0.0.50.0:
- Fix incorrectly interpreting multilayer presets created with versions 31-32 (commit b37bb7ae3cba0ee369061b6a91227f5896babf16)
1.10.2-0.0.47.0:
- CC API: Post events added in CC API update in versions 895-899. Requires at least CC 899. (commit f663d73940c4031fdfe940a329949d2094c1e5a1)
- Save smaller CustomCubic preset string, allows to add more layers without running into vanilla 64kB preset size limit. Preset GUI shows more readable version of preset json. (commit 157604cf50fe4a8aadf382d438d689a15b9f2eaa, e99eaadf4bad6ece4b6abf6a9aaa4726e5bbb052)
- Internal changes for ForgeEssentials compatibility. Update to mixin 0.7.10. (commit 8ca569b18b2c4eae7889af739aeef7fa77bbdc12)
1.10.2-0.0.41.0:
- Fix attempting to generate mixin config file for farlands with the same name as cubic chunks. (commit bd0f0fb0a9217c77e3f59cad13ad930f0ae5d4f8)
1.10.2-0.0.38.0:
- First release - split from CubicChunks.
- Data fixers for preset. (commit d153594b647def5993083b6a795ef773e16c45c5, bcbf0f9d2c3d78517b750d82d1ff765189746b13)
- Config option to disable initial worldgen spawn. (commit 725be561f59e011f3ea499dc65f30b62f1fd9b45, by Foghrye4)
- Fix crash when customization text fiels is empty. (commit 643991430cde304a044a71bf32dfee7cc2ffe981, by Shad0wlife)
- Add farlands option in mixin config. (commit c511846a48e9528dac0aebd6a4e85e522b3d771e)
- Generate a single biome in FlatCubic. (commit 53d8e4e92f7dc156c2b4183ff8d0be0208bcd37d)
- Fix MalisisCore version in error screen. (commit dc2dde35b2f55a4fc163bdecc7f5fd78047d3f48)
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:ONVu3r1l:WTUXOJjT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ONVu3r1l:WTUXOJjT"
}

