Minecraft-Deobfuscator3000

Deobfuscator3000 is a Java-based universal tool for deobfuscating Minecraft mods. It can decompile and deobfuscate your mod jar in one workflow, using user-specified obfuscation mappings. To use it, you first provide the appropriate mappings (excel/csv format) for the target Minecraft version, then point the tool to your mod jar (or zip). The deobfuscator will process the files and output a deobfuscated source tree alongside the original artifacts. The workflow supports both full mod deobfuscation and per-file deobfuscation, making it suitable for mods with missing sources or for reverse-engineering purposes. You’ll typically interact with a UI or CLI to select mappings and the mod package, then trigger the deobfuscation operation and wait for the results to appear in the output folder.

Prerequisites:

• Java Runtime Environment (JRE) or JDK installed on your system.
• Access to the Deobfuscator3000 JAR file (e.g., Deobfuscator3000.jar).

Installation steps:

1. Install Java:
   • Windows/macOS/Linux: download and install a supported JRE/JDK from Oracle/OpenJDK.
2. Obtain Deobfuscator3000:
   • Download Deobfuscator3000.jar from the official source.
3. Prepare mappings:
   • Acquire the deobfuscation mappings for your target Minecraft version (excel/csv format) as described in the project docs.
4. Run the application:
   • Open a terminal/command prompt and execute the server/jar: java -jar Deobfuscator3000.jar
5. Provide inputs:
   • In the UI or CLI, set the path to the mappings folder or file and the path to your mod jar/zip, then click or initialize the deobfuscation process.

Optional:

• If you need to automate the run, you can use the mcp_config entry to start the server with the appropriate command and arguments.

Tips and common issues:

• Ensure mappings correspond to the same Minecraft version as your mod; mismatched mappings are a common cause of incomplete deobfuscation.
• The tool may unzip jar files and modify files on disk during processing; you may see changed extensions or new folders created in the output path. If you suspect antivirus interference, consider adding the Deobfuscator3000 directory to scan exceptions or temporarily disabling real-time protection during processing.
• If the deobfuscation result appears incorrect, re-check the mappings and ensure you selected the correct mod jar and mapping set for the target version.
• The output will typically appear in the same folder as the original mod jar or in a designated output directory, depending on the run configuration.