StackDeobfuscator Mod Wiki
StackDeobfuscator Mod Wiki & Guide
wiki.9minecraft.net/stackdeobfuscator-mod/
When your game crashes, or if any error occurs within your game, information regarding these issues can be found as a text file crash report in the crash report folder or within the console. But the problem here is that these are basically unreadable. Trying to read a crash report can be confusing i
Guides
Step-by-step, in-game.
How to Read a Deobfuscated Crash Report with StackDeobfuscatorFind the Crash Report When Minecraft crashes with StackDeobfuscator installed, the crash report is written to the…How to Read Console Errors In-Game with StackDeobfuscatorOpen the Console Launch Minecraft with the console window visible (most launchers have a toggle for this).…How to Tell Which Mod Caused an Error Using StackDeobfuscatorRead the Stack Trace Open the crash report or console output. StackDeobfuscator has already replaced production names…How to Use StackDeobfuscator to Debug a Mod ConflictReproduce the Crash Launch the game with the mods you suspect conflict. Trigger the crash (load a world, open a menu,…
Frequently asked questions
How do I know StackDeobfuscator is actually working?
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.
Do I need to do anything to set up StackDeobfuscator after installing it?
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.
Where do I find the crash report after my game crashes?
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.
Why does my crash report still show class_ 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.