0.3.16
Compatibility
Changes
0.3.16
A page could hang the server. A spacer that fills, in a card with padding, in a grid: the grid measures its cells against "no limit", the card took its padding off that, and the spacer read what was left as a real height — 268 million units. Encoding a rectangle that tall ran a recursion out of stack on the server thread, which stood still for ten seconds first. Found on a live client, on the first page that did it.
- "No limit" survives being handed through padding: anything within half of it still means "as much as you like".
- The encoder draws only what can be on the screen, whatever it is given, so no layout mistake can take the server down through it again.
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:K6cjpywA:L2HrnycS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:K6cjpywA:L2HrnycS"
}

