Tags
Creators
Details
1.19.3+1.0
Compatibility
Required content
Changes
Updated to 1.19.3
New & improved Telemetry Fix
New telemetry menu in 1.19.3 allows you to set telemetry from Minimal to Full, Debugify adds a third option, off, that fully turns off and prevents Minecraft from connecting to Mojang telemetry services.
This also allows for a tooltip explaining each type of telemetry option.
Technical Details
Debugify adds another option in options.txt named debugifyTelemetry where
0 = off, 1 = minimal and 2 = full. Debugify internally sets the vanilla option
to minimal if off or minimal so if you delete Debugify you would not be defaulted
to full.
Options GUI improvements
You can now search for fixes using their descriptions as well as their bug ID.
'Server' fixes have been renamed to 'Main' fixes because previous wording was misleading that they only applied on a server.
'Main' and 'Client' are now categories instead of groups while 'Basic' and 'Gameplay' have taken their place as groups rather than categories. The gameplay warning and multiplayer toggle are mirrored in both categories.
Fix groups are now expanded by default.
New versioning system
Due to how intertwined Debugify is with Minecraft versions, starting 1.19.3, a new versioning
system for Debugify is being adopted. The version will reset on every Minecraft version bump, including
patches. An example version is 1.19.3+1.0, the major version will change when Debugify adds new fixes or
any significant changes to the mod itself happens, the minor version will change if Debugify makes any small
changes such as a bug fix or a text localisation update.
This has been made because the current system was very confusing and wasn't clear when there should ever be a major bump.
Removed bugs fixed in 1.19.3
| Bug ID | Name | Fixed in |
|---|---|---|
| MC-26757 | Large item tooltips can get cut off at the edges of the screen | 22w42a |
| MC-135973 | Can't hold Q to drop items rapidly from container inventories | 22w42a |
| MC-145748 | Clicking a settings button when there's a slider under the mouse in the next screen plays the click sound twice | 22w42a |
| MC-84873 | DeathTime values 20+ cause corrupted mobs | 22w43a |
| MC-147605 | Text cursors can exist in multiple fields | 22w46a |
| MC-151412 | "Edit Server Info" window does not focus "Server Name" text field automatically | 22w46a |
| MC-233042 | Server Address field isn't focused when Direct Connection menu is opened | 22w46a |
| MC-249059 | Loading terrain screen cannot close before 2 seconds have passed | 22w46a |
| MC-228976 | Entity collision is run on render thread | 1.19.3-pre3 |
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:l8A2i9nV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QwxR6Gcd:l8A2i9nV"
}


