Links
Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated 34 minutes ago
All versions
1.5.1
Release
LeashAll 1.5.134 minutes ago 1
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Server-side
Client and server
Required content
Any compatible version
Changes
LeashAll 1.5.1 (hotfix for NeoForge 26.3)
Fixed
- NeoForge 26.3.0.37-beta and later: the game no longer stops while mods are loading ("LeashAll (leashall) has failed to load correctly", NoSuchFieldError ... ModConfig$Type SERVER).
Changed
- NeoForge 26.3 now requires NeoForge 26.3.0.37-beta or newer (before: 26.3.0.0-beta). On an older 26.3 build NeoForge shows that the mod needs a newer NeoForge instead of crashing.
Unchanged
- Only the NeoForge 26.3 file changed. Fabric, Forge and the other NeoForge versions are the same as 1.5.0 apart from the version number.
- No gameplay changes: same leash rules and config options. Leashes saved in worlds keep working.
- Config stays in config/leashall-server.toml, so your settings still apply.
- LeashAll 1.5.0 and 1.5.1 servers and clients still work together.
Known behavior
- NeoForge itself now reads a per-world config copy from <world>/syncedconfig/ instead of <world>/serverconfig/ (this affects every mod). If you used such a copy, move it.
- NeoForge 26.3.0.48-beta and later need Architectury API 22.0.4 or newer: Architectury API 22.0.1 crashes at startup on those builds by itself, with or without this mod.
Compatibility (NeoForge 26.3)
| Minecraft | NeoForge | Architectury API |
|---|---|---|
| 26.3 | 26.3.0.37-beta+, below 26.4 | 22.0.1+ within 22.x; 22.0.4+ on NeoForge 26.3.0.48-beta+ |
All other versions' requirements are unchanged.
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:oKERV1Bi:xugJfP9i"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oKERV1Bi:xugJfP9i"
}

