You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the current game patches (such as "HRTF Sound", "Keep Camera Settings" etc. in SADX), each patch is stored in the profile JSON as a separate bool value, which requires handling each patch separately. Instead, I suggest storing a list of enabled patches as strings. This reduces the amount of code required to add new patches, especially on the Loader's side.
The new system on the Loader's side is ready to use, the section is called EnabledGamePatches. Example:
Another relevant thing I thought I should mention: we need to distinguish between game patches and patch-type codes, since both are called "patches". I suggest using "game patches" and "patch-type codes" to avoid confusion. I'll take care of this on the Loader's side.
With the current game patches (such as "HRTF Sound", "Keep Camera Settings" etc. in SADX), each patch is stored in the profile JSON as a separate bool value, which requires handling each patch separately. Instead, I suggest storing a list of enabled patches as strings. This reduces the amount of code required to add new patches, especially on the Loader's side.
The new system on the Loader's side is ready to use, the section is called
EnabledGamePatches
. Example:The text was updated successfully, but these errors were encountered: