mirror of
https://github.com/LumaTeam/Luma3DS.git
synced 2026-02-23 02:14:39 +00:00
fix indentation on options-and-usage
ihaveamac
parent
5f57a2c784
commit
50b47566e8
@ -30,30 +30,30 @@ A message can be displayed on the bottom screen when the PIN is being asked by p
|
||||
|
||||
- **New 3DS CPU**: Exclusive to **New 3DS** consoles.
|
||||
This allows you to configure the processor the same way NTR CFW does:
|
||||
- **Off** disables the patch.
|
||||
- **Clock** enables New 3DS clock speed for all games.
|
||||
- **L2** adds extra cache to the CPU _(Don't use this if your device crashes)_.
|
||||
- **Clock+L2** enables the N3DS clock speed and adds extra cache to the CPU. _(Pick **Clock** if your device crashes)_.
|
||||
- **Off** disables the patch.
|
||||
- **Clock** enables New 3DS clock speed for all games.
|
||||
- **L2** adds extra cache to the CPU _(Don't use this if your device crashes)_.
|
||||
- **Clock+L2** enables the N3DS clock speed and adds extra cache to the CPU. _(Pick **Clock** if your device crashes)_.
|
||||
|
||||
---
|
||||
|
||||
- **Autoboot SysNAND**: Determines if you want to boot **SysNAND** or **EmuNAND** by default (when **holding no buttons** on Luma3DS boot).
|
||||
- If the option is **on**, **holding L** boots **the default EmuNAND**.
|
||||
- If the option is **off**, **holding L** boots **SysNAND**.
|
||||
- If the option is **on**, **holding L** boots **the default EmuNAND**.
|
||||
- If the option is **off**, **holding L** boots **SysNAND**.
|
||||
|
||||
---
|
||||
|
||||
- **Use SysNAND FIRM if booting with R**:
|
||||
- **On**: uses the **FIRM from SysNAND** to boot EmuNAND **with R** (you usually can't boot a newer NAND with an older NATIVE_FIRM).
|
||||
- **Off**: uses the **FIRM from the default EmuNAND** to boot SysNAND **with R** (you usually can't boot a newer NAND with an older NATIVE_FIRM).
|
||||
- **On**: uses the **FIRM from SysNAND** to boot EmuNAND **with R** (you usually can't boot a newer NAND with an older NATIVE_FIRM).
|
||||
- **Off**: uses the **FIRM from the default EmuNAND** to boot SysNAND **with R** (you usually can't boot a newer NAND with an older NATIVE_FIRM).
|
||||
You can override the EmuNAND to take the FIRM from on boot by holding down a button on the **directional pad**, **Up**, **Right**, **Down**, **Left** for EmuNANDs 1, 2, 3 and 4 respectively.
|
||||
|
||||
---
|
||||
|
||||
- **Enable FIRMs and modules loading from SD**: If the option is **on**:
|
||||
- If present in the `luma` folder, one of `firmware.bin`, `firmware_twl.bin`, `firmware_agb` and `firmware_safe.bin` (depending on the firmware being launched) will be used instead of the one stored in CTRNAND.
|
||||
- If present in the `luma` folder, one of `firmware.bin`, `firmware_twl.bin`, `firmware_agb` and `firmware_safe.bin` (depending on the firmware being launched) will be used instead of the one stored in CTRNAND.
|
||||
If using NUS-encrypted FIRMs, a matching **cetk** file for each encrypted FIRM is needed (`/luma/cetk`, `/luma/cetk_twl`, `/luma/cetk_agb`, `/luma/cetk_safe` respectively).
|
||||
- If present in the `/luma/sysmodules` folder, standalone system modules will be loaded instead of the ones built-in to FIRM (not supported for SAFE_FIRM and NATIVE_FIRM versions older than 3.x).
|
||||
- If present in the `/luma/sysmodules` folder, standalone system modules will be loaded instead of the ones built-in to FIRM (not supported for SAFE_FIRM and NATIVE_FIRM versions older than 3.x).
|
||||
|
||||
---
|
||||
|
||||
@ -63,39 +63,39 @@ This path will be attempted on both SD and CTRNAND, and is also picked up if not
|
||||
---
|
||||
|
||||
- **Enable game patching**: Enables the following features:
|
||||
- The region/language emulation feature allows some games which need a specific language to be set to work, and **DLCs for foreign games** to load. To use it:
|
||||
- The region/language emulation feature allows some games which need a specific language to be set to work, and **DLCs for foreign games** to load. To use it:
|
||||
- Create a folder named **`titles`** inside `luma`.
|
||||
- Create a folder with the game's **title id** as the name (look them up on **www.3dsdb.com**) inside `titles`.
|
||||
- Create a file named **`locale.txt`** in the game's folder.
|
||||
- Inside the file,
|
||||
- Put **3 characters for the region** ("JPN", "USA", "EUR", "AUS", "CHN", "KOR", "TWN").
|
||||
- Put **an empty space**.
|
||||
- Put **2 characters for the language** ("JP", "EN", "FR", "DE", "IT", "ES", "ZH", "KO", "NL", "PT", "RU", "TW").
|
||||
- Put **3 characters for the region** ("JPN", "USA", "EUR", "AUS", "CHN", "KOR", "TWN").
|
||||
- Put **an empty space**.
|
||||
- Put **2 characters for the language** ("JP", "EN", "FR", "DE", "IT", "ES", "ZH", "KO", "NL", "PT", "RU", "TW").
|
||||
- For example, to play Pokémon™ Y in Japanese language and region:
|
||||
- Create `0004000000055E00/locale.txt`.
|
||||
- Put in `JPN JP`.
|
||||
- Save.
|
||||
- Create `0004000000055E00/locale.txt`.
|
||||
- Put in `JPN JP`.
|
||||
- Save.
|
||||
- The LayeredFS feature allows you to replace RomFS files with files on the SD card for most games. To use it:
|
||||
- Create a folder named **titles** inside `luma`.
|
||||
- Create a folder with the game's **title id** as the name (look them up on **www.3dsdb.com**) inside `titles`.
|
||||
- Create a folder called **`romfs`** in the game's folder.
|
||||
- Put the replacement files in the `romfs` folder.
|
||||
- For example, to use LayeredFS with Pokémon™ Y, make a folder named `romfs` , put your replacement files in it, then put `romfs` in `0004000000055E00`.
|
||||
- The external .code feature allows you to use patched binaries for games. To use it:
|
||||
- The external .code feature allows you to use patched binaries for games. To use it:
|
||||
- Create a folder named **titles** inside `luma`.
|
||||
- Create a folder with the game's **title id** as the name (look them up on **www.3dsdb.com**) inside `titles`.
|
||||
- Obtain a patched code.bin for the game, and rename it with game's **title id** as the file name (look them up on **www.3dsdb.com**).
|
||||
- For example, to use a patched binary with Pokémon™ Y, rename it to `code.bin` and put it in `0004000000055E00`.
|
||||
- The code IPS patching feature allows you to use IPS patches on a game's code. To use it:
|
||||
- Create a folder named **titles** inside `luma`.
|
||||
- Create a folder with the game's **title id** as the name (look them up on **www.3dsdb.com**) inside `titles`.
|
||||
- Obtain an IPS patch for the game, and rename it with game's **title id** as the file name (look them up on **www.3dsdb.com**).
|
||||
- For example, to use a patch with Pokémon™ Y, rename it to `code.ips` and put it in `0004000000055E00`.
|
||||
- Create a folder named **titles** inside `luma`.
|
||||
- Create a folder with the game's **title id** as the name (look them up on **www.3dsdb.com**) inside `titles`.
|
||||
- Obtain an IPS patch for the game, and rename it with game's **title id** as the file name (look them up on **www.3dsdb.com**).
|
||||
- For example, to use a patch with Pokémon™ Y, rename it to `code.ips` and put it in `0004000000055E00`.
|
||||
|
||||
---
|
||||
|
||||
- **Show NAND or user string in System Settings**: By default, this displays the current NAND/FIRM instead of "Ver." in System Settings.
|
||||
- The strings that can be shown are:
|
||||
- The strings that can be shown are:
|
||||
- **Sys**: **SysNAND** booted with with its own FIRM,
|
||||
- **Emu**: **first EmuNAND** booted with its own FIRM,
|
||||
- **EmuX** (where **X** can be **2**, **3** or **4**): **EmuNAND X** booted with its own FIRM,
|
||||
@ -103,7 +103,7 @@ This path will be attempted on both SD and CTRNAND, and is also picked up if not
|
||||
- **SyEX** (where **X** can be **2**, **3** or **4**): **SysNAND** booted with EmuNAND X's FIRM,
|
||||
- **EmuS**: **first EmuNAND** booted with **the SysNAND FIRM**,
|
||||
- **EmXS** (where **X** can be **2**, **3** or **4**): **EmuNAND X** booted with **the SysNAND FIRM**.
|
||||
- You can also display a custom version string for each NAND, by creating text files named `customversion_sys.txt`, `customversion_emu.txt`, `customversion_emu2.txt`, `customversion_emu3.txt` or `customversion_emu4.txt` inside `luma`.
|
||||
- You can also display a custom version string for each NAND, by creating text files named `customversion_sys.txt`, `customversion_emu.txt`, `customversion_emu2.txt`, `customversion_emu3.txt` or `customversion_emu4.txt` inside `luma`.
|
||||
The version strings can't exceed **39 characters**.
|
||||
|
||||
---
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user