1.0.4
Compatibility
Changes
πΉ Editor Copy/Paste Improvements Click directly on the grid to place your cursor exactly where you want it. Need to grab a full screen? Shift+Copy now selects all 8 ticks visible on screen at once β no more manual dragging.
π Update Notifications
Consoles and admins will now get notified automatically when a new release drops, so you're never caught off guard by an outdated build. Toggle this with update-check.enabled in your config. (Note: notifications will not appear on versions v1.0.3 or earlier!)
π¦ Simplified Build Versioning
Builds are now grouped by series (e.g. 1.20, 1.21, 26.1.2) instead of individual scattered numbers, making it way easier to track which build you're actually running.
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:AA4kD3X0:VmajZrKC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AA4kD3X0:VmajZrKC"
}

