Batch Checking Reject Conditions - Revision history

Prostagma at 15:12, 14 October 2023

2023-10-14T15:12:03Z

← Older revision		Revision as of 17:12, 14 October 2023
Line 73:		Line 73:

	Once you have finished checking a batch, send a message in the #batch-checkers channel listing the batch you checked and the curations you rejected, if any. Rejected curations should also be reuploaded into #batch-rejects, following the instructions in the pinned post on said channel.		Once you have finished checking a batch, send a message in the #batch-checkers channel listing the batch you checked and the curations you rejected, if any. Rejected curations should also be reuploaded into #batch-rejects, following the instructions in the pinned post on said channel.

			<noinclude>
			[[Category:Curation Guides]]
			</noinclude>

BlueMaxima at 03:48, 9 April 2021

2021-04-09T03:48:46Z

← Older revision		Revision as of 05:48, 9 April 2021
Line 34:		Line 34:

	'''Notes: ''' Notes should be short, to the point, with no extraneous nonsense. Examples that should be rejected:		'''Notes: ''' Notes should be short, to the point, with no extraneous nonsense. Examples that should be rejected:
			* Non-English notes.
	* Controls that are easy to figure out by hitting random buttons or are explained in game.		* Controls that are easy to figure out by hitting random buttons or are explained in game.
	* Instructions or walkthroughs that are along the same lines.		* Instructions or walkthroughs that are along the same lines.

Nosamu at 05:49, 25 March 2021

2021-03-25T05:49:50Z

← Older revision		Revision as of 07:49, 25 March 2021
Line 71:		Line 71:
	If it doesn't, mention the person in question and give them the opportunity to fix it up and resubmit it. If they don't respond within a reasonable amount of time (a day or so), fix and resubmit it yourself.		If it doesn't, mention the person in question and give them the opportunity to fix it up and resubmit it. If they don't respond within a reasonable amount of time (a day or so), fix and resubmit it yourself.

	Once you have finished checking a batch, send in a message in the #batch-checkers channel listing the batch you checked and the curations you rejected, if any. Rejected curations should also be reuploaded into #batch-rejects, following the instructions in the pinned post on said channel.		Once you have finished checking a batch, send a message in the #batch-checkers channel listing the batch you checked and the curations you rejected, if any. Rejected curations should also be reuploaded into #batch-rejects, following the instructions in the pinned post on said channel.

BlueMaxima at 05:42, 25 March 2021

2021-03-25T05:42:46Z

← Older revision		Revision as of 07:42, 25 March 2021
Line 71:		Line 71:
	If it doesn't, mention the person in question and give them the opportunity to fix it up and resubmit it. If they don't respond within a reasonable amount of time (a day or so), fix and resubmit it yourself.		If it doesn't, mention the person in question and give them the opportunity to fix it up and resubmit it. If they don't respond within a reasonable amount of time (a day or so), fix and resubmit it yourself.

	Once you have finished checking a batch, send in a message in the #batch-checkers channel listing the batch you checked and the curations you rejected, if any. ~~For each rejected curation~~, ~~indicate~~ the ~~status of~~ the ~~curation: <code>(Rejected)</code>, <code>(Will Resubmit)</code>, or <code>(Resubmitted)</code>. After you resubmit curations, edit your message to indicate that~~.		Once you have finished checking a batch, send in a message in the #batch-checkers channel listing the batch you checked and the curations you rejected, if any. Rejected curations should also be reuploaded into #batch-rejects, following the instructions in the pinned post on said channel.

Nosamu at 05:11, 25 March 2021

2021-03-25T05:11:24Z

← Older revision		Revision as of 07:11, 25 March 2021
Line 1:		Line 1:
	The following is a quick and dirty list of things to fail a curation for, field by field.		The following is a quick and dirty list of things to fail a curation for, field by field.

	If a curation fails one of these conditions, ping the curator in #curator-lounge, explain their mistake, and ask them to reupload the curation. If they haven't done so within a day or so, fix the curation and resubmit it yourself.

	Once you have finished checking a batch, send in a message in the #batch-checkers channel listing the batch you checked and the curations you rejected, if any. For each rejected curation, indicate the status of the curation: <code>(Rejected)</code>, <code>(Will Resubmit)</code>, or <code>(Resubmitted)</code>. After you resubmit curations, edit your message to indicate that.

	'''Logo and Screenshot: ''' Poor cropping (buttons visible / not enough cropped in logo). Screenshot has things like the Adobe Flash Player window still visible on the edges/too much space on the outside. ''Logos that are taken from the game itself are not rejection worthy, even if there's a proper logo.''		'''Logo and Screenshot: ''' Poor cropping (buttons visible / not enough cropped in logo). Screenshot has things like the Adobe Flash Player window still visible on the edges/too much space on the outside. ''Logos that are taken from the game itself are not rejection worthy, even if there's a proper logo.''
Line 68:		Line 64:

	'''Content Files: ''' Keep your eye open for irrelevant files. Some people upload multiple single-game SWFs in one curation, sometimes. Play the game and see what happens.		'''Content Files: ''' Keep your eye open for irrelevant files. Some people upload multiple single-game SWFs in one curation, sometimes. Play the game and see what happens.

			== After Checking ==

	If a curation passes all of these conditions, it is a successful check.		If a curation passes all of these conditions, it is a successful check.

	If it doesn't, mention the person in question and give them the opportunity to fix it up and resubmit it. If they don't respond within a reasonable amount of time (a day or so), fix and resubmit it yourself.		If it doesn't, mention the person in question and give them the opportunity to fix it up and resubmit it. If they don't respond within a reasonable amount of time (a day or so), fix and resubmit it yourself.

			Once you have finished checking a batch, send in a message in the #batch-checkers channel listing the batch you checked and the curations you rejected, if any. For each rejected curation, indicate the status of the curation: <code>(Rejected)</code>, <code>(Will Resubmit)</code>, or <code>(Resubmitted)</code>. After you resubmit curations, edit your message to indicate that.

Nosamu at 05:07, 25 March 2021

2021-03-25T05:07:35Z

← Older revision		Revision as of 07:07, 25 March 2021
Line 1:		Line 1:
	The following is a quick and dirty list of things to fail a curation for, field by field.		The following is a quick and dirty list of things to fail a curation for, field by field.

	If a curation fails one of these conditions, ping the curator in #curator-lounge, explain their mistake, and ask them to reupload the curation. If they haven't done so within a ~~few days~~, fix the curation and resubmit it yourself.		If a curation fails one of these conditions, ping the curator in #curator-lounge, explain their mistake, and ask them to reupload the curation. If they haven't done so within a day or so, fix the curation and resubmit it yourself.

	Once you have finished checking a batch, send in a message in the #batch-checkers channel listing the batch you checked and the curations you rejected, if any. For each rejected curation, indicate the status of the curation: <code>(Rejected)</code>, <code>(Will Resubmit)</code>, or <code>(Resubmitted)</code>. After you resubmit curations, edit your message to indicate that.		Once you have finished checking a batch, send in a message in the #batch-checkers channel listing the batch you checked and the curations you rejected, if any. For each rejected curation, indicate the status of the curation: <code>(Rejected)</code>, <code>(Will Resubmit)</code>, or <code>(Resubmitted)</code>. After you resubmit curations, edit your message to indicate that.

Nosamu at 05:05, 25 March 2021

2021-03-25T05:05:14Z

← Older revision		Revision as of 07:05, 25 March 2021
Line 1:		Line 1:
	The following is a quick and dirty list of things to fail a curation for, field by field.		The following is a quick and dirty list of things to fail a curation for, field by field.

			If a curation fails one of these conditions, ping the curator in #curator-lounge, explain their mistake, and ask them to reupload the curation. If they haven't done so within a few days, fix the curation and resubmit it yourself.

			Once you have finished checking a batch, send in a message in the #batch-checkers channel listing the batch you checked and the curations you rejected, if any. For each rejected curation, indicate the status of the curation: <code>(Rejected)</code>, <code>(Will Resubmit)</code>, or <code>(Resubmitted)</code>. After you resubmit curations, edit your message to indicate that.

	'''Logo and Screenshot: ''' Poor cropping (buttons visible / not enough cropped in logo). Screenshot has things like the Adobe Flash Player window still visible on the edges/too much space on the outside. ''Logos that are taken from the game itself are not rejection worthy, even if there's a proper logo.''		'''Logo and Screenshot: ''' Poor cropping (buttons visible / not enough cropped in logo). Screenshot has things like the Adobe Flash Player window still visible on the edges/too much space on the outside. ''Logos that are taken from the game itself are not rejection worthy, even if there's a proper logo.''

BlueMaxima at 04:54, 25 March 2021

2021-03-25T04:54:14Z

← Older revision		Revision as of 06:54, 25 March 2021
Line 66:		Line 66:

	If a curation passes all of these conditions, it is a successful check.		If a curation passes all of these conditions, it is a successful check.

			If it doesn't, mention the person in question and give them the opportunity to fix it up and resubmit it. If they don't respond within a reasonable amount of time (a day or so), fix and resubmit it yourself.

BlueMaxima at 01:44, 25 March 2021

2021-03-25T01:44:10Z

← Older revision		Revision as of 03:44, 25 March 2021
Line 35:		Line 35:
	'''Notes: ''' Notes should be short, to the point, with no extraneous nonsense. Examples that should be rejected:		'''Notes: ''' Notes should be short, to the point, with no extraneous nonsense. Examples that should be rejected:
	* Controls that are easy to figure out by hitting random buttons or are explained in game.		* Controls that are easy to figure out by hitting random buttons or are explained in game.
	* Instructions that are along the same lines.		* Instructions or walkthroughs that are along the same lines.
	* Shout-outs to persons or companies or political affiliations.		* Shout-outs to persons or companies or political affiliations.
	* Notes that read like Original Descriptions. People tend to get them in the wrong fields sometimes.		* Notes that read like Original Descriptions. People tend to get them in the wrong fields sometimes.
			* Irrelevant notes about developers or publishers that aren't related to the entry in question.
	* Things that are irrelevant to the context of Flashpoint. Think links to other, related parts to the 'curation' but not the idea of Flash preservation, eg. a financial report.		* Things that are irrelevant to the context of Flashpoint. Think links to other, related parts to the 'curation' but not the idea of Flash preservation, eg. a financial report.
	* Explanations as to why things are the way they are in Flashpoint that are irrelevant to the average user, i.e. "This game runs in Basilisk because"...		* Explanations as to why things are the way they are in Flashpoint that are irrelevant to the average user, i.e. "This game runs in Basilisk because"...

VFDan: Singleplayer -> Single Player

2021-03-23T23:10:46Z

Singleplayer -> Single Player

← Older revision		Revision as of 01:10, 24 March 2021
Line 15:		Line 15:
	'''Tags: ''' Inappropriate tags. Note that ''Extreme'' is a tag now in the form of ''LEGACY-Extreme''. While there may be a lack of tags, as long as there's one general purpose tag and one adult-content related tag for any Extreme titles on top, it isn't rejection worthy.		'''Tags: ''' Inappropriate tags. Note that ''Extreme'' is a tag now in the form of ''LEGACY-Extreme''. While there may be a lack of tags, as long as there's one general purpose tag and one adult-content related tag for any Extreme titles on top, it isn't rejection worthy.

	'''Play Mode: ''' Wrong play mode. Remember Cooperative is two+ people working together, and Multiplayer is two+ people working against eachother. So a game of chess that two people can play against eachother, but also has one player vs AI, is "~~Singleplayer~~; Multiplayer"		'''Play Mode: ''' Wrong play mode. Remember Cooperative is two+ people working together, and Multiplayer is two+ people working against eachother. So a game of chess that two people can play against eachother, but also has one player vs AI, is "Single Player; Multiplayer"

	'''Status: ''' Most of the time this should be Playable. If it's Partial, Hacked or Not Working, there needs to be a Note explaining why. If there isn't, reject.		'''Status: ''' Most of the time this should be Playable. If it's Partial, Hacked or Not Working, there needs to be a Note explaining why. If there isn't, reject.