Submission Testing Instructions - Revision history

RockoRotten: Added a rule under "Tags" concerning the Other tag's usage.

2025-04-14T22:05:31Z

Added a rule under "Tags" concerning the Other tag's usage.

← Older revision		Revision as of 00:05, 15 April 2025
Line 53:		Line 53:
	* The curation has no Gameplay (or Animation) Tags or if the Gameplay tags it has are incorrect.		* The curation has no Gameplay (or Animation) Tags or if the Gameplay tags it has are incorrect.
	* The tag is no longer used, e.g. <code>LEGACY-Extreme</code>, <code>Find</code>, <code>Unusual Input</code>. These tags should not be added to any new submissions.		* The tag is no longer used, e.g. <code>LEGACY-Extreme</code>, <code>Find</code>, <code>Unusual Input</code>. These tags should not be added to any new submissions.
			* The <code>Other</code> tag is present along with other gameplay tags.
	This section is '''not relevant''' if you're testing content patches since they are unable to change tags.		This section is '''not relevant''' if you're testing content patches since they are unable to change tags.
	\|-		\|-

Cursed-light: Added content patches inability to change tags and platforms to the respective fields

2024-10-26T11:24:10Z

Added content patches inability to change tags and platforms to the respective fields

← Older revision		Revision as of 13:24, 26 October 2024
Line 53:		Line 53:
	* The curation has no Gameplay (or Animation) Tags or if the Gameplay tags it has are incorrect.		* The curation has no Gameplay (or Animation) Tags or if the Gameplay tags it has are incorrect.
	* The tag is no longer used, e.g. <code>LEGACY-Extreme</code>, <code>Find</code>, <code>Unusual Input</code>. These tags should not be added to any new submissions.		* The tag is no longer used, e.g. <code>LEGACY-Extreme</code>, <code>Find</code>, <code>Unusual Input</code>. These tags should not be added to any new submissions.
			This section is '''not relevant''' if you're testing content patches since they are unable to change tags.
	\|-		\|-
	\| '''Play Mode'''		\| '''Play Mode'''
Line 79:		Line 80:
	\| '''Platform'''		\| '''Platform'''
	\| Changes should be requested if this field is incorrect. For information specific to each Platform go to [[#Platform Specific Requirements\|Platform Specific Requirements]].		\| Changes should be requested if this field is incorrect. For information specific to each Platform go to [[#Platform Specific Requirements\|Platform Specific Requirements]].
			This section is '''not relevant''' if you're testing content patches since they are unable to change the platform.
	\|-		\|-
	\| '''Application Path'''		\| '''Application Path'''

RockoRotten: Bolded some words in the Using FPFSS section, added a bit in the Notes section about the Broken Feature tag.

2024-08-19T14:53:34Z

Bolded some words in the Using FPFSS section, added a bit in the Notes section about the Broken Feature tag.

← Older revision		Revision as of 16:53, 19 August 2024
Line 2:		Line 2:

	==Using FPFSS==		==Using FPFSS==
	# Assign yourself to the submission(s) you want to test. The '''Ready for Testing''' and '''Ready for Verification''' buttons at the top of [https://fpfss.unstable.life/ FPFSS]'s '''Browse Submissions''' page will provide you with a list of submissions in need of testing, sorted by oldest first. The former option will show you submissions that have not been reviewed at all yet, while the latter shows ones that have been tested by one staff member already and need to be double checked. There is no difference in the process whether you are testing or verifying, other than having to use the blue '''Assign Testing''' button if you are testing and the brown '''Assign Verification''' if you are verifying. If you just want to test curations and not [[Content Patches\|content ~~fixes~~]], go to the "Filter by type" section in the "Quick filters" menu and select "Curations". ‎<br /> If you are assigning yourself to a single submission, go to the submission's page and click the appropriate assignment button at the bottom of the page. If you are assigning yourself to multiple submissions, check the boxes for each submission you want on the left side of the list on the Browse page then use the assignment buttons at the bottom of the list to apply the action to all selected submissions.		# Assign yourself to the submission(s) you want to test. The '''Ready for Testing''' and '''Ready for Verification''' buttons at the top of [https://fpfss.unstable.life/ FPFSS]'s '''Browse Submissions''' page will provide you with a list of submissions in need of testing, sorted by oldest first. The former option will show you submissions that have not been reviewed at all yet, while the latter shows ones that have been tested by one staff member already and need to be double checked. There is no difference in the process whether you are testing or verifying, other than having to use the blue '''Assign Testing''' button if you are testing and the brown '''Assign Verification''' if you are verifying. If you just want to test curations and not [[Content Patches\|content patches]], go to the '''Filter by type''' section in the '''Quick filters''' menu and select '''Curations'''. ‎<br /> If you are assigning yourself to a single submission, go to the submission's page and click the appropriate assignment button at the bottom of the page. If you are assigning yourself to multiple submissions, check the boxes for each submission you want on the left side of the list on the Browse page then use the assignment buttons at the bottom of the list to apply the action to all selected submissions.
	# Use the '''Get''' button to download that submission or, for multiple submissions, with the boxes still checked from when you assigned yourself to them, use the '''Download Selected''' button near the bottom of the pag to compress all of the submissions together as a file that will need to be extracted using 7-Zip before you can open them.		# Use the '''Get''' button to download that submission or, for multiple submissions, with the boxes still checked from when you assigned yourself to them, use the '''Download Selected''' button near the bottom of the pag to compress all of the submissions together as a file that will need to be extracted using 7-Zip before you can open them.
	# In your Flashpoint's Curate tab, use the '''Load Archive''' button at the right panel and select the downloaded file(s). Check over their metadata for any errors and run each submission to make sure it works (do not use MAD4FP). You are not required to play through the entire game, but enough that you can be confident that it works.		# In your Flashpoint's Curate tab, use the '''Load Archive''' button at the right panel and select the downloaded file(s). Check over their metadata for any errors and run each submission to make sure it works (do not use MAD4FP). You are not required to play through the entire game, but enough that you can be confident that it works.
Line 101:		Line 101:
	* The Notes are overly long or complex at explaining some information the player needs.		* The Notes are overly long or complex at explaining some information the player needs.
	* The submission has an Extras Application, but no Note explaining what the Extras are.		* The submission has an Extras Application, but no Note explaining what the Extras are.
			* The submission is accompanied with the <code>Broken Feature</code> tag, but there is no note explaining what is broken.
	\|-		\|-
	\| '''Original Description'''		\| '''Original Description'''

Childishbeat: /* Basic metadata requirements */ Fixed a grammatical error in Series.

2024-03-02T15:02:28Z

Basic metadata requirements: Fixed a grammatical error in Series.

← Older revision		Revision as of 17:02, 2 March 2024
Line 37:		Line 37:
	\| Should not be the franchise it relates to.		\| Should not be the franchise it relates to.
	:- e.g. a Mario game should have the <code>Super Mario</code> tag and not "Super Mario" in the Series field.		:- e.g. a Mario game should have the <code>Super Mario</code> tag and not "Super Mario" in the Series field.
	:- If an unofficial series ~~has indeed that~~ name, request the field to be <code>Super Mario (dev/publisher's name)</code> instead.		:- If an unofficial series uses this name, request the field to be <code>Super Mario (dev/publisher's name)</code> instead.
	\|-		\|-
	\| '''Developer''' and '''Publisher'''		\| '''Developer''' and '''Publisher'''

Revac: /* Basic metadata requirements */ minor formatting

2024-01-27T18:20:46Z

Basic metadata requirements: minor formatting

← Older revision		Revision as of 20:20, 27 January 2024
Line 78:		Line 78:
	\|-		\|-
	\| '''Platform'''		\| '''Platform'''
	\| Changes should be requested if this field is incorrect. For information specific to each Platform go to [[#Platform Specific Requirements]].		\| Changes should be requested if this field is incorrect. For information specific to each Platform go to [[#Platform Specific Requirements\|Platform Specific Requirements]].
	\|-		\|-
	\| '''Application Path'''		\| '''Application Path'''

Prostagma: Cleanup, less bold text

2023-10-14T18:10:42Z

Cleanup, less bold text

Show changes

Cursed-light: Remove (via Wayback Machine) method

2023-05-05T22:48:39Z

Remove (via Wayback Machine) method

← Older revision		Revision as of 00:48, 6 May 2023
Line 75:		Line 75:
	\| The Source should:		\| The Source should:
	* Be the full URL of where the curator found the game.		* Be the full URL of where the curator found the game.
	* If the curation was sourced from the Wayback Machine, this should ~~be indicated by~~ have ~~<code>(via Wayback Machine)</code> at the end of the Source, or by having~~ the full web.archive.org URL as the Source.		* If the curation was sourced from the Wayback Machine, this should have the full web.archive.org URL as the Source.
	* If the curation was not sourced from a webpage, there will be some other way of indicating where it came from, e.g. a game from a CD should have the name of the CD.		* If the curation was not sourced from a webpage, there will be some other way of indicating where it came from, e.g. a game from a CD should have the name of the CD.
	\|-		\|-

RockoRotten: Added an additional instruction in #1 of the "How To Test Using the FPFSS" section, and rephrased the last bulletpoint in the "Tags" section of "Checking Metadata".

2023-05-03T15:58:33Z

Added an additional instruction in #1 of the "How To Test Using the FPFSS" section, and rephrased the last bulletpoint in the "Tags" section of "Checking Metadata".

← Older revision		Revision as of 17:58, 3 May 2023
Line 3:		Line 3:
	In order to test submissions, you must be a Staff Member with the Curator role in the Discord server. The process for how to test a submission is fairly simple, and is similar to the old Batch Check system.		In order to test submissions, you must be a Staff Member with the Curator role in the Discord server. The process for how to test a submission is fairly simple, and is similar to the old Batch Check system.

	# The first step is to assign yourself to the submission(s) you want to test. The '''Ready for Testing''' and '''Ready for Verification''' buttons near the top of the '''Browse Submissions''' page on the FPFSS will provide you with a list of submissions in need of testing, sorted by oldest first. The '''Ready for Testing''' option will show you submissions that have not been reviewed at all yet, while the '''Ready for Verification''' option will show you ones that have been tested by one staff member already and need to be double checked. There is no difference in the process whether you are Testing or Verifying, other than making sure to use the blue '''Assign Testing''' button if you are Testing and the brown '''Assign Verification''' if you are verifying. ‎<br /> If you are assigning yourself to a single submission, go to the submission's page and click the appropriate assignment button at the bottom of the page. If you are assigning yourself to multiple submissions, check the boxes for each submission you want on the left side of the list on the Browse page. Then use the assignment buttons at the bottom of the list to apply the action to all selected submissions.		# The first step is to assign yourself to the submission(s) you want to test. The '''Ready for Testing''' and '''Ready for Verification''' buttons near the top of the '''Browse Submissions''' page on the FPFSS will provide you with a list of submissions in need of testing, sorted by oldest first. The '''Ready for Testing''' option will show you submissions that have not been reviewed at all yet, while the '''Ready for Verification''' option will show you ones that have been tested by one staff member already and need to be double checked. There is no difference in the process whether you are Testing or Verifying, other than making sure to use the blue '''Assign Testing''' button if you are Testing and the brown '''Assign Verification''' if you are verifying. If you just want to test curations and not content fixes, go to the '''Filter by type''' section in the '''Quick filters''' menu and select '''Curations'''. ‎<br /> If you are assigning yourself to a single submission, go to the submission's page and click the appropriate assignment button at the bottom of the page. If you are assigning yourself to multiple submissions, check the boxes for each submission you want on the left side of the list on the Browse page. Then use the assignment buttons at the bottom of the list to apply the action to all selected submissions.
	# Next you'll need to download the submission(s). For a single submission, use the '''Download Latest Version''' button on the submission's page. For multiple submissions, with the boxes still checked from when you assigned yourself to them, use the '''Download Selected''' button near the bottom of the page. It will compress all of the submissions together as a file that will need to be extracted using 7-Zip before you can open the submissions in Core.		# Next you'll need to download the submission(s). For a single submission, use the '''Download Latest Version''' button on the submission's page. For multiple submissions, with the boxes still checked from when you assigned yourself to them, use the '''Download Selected''' button near the bottom of the page. It will compress all of the submissions together as a file that will need to be extracted using 7-Zip before you can open the submissions in Core.
	# The next thing you'll need to do is open the submissions in Core. In the Curate tab, use the '''Load Archive''' in the right panel and select the downloaded curation file(s). Once Core has opened all of the files, you can start testing. You'll need to check over the metadata for any errors, as well as running the submission to make sure it works. You are not required to play through the entire game, you only need to play enough that you can be confident that it works.		# The next thing you'll need to do is open the submissions in Core. In the Curate tab, use the '''Load Archive''' in the right panel and select the downloaded curation file(s). Once Core has opened all of the files, you can start testing. You'll need to check over the metadata for any errors, as well as running the submission to make sure it works. You are not required to play through the entire game, you only need to play enough that you can be confident that it works.
Line 53:		Line 53:
	* There is a tag used which is not on the [[Tags]] wiki page.		* There is a tag used which is not on the [[Tags]] wiki page.
	* The curation has no Gameplay (or Animation) Tags or if the Gameplay tags it has are incorrect.		* The curation has no Gameplay (or Animation) Tags or if the Gameplay tags it has are incorrect.
	* The <code>LEGACY-Extreme</code> ~~tag is used~~. ~~This tag~~ should not be added to any new submissions.		* The tag is no longer used, e.g. <code>LEGACY-Extreme</code>, <code>Find</code>, <code>Unusual Input</code>. These tags should not be added to any new submissions.
	\|-		\|-
	\| '''Play Mode'''		\| '''Play Mode'''

Curs3dLight: Adding the rule saying that when there are hacked files, the unhacked version have to be in the content folder

2022-10-10T19:40:13Z

Adding the rule saying that when there are hacked files, the unhacked version have to be in the content folder

← Older revision		Revision as of 21:40, 10 October 2022
Line 155:		Line 155:
	* Contains any DLL files.		* Contains any DLL files.
	* Contains EXE files in the Content folder. These files are allowed in the Extras folder only.		* Contains EXE files in the Content folder. These files are allowed in the Extras folder only.
			* Files have been hacked but the originals, unhacked files aren't in the Content folder.
	\|}		\|}

Nosamu at 06:13, 28 June 2022

2022-06-28T06:13:13Z

← Older revision		Revision as of 08:13, 28 June 2022
Line 26:		Line 26:
	* The Title doesn't roughly match the submission's logo (if it has one).		* The Title doesn't roughly match the submission's logo (if it has one).
	* There are spelling errors.		* There are spelling errors.
			* The Title text was clearly intended to be a description of the game, not the actual title. Descriptions go in the Original Description field.
	Along with the above, Alternate Titles should not:		Along with the above, Alternate Titles should not:
	* Be a shorter version of the Main Title.		* Be a shorter version of the Main Title.