StackDeobfuscator Mod FAQ

Trigger any error or crash and look at the console or crash report: if you see readable names like net.minecraft.client.MinecraftClient instead of net.minecraft.class_310, it's working. If names still look like class_123, the remapping didn't apply to that output.

No, it works automatically once installed. It hooks into the game's logging and crash handling so any error produced afterward is remapped without you running a command or opening a menu.

Look in the crash-reports folder inside your Minecraft instance directory, or read the same output directly in the console/log window. StackDeobfuscator remaps both, so either source will show readable names.

This usually means the crash happened before StackDeobfuscator loaded, or the report was generated by something outside the game's normal error path. Crashes that occur during very early startup may not get remapped.

It doesn't name the culprit directly, but it makes the stack trace readable so you can see which mod's classes appear in the error. Look for package names that match a mod's ID near the top of the trace.

It's designed for the client, where crash reports and console output are what you read. Server-side crash reports use a different obfuscation mapping, so remapping there isn't its focus.

No, it only acts when an error or crash is being logged, not during normal gameplay. There's no ongoing overhead while you're just playing.

It's generally compatible because it only touches logging and crash output rather than gameplay code. If another mod also rewrites stack traces, you might see double remapping or odd formatting, but crashes are rare.

Yes, that's one of its main uses. Read the remapped stack trace to see which mods' classes appear together in the error, then disable them one at a time to isolate the conflict.

It's still useful for regular players because it makes crash reports readable enough to search online or share in a support thread. You don't need to understand code to benefit from clearer names.