Toggle menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

RePatch reLoaded Vita: Difference between revisions

From GameBrew
m (HydeWing moved page Repatch Reloaded Vita to RePatch ReLoaded Vita without leaving a redirect)
m (HydeWing moved page RePatch ReLoaded Vita to RePatch reLoaded Vita without leaving a redirect)
(No difference)

Revision as of 06:27, 11 Ocak 2023

rePatch reLoaded
File:Repatchreloadedvita.jpg
General
AuthorSonicMastr
TypePlugins
Version1.2-Hotfix
LicenseMIT License
Last Updated2021/05/24
Links
Download
Source

RePatch reLoaded is a plugin that allows to redirect official game and homebrew data files in order to make it easier to mod and customize them.

Note: This is a full replacement for older rePatch installations and requires no changes to previous rePatch configurations to use.

What is rePatch reLoaded

This plugin serves as a substitute for the patch folder when an existing update is present on official cartridges or other encrypted formats. It also has the benefit of loading decrypted content on 3.60+. This includes newly added DLC and traditional modding.

ioPlus may be required.

To clarify: this plugin works on 3.60-3.68 on NoNpDrm, official cartridges, and officially downloaded games.

Note: Be wary of using a Vitamin dumped(or similar) eboot, it will be affected by save issues.

Usage

General Usage

  1. Install the plugin as any other kernel plugin, being sure to add it to the *KERNEL section of your config.txt.
  2. Create the folder ux0:rePatch
  3. Create a folder within the rePatch folder with the TITLE ID of the game you wish to patch.
  4. Place decrypted content within this TITLE ID folder. Exclude the sce_sys folder.
  5. You may delete overlapping files within the original patch folder or app folder to save space.

You should have 3 separate folders:

  1. An app folder for the original app. (Minus the ones that are being patched by rePatch)
  2. A patch folder to contain the official update/patch files. (Minus the ones that are being patched by rePatch)
  3. A rePatch folder which contains modified versions of files that were formally contained in app and patch

DLC Usage

  1. Create the folder: "ux0:reAddcont/<TITLE ID>"
  2. Place DECRYPTED content within this folder relating to DLC. This may include: DLC mods (similar to normal rePatch mods) or DLC decrypted/dumped by a pre-taihen dumper or Motoharu's tools.
  3. Please continue to the following sections pertaining to the subject you want.

DLC Decrypted Only

  1. Make sure that ux0:addcont/<TITLE ID> does not exist. This will make the game load from the rePatch addcont folder instead.
  2. Place completely decrypted content in: ux0:reAddcont/<TITLE ID>/<DLC ID> NOTE: You now may mod the DLC directly as you could with MAIDUMP or VITAMIN.

DLC Encrypted Only (Modding)

  1. Make sure that ux0:addcont/<TITLE ID> does exist and that you have encrypted DLC. This includes officially downloaded DLC along with NoNpDRM DLC.
  2. Place completely decrypted content in corresponding folder: ux0:reAddcont/<TITLE ID>/<DLC ID>
  3. You may delete overlapping files within the original addcont folder to save space. This works exactly like a rePatch patch.

DLC Encrypted + Decrypted

  1. Make sure that ux0:addcont/<TITLE ID> does exist and that you have encrypted DLC. This includes officially downloaded DLC along with NoNpDRM DLC.
  2. Place completely decrypted content in corresponding folder: ux0:reAddcont/<TITLE ID>/<DLC ID> NOTE: Modding still works in this mode.

How to Use for Homebrew

Homebrew application files can now be moved from ux0:app/TITLEID to YOUR_DESIRED_PARTITION:/rePatch/TITLEID, just like a normal game (eg. imc0:/rePatch/NXEV00001, uma0:/rePatch/NXEV00001). Just make sure not to delete eboot.bin and sce_sys from the original folder when saving space.

For extra homebrew data. Copy the required files from ux0:/data/ to YOUR_DESIRED_PARTITION:/reData/ (eg. ux0:/data/nxengine to uma0:/reData/nxengine). If the files aren't found in ux0:data/, rePatch will find the data in the folder you copied it to.

For the new ux0:data migration

Below will show you how to copy your homebrew data files from ux0:data to another partition.

It's actually extremely simple. Just copy the files from ux0:/data/ to YOUR_DESIRED_PARTITION:/reData/. That's it.

Example:

  • ux0:data/Sonic1/Data.rsdk -> imc0:reData/Sonic1/Data.rsdk or uma0:reData/Sonic1/Data.rsdk
  • ux0:data/RE3 -> imc0:reData/RE3 or uma0:reData/RE3

Once done copying files, simply delete the originals in ux0 and free up your space. 99% of homebrew that use that data will now default to the reData folder (Vitashell is exluded. Don't even try). If you ever want to go back, simply copy it back to ux0.

Media

Changelog

(v.1.2-fix)

  • This fixes the issues of certain homebrew causing a complete system crash and reboot. If you had issues with 1.2 in the past, use this one. It was an oversight.
  • Also added support for firmwares up to version 3.74

(v.1.2)

  • Fixed Redirecting Homebrew wouldn't work if the application used Directory Open/Close in addition to File Open/Close
  • OpenXcom and other homebrews that were affected by this should now work. Thanks to SKGleba for making me aware of this honestly stupid mistake

(v.1.0)

  • Full backwards compatibility with rePatch_4.skprx.
  • (Finally) Support for patching/moving homebrew app0: data to other partitions as long as a rePatch folder is present (ie. imc0:rePatch, uma0:rePatch)
  • Support for loading Homebrew data from other storage devices using reData folder (ie. imc0:reData/Sonic1/Data.rsdk, uma0:reData/Sonic1/Data.rsdk)

Other information

External links

Advertising: