Tags
Creators
Details
26.1.2.2
Compatibility
Required content
Changes
Debugify 26.1.2.2
Debugify now has a new versioning scheme!
It is now similar to the versioning scheme of NeoForge.
This version, 26.1.2.2, refers to 26.1.2 Minecraft version, build 2 of Debugify.
This change was made to make Debugify's version semantically parseable by Fabric.
Changes
- Move MC-136249 (Depth strider + riptide bug) to a gameplay fix, meaning it is disabled by default in multiplayer.
- Move MC-231097 (Release item after dropping bug) to a gameplay fix, meaning it is disabled by default in multiplayer.
Both of these fixes had been known to cause strict anti-cheats, such as the one found on minemen.club,
to ban users of Debugify.
As of this release, Debugify will no longer cause bans on minemen.club, as of this update, confirmed by dewgs.
Optional dependencies
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:QwxR6Gcd:AYdf2KSj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QwxR6Gcd:AYdf2KSj"
}


