Repository navigation
Post‐Build Patches
they are all the patches applied AFTER generating a .cci file in Unity. This process disassembles the .cci file, superficially modifies the RSF file, and then repackages everything into a .cia file, establishing additional settings not present in Unity by default.
This is where you (optionally) should set the URL and API key of the RID small API; it's this one, so you don't have to struggle much searching: https://rid-system.onrender.com
The API key is also optional; for now, there's no way to obtain it, so your titleid will be added to the database manually by our team.
If you press the "Get Random TitleID" button, rid-tools will generate a new titleid randomly for you to use and it will be applied to the project automatically (check the playersettings to verify this).
This panel contains the main settings to apply to your entire project.
- AutoCIA: Automatically creates a functional .cia file ready to install on any Nintendo 3DS family console without needing developer mode (unlike Unity's .cia file, which only works on developer consoles like the 3DS Panda).
There are two variations of this setting:
- Patches
- No Patches (WARNING! This mode requires a copy of your console's boot9.bin file to work).
Currently, it appears you can select both simultaneously, and technically that's correct. You can create one CIA file without patches and another with patches at the same time, but it's recommended to choose only one.
Patches include all other applied settings, such as system modes.
RID-Tools can force the use of different SystemModes in your old3ds app. Some of these are:
- 64MB
- 96MB (Crashes instantly)
- 80MB
- 72MB
- 32MB
Objectively, only the 72MB and 80MB modes are worth using, since Unity already uses the 64MB mode, and the other modes will likely just cause crashes because they don't allow your app to use the additional memory Unity requires.
Post-build patches REQUIRE a .cci file to disassemble, modify, and repackage, as well as a path to save the resulting .cia file.
If neither a .cci file nor a location for the .cia file is selected, an error will simply occur.
When the AutoCIA patcher is activated, the paths for both the .cci and .cia files will be automatically updated to the same path where Unity finished compiling.
These are a series of specific settings for the New 3DS; they only work on a New 3DS for obvious reasons (the Old 3DS doesn't have them, haha). They can be quite useful for squeezing out a little extra power.
The New 3DS only has three additional system modes beyond the default settings of the Old 3DS:
-
Legacy: This uses the same memory mode as the Old 3DS. It should be able to "emulate" an Old 3DS from a New 3DS, but it probably won't do anything at all.
-
128MB: This is the New 3DS's default mode. All New 3DS apps run in this mode.
-
178MB: This is the New 3DS's extended memory mode. It's the maximum amount of memory an app can access, but unfortunately, it crashes instantly.
Finally, regarding post-build patches, we have the additional settings. These have self-explanatory names, but I must admit that the only truly useful one is F. Compress StaticMem, as it forces memory compression, freeing up more space for additional features.
As a final step, you must save your configuration so it can be applied.
You can submit your titleID to be reviewed and added to the RID API.
"Create CIA from CCI" requires a copy of your console's boot9.bin file in /Assets/Editor/RID-Tools/ExtTools/boot9/boot9.bin, This button does NOT apply any patches; it only converts your .cci file to .cia, just like your console would using godmode9.
With Make CIA With Patches, you don't need your console's boot9.bin file, just the .cci file where you apply the patches, and that's it (it doesn't necessarily have to be from your project xdxd). This will APPLY each and every PATCH that YOU have chosen and saved. Remember to always save; if you don't save your patches, they will not be applied.
