Content Patches
This page will show you how to make content patches. Content patches are fixes for games that change the game files in one way or another. You may be adding a missing asset, zipping a Legacy entry, adding a new version, removing unnecessary files, they are all content patches. Knowing how to curate is not necessary to understand this, but it highly recommended.
If you are looking to only edit metadata, see Metadata Edits. Logos and screenshots cannot be changed with content changes, see the previous link for those edits.
Preparation
First, you are going to need the new Installer build of Flashpoint, which can be downloaded here, or you can see the pinned messages in the #notification-squad channel of the Discord server. Run the installer, choose the components you want, extract it to where you want, and get Flashpoint running.
Open the config menu and toggle Enable Editing. This will enable the Curate menu and the context menu option of Make Curation From Game. Right clicking on any entry and selecting this option will either create a working curation in the Curate menu with all the metadata auto filled. If the entry is zipped, all the game files will copy into the content folder automatically. If the entry is still in the Legacy format, meaning it's files are still in Legacy\htdocs and not in a zip, the files will not automatically copy and you will have to do so manually for each file.
Zipped entries will automatically copy all of their files, so no additional work is needed gathering the files.
You cannot manually make a content patch from scratch. Make Curation From Game is necessary here as it gives the curation a flag specifying it is a content patch, which is needed when submitting!
Legacy Entries
As the game files will not copy over, you will have to manually add them to the curation's content folder. Run the game as normal and pay attention to the Logs tab. You will need to make sure you grab all files that is necessary for the game to run as intended, as long as all the files for any alternative applications the game may have. The game may call for files that are not necessary. If the game is single asset, you can just right click it and select Open File Location and grab the .swf from there.
Make sure that the folder structure of your launch command. For example, if you have the launch command http://localflash/redball/redball.swf then redball.swf needs to be in a folder called redball and that folder needs to be in a localflash folder. The main and alternative applications all need to follow this.
In your content folder, make all the necessary folders and add files, including any missing assets you may be adding. If all you are doing is zipping up a Legacy game, run it to make sure it works and Export.
Adding Files
Now it is time to make the actual patch part of your content patch. Add needed files, remove unnecessary files, change folders, whatever you want to do, just make sure that it works by running the game. If you are adding alternative applications, add their files and then add the alternative application and it's details. For more information on alternative applications, see the Curation Format page.
This content patch is zipping up a Legacy entry. This zip is also updating the launch command to include an extra 99blocks folder in the localflash folder, to follow the recommended curation formatting.
Metadata Edits
It is possible to include metadata edits with your content patch. However, because the launcher supports live, in-browser, and immediate metadata editing, you should only include metadata edits that are tied directly to your content patch. For example, if you are adding an alternative application that adds a version of the game in a different language, you can edit the language field to reflect this version. Another example, if a game is missing files, has the Partial status and mentions the missing files in the notes, and you are adding those missing files, you can change the status and remove the notes.
Tag and platform changes must be done as in-browser metadata changes, and not part of content patches.
Submitting
Content patches are submitted just like curations, at https://fpfss.unstable.life/web/submit. Export your patch out with the Export option. Upload the exported file, and it should successfully upload to FPFSS. If you made any metadata edits, specify every single edit you made in a comment or the patch's curation notes.
An example comment on a content change that zipped a Legacy entry, changed the launch command, added an html embed for the game, and removed notes. Mentioning file related changes is optional, but in this content patch the Notes were changed, this is a metadata change tied directly to the content patch, so it is necessary.
If you do not have the Trial Curator or Trial Editor role, you can only submit one content change until a staff member approves your first one, also known as an audition.