Update Creating Mods
@@ -29,7 +29,7 @@ The above commands will extract to the current working directory. All of the Wip
|
||||
For storing mods, Firestar uses the common ZIP format with the FSTAR file extension. The contents of the ZIP are dumped directly over top of the original assets at build time when the user selects "Deploy" and then psp2psarc is called to re-bundle the assets together.
|
||||
|
||||
### Patching Capabilities
|
||||
To solve mod conflicts, older versions of Firestar used a "delete.txt" file as shown above. Since version 1.3 this has been replaced by the [FScript patching system](Using-FScript). FScripts are run after a mod has been extracted and allow you to patch any file inside of the assets before the next mod is processed. This is useful if you want to modify part of a large file, without creating an entire copy of it that would overwrite any mods underneath it. FScript also natively supports using java-diff-utils to run diff patches, and includes binary editing capability. To learn more, please read [Using FScript](Using-FScript).
|
||||
To solve mod conflicts, Firestar uses the in-house [FScript patching system](Using-FScript). FScripts are run after a mod has been extracted and allow you to patch any file inside of the assets before the next mod is processed. This is useful if you want to modify part of a large file, without creating an entire copy of it that would overwrite any mods underneath it. FScript also natively supports using java-diff-utils to run diff patches, and includes binary editing capability. To learn more, please read [Using FScript](Using-FScript).
|
||||
|
||||
Firestar will execute the file named "fscript" at the root of your FSTAR package, if it exists.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user