> For the complete documentation index, see [llms.txt](https://docs.shrinefox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shrinefox.com/getting-started/persona-5-royal-switch-mod-support/manually-installing-switch-mods.md).

# Manually Installing Switch Mods

{% hint style="info" %}
This is an outdated method of installing mods, written before [Aemulus Package Manager](https://github.com/TekkaGB/AemulusModManager) was updated to support P5R Switch. These instructions are still included for those who rely on the original workflow.
{% endhint %}

Follow the steps on the [Persona 5 Royal (Switch) Mod Support page](/getting-started/persona-5-royal-switch-mod-support.md) to obtain the `ALL_USEU.CPK` and `PATCH1.CPK` files.

The game considers the root of each `.CPK` to be the same folder. `PATCH1.CPK` has higher load priority, since it's meant to override anything that needs to be updated. We can extract and then rebuild `PATCH1.CPK` with our modded files inside.

1. Download [`CriPakGUI-P5R.7z`](https://drive.google.com/file/d/1X9TPpQffaiqH-bFCedxO5gOqt1uw0U3a/view?usp=sharing) and extract with [7-zip](https://www.7-zip.org/).
2. Open `ALL_USEU.CPK` and click the **Extract Files** button to unpack the files to a folder.\
   The program may appear to freeze, this is normal. Please be patient as this can take a very long time. 
3. Do the same with the `PATCH1.CPK`.

{% hint style="warning" %}
You can think of `ALL_USEU.CPK` and `PATCH1.CPK` like zip folders. They are compressed, so once unpacked, the contents become much larger. The unpacked files end up being about 35 GB in total, so make sure you have enough space free on your hard drive.
{% endhint %}

1. Download and extract [`CpkMaker.zip`](https://drive.google.com/file/d/19RAhHnro19plJK53wAE02R5kFOfRA8Xq/view?usp=sharing) to the directory containing your unpacked `.CPK` folders.
2. Drag the `PATCH1.CPK_unpacked` folder onto `CPK.bat` to build a new `PATCH1.CPK` containing your modded files.
3. Transfer the new `PATCH1.CPK` to the directory matching your target platform.\
   Switch: `sdmc:/atmosphere/contents/01005CA01580E000/romfs/CPK`\
   RyujiNX: `/Ryujinx/mods/contents/01005CA01580E000/romfs/CPK`\
   Yuzu: `/yuzu/load/01005CA01580E000/ModName/romfs/CPK`

Be sure to match the directory structure of the extracted `.CPK`.\
On Switch, there's one extra thing to consider: the root of the `BASE.CPK` contains two folders, `BASE` and `EN`. But you can actually substitute either one with a folder called `PATCH1` and the files will still be loaded. For instance, if you're editing a file in the `ALL_USEU.CPK_unpacked/EN/INIT/` folder, copy it to your `PATCH1.CPK_unpacked/PATCH1/INIT` folder.

{% hint style="success" %}
Replacement files/folders can be uppercase or lowercase, it doesn't matter since the game loads them either way! Just make sure the `.CPK` filename is all uppercase.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.shrinefox.com/getting-started/persona-5-royal-switch-mod-support/manually-installing-switch-mods.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.