Recaf operates in workspaces. Each workspace can have one or more files loaded at a time. The first file loaded will be marked as the primary resource. All following files are secondary resources. In addition to these two resources, there are two additional back-end resources that add functionality to Recaf.
Types of Resources
A primary resource contains all the class files and resources of the program you wish to modify.
Supported file types:
- Directories (Only accessible by workspace config file)
A secondary resource contains supporting class files and resources. They are for reference purposes and are used to improve support for the following features:
- Compiler classpath classes
- Context sensitive navigation
- Stack-frame generation.
You can add multiple secondary resources to a workspace. However, if you do not have access to the relevant secondary files, you can enable “Generate missing classes” in the Assembler config. This is supported via the Phantom Resource.
Supported file types:
- Directories _(Only accessible by workspace config file
The phantom resource is a hidden resource common to all workspaces. It is similar to the secondary resource in that it contains supporting class files. These classes are generated automatically by Recaf when you open a new workspace. Recaf uses the JPhantom library to analyze the primary resource of a workspace and generates missing references to classes, interfaces, enums, and all of their referenced fields and methods. The generated code only contains stubbed declarations, but that is all you need for a reference resource.
If the phantom generation process fails it will emit a message in the console. This is rarely the case except for certain intensely obfuscated programs. In this situation you may have to provide libraries as secondary resources to use some features.
In the config window under the “Assembler” tab it can be toggled with the setting “Generate missing classes”
The classpath resource is a hidden resource common to all workspaces. It allows Recaf to read class files directly from memory.
Creating a workspace
You can create a new workspace by selecting “File > Load”. This will show a file prompt where you can select the primary resource. Alternatively you can drag-and-drop a file onto the left-most panel.
Once the workspace is created with the primary resource you can add additional secondary resources with “File > Add library”.
All resources can have sources and JavaDocs attached as references. Right click on the resource and select which item you would like to attach. After attaching JavaDocs you can hover over a method to show a documentation popup.
Navigating the workspace
Considering the fact that Recaf supports multiple resources in a workspace there needs to be a way to navigate to the files of each resource. This is done by inserting a dropdown menu at the top of the navigation tree. In this menu the primary resource will be listed at the top and all additional libraries will be added below it. Selecting one of these items will replace the tree with the contents of that file.
Each resource’s navigation tree is persistent. This means that when a directory is opened it will stay open even after switching to another resource. When you switch back the tree will be just as it was before.
In order to quickly navigate to files it would be useful for there to be a filter. At the bottom of the navigation tree is a filter box. The content of the filter will show all tree items that contain the given path. For example
String will show the
String class in the navigation tree (Along with
StringBuilder since it contains
Exporting your changes
Before you export, make sure you have saved your changes. All editors can have their changes saved via the save keybind,
Control + S (default bind, can be changed). Saved changes are stored internally in Recaf until you export your changes.
To export your changes go to the “File” menu and select “Export program”. This will prompt you to give a file location to save the file to. This will export only the primary resource.
Exporting a workspace config
If you want to save the configured workspace go to the “File” menu and select “Export workspace”. This will prompt you to give a file location to save the workspace to. This will create a JSON file that holds references to each resource in the workspace. This JSON file can be used when loading a file (from either the menu prompt, or by drag-and-drop) to open all items in the workspace at once.
- Workspaces that use runtime components such as the attach function to connect to live processes cannot be exported to a JSON.
- You can modify the exported JSON to use point to directories instead of files. Change the
sourceto the directory containing classes you want to load.