1.20.6-0.4.2
Compatibility
Changes
I finally implemented two often requested features: the ability to restart your client without losing your shapes and support for NeoForge. It took a bit longer than I hoped due to a weird asynchronous classloading bug in Forge and some hiccups with getting NeoForge to cooperate, but I managed it!
New requirements are as follows:
- 1.17.1: Minecraft Forge 37.1.1, or Fabric Loader 0.16.2 and Fabric API 0.46.1.
- 1.18/1.18.1/1.18.2: Minecraft Forge 38.0.17, or Fabric Loader 0.16.2 and Fabric API 0.44.0.
- 1.19/1.19.1/1.19.2: Minecraft Forge 41.1.0, or Fabric Loader 0.16.2 and Fabric API 0.58.0.
- 1.19.3: Minecraft Forge 44.1.23, or Fabric Loader 0.16.2 and Fabric API 0.76.1.
- 1.19.4: Minecraft Forge 45.3.3, or Fabric Loader 0.16.2 and Fabric API 0.87.2.
- 1.20/1.20.1: Minecraft Forge 46.0.14, or Fabric Loader 0.16.2 and Fabric API 0.83.0.
- 1.20.2/1.20.3: Minecraft Forge 48.1.0, or Fabric Loader 0.16.2 and Fabric API 0.91.6.
- 1.20.4/1.20.5: Minecraft Forge 49.1.4, or Fabric Loader 0.16.2 and Fabric API 0.97.1.
- 1.20.6: Minecraft Forge 50.1.12, or Fabric Loader 0.16.2 and Fabric API 0.100.8.
- 1.21/1.21.1: Minecraft Forge 51.0.33, or Fabric Loader 0.16.2 and Fabric API 0.102.0, or NeoForge 21.0.167.
Added:
- Shapes can now persist by automatically saving them to a file. This is disabled by default due to some strange classloading issues under Minecraft Forge, but can be enabled in the config.
- NeoForge support for Minecraft 1.21 and up.
- Shape: Grid.
Fixed:
- Java versions on Fabric now allow versions greater than the supported version, like Java 22.
- Build Guide no longer pauses the game on some versions of Minecraft.
Removed:
- Support for 1.16.4 and 1.16.5 as Minecraft Forge no longer runs on the latest versions of Java.
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:XwBDibES:ItSlOgfF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XwBDibES:ItSlOgfF"
}

