Tags
Creators
Details
0.1.2.2-pre-alpha17
Compatibility
Changes
Pre-Alpha-Release 17 - 0.1.2.2
This is still half of the Alpha-Release 17 - 0.1.3. This update only fix the Java classes in preparation for the 0.1.3.
Additions
- A GitHub Repositories
- In the .jar file, there's now 4 new sub-files :
- README.md
- LICENSE.md
- NOTICE.md - Currently, this file is blank. The content in this file will be added in 0.1.3.
- CHANGELOG.md
Changes
- We're leaving MCreator
Fixes
- Fixed all the classes added in the previous update, as they weren't compiled correctly in the .jar file. They still were presents as .java files and not as .class files.
Next Update
The next update will be custom Copycat blocks, working like FramedBlocks or Create: Copycats.
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:f2eLUpug:uUfd60CW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:f2eLUpug:uUfd60CW"
}

