1.1.0+neoforge-26.3
Compatibility
Changes
1.1.0
New Minecraft versions: 26.3, 26.2 and 26.1 – 26.1.2 on Fabric, Quilt and NeoForge, 26.1 – 26.2 on Forge (built against the unobfuscated game with Mojang names). Forge gains 1.21 – 1.21.11 as well. Paper/Spigot/Purpur, Folia, Velocity and BungeeCord builds cover 1.21.5 – 26.3, Sponge 1.21.5 – 26.2.
New commands
/tpa deny [player]– you can finally say no./tpa list– pending requests with time left./tpa toggle(on top ofenable/disable),/tpa reload,/tpa settingwith no arguments lists everything.- Aliases
/tpahere,/tpaccept,/tpdeny,/tpacancel. - Tab completion for every argument, including online players and pending senders.
Improvements
- Clickable [Accept] [Deny] buttons on Fabric, NeoForge, Forge 1.13+, Paper/Spigot, Folia and Sponge.
/tpa acceptwithout a name takes the newest request instead of the oldest.- Warmup is cancelled by any damage (
cancel-on-damage) and by moving one block (cancel-on-move), including changing dimension; both are configurable. messages.properties– every message can be customised, with&colour codes.- Magma blocks and campfires count as hazards; explicit permission denies from permission mods are respected.
- Settings are saved as soon as they change;
require-opwas renamedrequire-permission(old files still load).
Fixes
- Forge/NeoForge no longer lose all pending requests on
/reload, and now save on server stop. - Combat tagging on Fabric 1.17 – 1.19.3 no longer depends on an API that did not exist there.
- Colours were wrong on Forge 1.7.10.
- NeoForge 1.20.2 – 1.20.4 needed
mods.toml; it is now included. - Fabric 1.14/1.15 dimension lookups used an API from 1.16.
Builds
- Every Fabric/NeoForge/Forge jar is now compiled against the version range it claims (separate jars for 1.21–1.21.1, 1.21.2–1.21.4, 1.21.5, 1.21.6–1.21.8, 1.21.9–1.21.10, 1.21.11, 26.1.x, 26.2) instead of one jar pretending to cover everything; the Fabric 1.14–1.20.6 range is split the same way.
- Fabric jars run on Quilt as-is; the separate Quilt jars are gone.
- Jars are shrunk with ProGuard after compiling (unused code and debug info removed, private names shortened, maximum compression): ~30 KB per platform instead of ~41 KB, and the proxy companions are 2–3 KB.
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:2eBnbq9r:Rn1rwuzc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2eBnbq9r:Rn1rwuzc"
}

