All versions
1.1.1
Release
AutoTorch! 1.1.16 days ago 10
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client-side
Required content
Any compatible version
Changes
AutoTorchSet 1.1.1
Changed
- Lower minimum loader versions: instead of the exact Fabric Loader, Fabric API, Forge and NeoForge builds the mod was compiled against, 1.1.1 asks only for the oldest build of each Minecraft line it works with (see the table below).
- Fabric 26.1.2 now requires Fabric Loader 0.19.5 or newer: the current Architectury API crashes the game at startup on older loaders.
Fixed
- Minecraft 1.21.11 on Forge and NeoForge: the log no longer shows "Couldn't load mod/autotorchset pack metadata" every time a world is loaded.
Unchanged
- Torch placement works under the same conditions as in 1.1.0.
- Same config file, key bindings and (Fabric) /autotorchset command.
- Same Minecraft versions and loaders: nothing added, nothing removed.
Compatibility
- Client-side only: a server does not need the mod.
- Fabric needs Fabric API and Architectury API, NeoForge needs Architectury API, Forge needs nothing but Forge.
| Minecraft | Fabric Loader | Fabric API | Architectury API (Fabric, NeoForge) | Forge | NeoForge |
|---|---|---|---|---|---|
| 1.19.2 | 0.14.9+ | 0.66.0+1.19.2 or newer | 6.6.92+, below 7 | 43.1.0+, below 44 | – |
| 1.20.1 | 0.14.21+ | 0.83.0+1.20.1 or newer | 9.2.14+, below 10 | 47.1.0+, below 48 | – |
| 1.21.1 | 0.15.11+ | 0.102.0+1.21.1 or newer | 13.0.11+, below 14 | 52.1.0+, below 53 | 21.1.1+, below 21.2 |
| 1.21.11 | 0.17.3+ | 0.139.4+1.21.11 or newer | 19.0.1+, below 20 | 61.1.0+, below 62 | 21.11.0-beta+, below 21.12 |
| 26.1.2 | 0.19.5+ | 0.154.0+26.1.2 or newer | 20.1.14+, below 21 | – | 26.1.2.99+, below 26.2 |
| 26.2 | 0.19.3+ | 0.154.0+26.2 or newer | 21.0.7+, below 22 | – | 26.2.0.40-beta+, below 26.3 |
| 26.3 | 0.19.5+ | 0.160.5+26.3 or newer | 22.0.1+, below 23 | – | 26.3.0.0-beta+, below 26.4 |
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:JPip03vS:QUkxd7kA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JPip03vS:QUkxd7kA"
}

