Tags
Creators
Details
5.8.0+fn-26.3
Compatibility
Changes
Technical API changes
To tackle issues like TheCSDev/betterstats#65, it has been made possible to instantiate TScreenWrapper<T> instances directly.
This resulted in a structural change where TScreen#createWrapperScreen() is not called immediately upon instantiation of a TScreen. Instead, a TScreen will receive its corresponding wrapper instance when either:
TScreen#getAsScreen()is called, or- A
TScreenWrapper<T>instance is manually instantiated for saidTScreen(ex.new TScreenWrapper<>(myTScreen)).
Therefore, TScreen#getAsScreen() is no longer "pure". If you happen to be a developer using this API, you should keep this in mind.
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:Eldc1g37:GVSkIJY4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Eldc1g37:GVSkIJY4"
}

