This wiki has been closed following a Request for Comments. Please see this page for more information.

Crappy Games Wiki:Tutorial

From Crappy Games Wiki
Jump to navigation Jump to search

This is a tutorial on how to create an article on Crappy Games Wiki.

Starting

You need to have an account and be autoconfirmed or confirmed. To create an account, click here. To request confirmation, contact the admins by leaving them a message. (note that if you have enough edits and your account is old enough, your account will be autoconfirmed and you won't need to contact the admins)

It is preferred to draft pages on your sandbox (preferably on subpages).

If the game/console/company/webshop has mostly mixed reviews, use the Bad Qualities header. Otherwise, use either Why It Sucks for games, Why It Flopped for consoles, Why (They/He/She) and (Their/His/Her) Games Suck for developers. If the game/console/company/webshop has/have mostly positive reviews (for games and developers) or if it succeeded (for consoles), create it on Awesome Games Wiki instead.

Due to corruption in gaming journalism, make sure to check this blog for reliable sources first.

Make sure to read both the rules and guidelines and forbidden pages on the Main Page before creating your article.

Examples of pages not to create can be found here and here.

To make a well-written and detailed page, check the wiki's good and featured articles, which can easily be found on the main page.

Do not add categories to sandboxes, instead, wrap the categories inside a <pre> block, and remove the <pre> block when you publish your article.

Choosing the first contents of the page

The first contents vary per type of article.

For games

One image

{{GameInfobox
|Picture=ImageName.png
|Quote=Insert a quote here.
|Protagonist=(insert the name of the protagonist)
|Genre=(insert the name of the genre)
|Platforms=(insert any platform)
|Release Date=(insert the release date)
|Delist Date=(insert the delist date)
|Game Engine=(insert the game engine)
|Developer=(insert the name of the developer)
|Publisher=(insert the name of the publisher)
|Country=(insert the country)
|Franchise=(insert the name of the franchise)
|Prequel=(insert the name of the previous game)
|Sequel=(insert the name of the next game)
}}'''Game name''' is a game developed by (insert the name of the developer) and published by (insert the name of the publisher) on (insert the release date).

Multiple images

{{MPGameInfobox
|Picture=<tabber>Tab 1=[[File:ImageName.png|330px]]|-|Tab 2=[[File:ImageName2.png|330px]]</tabber>
|Quote=Insert a quote here.
|Protagonist=(insert the name of the protagonist)
|Genre=(insert the name of the genre)
|Platforms=(insert any platform)
|Release Date=(insert the release date)
|Delist Date=(insert the delist date)
|Game Engine=(insert the game engine)
|Developer=(insert the name of the developer)
|Publisher=(insert the name of the publisher)
|Country=(insert the country)
|Franchise=(insert the name of the franchise)
|Prequel=(insert the name of the previous game)
|Sequel=(insert the name of the next game)
}}'''Game name''' is a game developed by (insert the name of the developer) and published by (insert the name of the publisher) on (insert the release date).

For consoles

One image

{{ConsoleInfobox
|Picture=ImageName.png
|Quote=Add a quote here.
|Developer=(add the manufacturer name here)
|Release Date=(add the release date here)
|Predecessor=(add the previous console of the manufacturer here)
|Successor=(add the next console of the manufacturer here)
|Competitors=(add competitor consoles here)
|Generation=(add the console generation here)
|Discontinued=(add the discontinuation date here)
}}'''Console name''' is a console manufactured by (add the manufacturer name here) and released on (add the release date here).

Multiple images

{{MPConsoleInfobox
|Picture=<tabber>Tab 1=[[File:ImageName.png|330px]]|-|Tab 2=[[File:ImageName2.png|330px]]</tabber>
|Quote=Add a quote here.
|Developer=(add the manufacturer name here)
|Release Date=(add the release date here)
|Predecessor=(add the previous console of the manufacturer here)
|Successor=(add the next console of the manufacturer here)
|Competitors=(add competitor consoles here)
|Generation=(add the console generation here)
|Discontinued=(add the discontinuation date here)
}}'''Console name''' is a console manufactured by (add the manufacturer name here) and released on (add the release date here).

For companies

One image

{{CompanyInfobox
|Picture=ImageName.png
|Quote=Add a quote here.
|Founded=(add the foundation name here)
|Defunct=(add the dissolution date here)
|Founder=(add the founders here)
|Key people=(add the key people here)
|Services=(add the services the company own here)
|Predecessor=(add the predecessor company here)
|Successor=(add the successor company here)
|Parent=(add the parent company here)
|Subsidiaries=(add the subsidiaries here)
|Website=(add the company's website here)
}}'''Company name''' is a(n) (country the company's headquarters is currently located, examples: American, German) (type of company, like a video game developer and/or publisher) headquartered in (location of the company's headquarters).

Multiple images

{{MPCompanyInfobox
|Picture=<tabber>Tab 1=[[File:ImageName.png|330px]]|-|Tab 2=[[File:ImageName2.png|330px]]</tabber>
|Quote=Add a quote here.
|Founded=(add the foundation name here)
|Defunct=(add the dissolution date here)
|Founder=(add the founders here)
|Key people=(add the key people here)
|Services=(add the services the company own here)
|Predecessor=(add the predecessor company here)
|Successor=(add the successor company here)
|Parent=(add the parent company here)
|Subsidiaries=(add the subsidiaries here)
|Website=(add the company's website here)
}}'''Company name''' is a(n) (country the company's headquarters is currently located, examples: American, German) (type of company, like a video game developer and/or publisher) headquartered in (location of the company's headquarters).

For game stores

Coming soon.

Adding sources

Sources are optional for most articles, but for articles about people, they are required due to repeated violations of the Content Policy.

As mentioned above, a list of many reliable sources are available here and here.

A basic source can be added with the following code:

This is an example.<ref name="sourcename">The source of the claim.</ref>

Getting the box art

Box art can be obtained in various ways (either by scanning it yourself or finding it on websites).

If you're scanning the box art yourself, it is recommended to scan it as PNG and on the highest quality supported by your scanner or software.

If you're obtaining the box art from a website, use this chart to determine if a website is recommended. The check mark means that it's recommended and the X means that it's not recommended.

  • Yes check.svg GameFAQs
  • Yes check.svg Google Images (if you find a high quality scan, a minimum of 500x500px is recommended)
  • Yes check.svg MobyGames
  • X mark.svg Wikipedia (mostly low quality)

Uploading and using files

Uploading

There are two ways of uploading a file, MsUpload and Special:Upload. MsUpload allows you to upload multiple files at once, meanwhile Special:Upload only allows you to upload one file at a time.

MsUpload

Drag and drop your files into the "Drop files here" bar in the source editor, give the files a descriptive name (like "(game name) box art.png"), then click the "Upload this file/Upload all files" button.

Special:Upload

Select the file, give it a descriptive name and fill out the summary with things like a description and the source of the image.

Most of the time, the license should be "This will be used in a way that qualifies as fair use under US law".

Then, click the "Upload file" button.

Using

Basic use

The following code will embed the file:

[[File:(your file name)]]

Adding the "right" parameter shows it in the right side of the screen:

[[File:(your file name)|right]]

and so does the "left" parameter:

[[File:(your file name)|left]]

Adding the following parameter makes the file 300 pixels wide:

[[File:(your file name)|300px]]

The following makes it 200 pixels tall:

[[File:(your file name)|x200px]]

And the following makes it both 300 pixels wide and 200 pixels tall:

[[File:(your file name)|300x200px]]

Adding the "border" parameter shows a border around the file:

[[File:(your file name)|border]]

The "thumb" parameter shows a thicker border and allows you to put a quote on the image:

[[File:(your file name)|thumb|Example.]]

On the infobox

To use the uploaded file on the infobox, replace "ImageName.png" in the "Picture" parameter with the name of your file (without the File: prefix, if the infobox only allows for a single image.

|Picture=Example.png
|Picture=<tabber>Foo=[[File:Example.png|330px]]|-|Bar=[[File:Example.jpg|330px]]</tabber>

Creating the article

Copy and paste the following text on your sandbox or its subpages:

(Insert the first contents here. See the "Adding the first contents of the page" section)

==Plot (optional)==
Add the game's plot here.

==Why It Sucks/Why It Flopped/Why (They/He/She) and (Their/His/Her) Games Suck/Why (They/He/She) Suck(s)/Bad Qualities==
#WIS 1
#WIS 2
#WIS 3

==Redeeming Qualities/The Only Redeeming Quality/Good Qualities==
#RQ 1
#RQ 2
#RQ 3

==Reception ==
Add reception content here.

==Videos==
<youtube width="320" height="180">Video-ID</youtube>

==References==
<references/>

==Comments==
<comments/>

Adding reasons

"Why It Sucks/Bad Qualities" is the only required header on a page (apart from pages about terrible moments in gaming history), if a page doesn't have it, it will be deleted.

To add WIS reasons/redeeming qualities, add #the reason as a new line on the "Why It Sucks"/"Redeeming Qualities" section. Avoid using short reasons, like instead of "Bad graphics." use "Bad and outdated graphics. They look like a PlayStation 1 game, despite the game being released in 2014."

A more complete guide to adding reasons in articles can be found below:

How to write an article, step by step

(Pay attention to the color indicators to get a better idea of what each point is trying to teach!)

Primary tips/essential resources:

  1. The biggest priority when writing an article is to explain with detail what your point is to get it across correctly. Each pointer has to provide a defense to its statement rather than vaguely confirming without one.
    • Don't do this:
  1. Creative take on the game's genre.
  • Do this:
  1. Creative take on the game's genre: Half-Life innovated the FPS genre thanks to its merge with brain-teasing puzzles, which opens up new gameplay ideas and challenges.
2. All pointers from both the positive and negative sections must sound like a respectful thought and not an informal bias relying on nothing but adverbs and adjectives. Avoid the previously mentioned and endorse they provide equal informative value to the article.
  • Don't do this:
Why It Rocks

  1. Blazing Beaks' irreplaceable gameplay is characterized by the innovative Artifacts mechanic. Artifacts are items that debuff your character, and with each Artifact that you pick up, your 'Risk Value' increases. You can empty your Risk Value in the shop levels by trading your Artifacts with the Crow in exchange of good items. Risk Value determines how good your rewards will be.
  2. Incredibly exceptional pixel art graphics.
Bad Qualities

  1. Heavy reliance on random number generation, especially with the tedious Artifact drops.
  • Do this:
Why It Rocks

1.

statementBlazing Beaks' irreplaceable gameplay is characterized by the innovative Artifacts mechanic. defenseArtifacts are items that debuff your character, and with each Artifact that you pick up, your 'Risk Value' increases. You can empty your Risk Value in the shop levels by trading your Artifacts with the Crow in exchange of good items. Risk Value determines how good your rewards will be.

2.

statementIncredible pixel art graphics defensethat compose an important part of the game's world and feel, as their looks and sprite animations are polished, the character and enemy design choices stick to the art-style while looking unique from one another, and each environment has a proper use of colors that make them special in their own way.

Bad Qualities

1.

statementHeavy reliance on random number generation, especially with the tedious Artifact drops, defensegiven you will not always receive that many Artifacts in the first levels and many drops won't give you that much Risk Value either. Some specific game modes shouldn't allow certain Artifacts to drop as they could break the run to your advantage or to your misfortune, yet they can appear as drops regardless.

Secondary tips for users with high standards:

3. Organize pointers attentively and remark the important; don't put unequal focus on random details of the game, but the ones that strike of it the most. Your first pointer has to be the most powerful one, as it gets a game's spot in the wiki where it is. Anything that catches players' attention the most should be analyzed before the secondary reasons, later come the minor attributes.
  • Don't do this:
1. On-point soundtrack by Valmont, submitting a collection of adrenergic songs that spice up the emotion of their respective segments significantly. A notable element are the guitar segments that predominate over all other instruments without vanquishing them out of the spotlight entirely, as seen with the track Prisoner's Awakening.
2. Delicate choice of features in general. Every aspect of the game was designed to work reciprocally with the others, which only makes a tiny contribution to the panoramic success of Dead Cells' exemplar game design.
3. Dead Cells' metroidvania-roguelike gameplay is one of the game's most impressive aspects, as the potential that this concept had was correctly exploited with its multiple freshly planned mechanics.
4. Frenetic combat system that pushes the limits of action-platformers with an effective use of unique playstyle mechanics for each gear and predictable, but challenging attack patterns for each enemy.
  • Do this:
1.

statementDead Cells' metroidvania-roguelike gameplay is, by far, the game's most impressive aspect and the primary cause of its success, defenseas the potential that this concept had was correctly exploited with its multiple freshly planned mechanics examined in the following pointers.

2.

statementDelicate choice of features in general. defenseEvery aspect of the game was designed to work reciprocally with the others, which only makes a tiny contribution to the panoramic success of Dead Cells' exemplar game design.

3.

statementFrenetic combat system that pushes the limits of action-platformers defensewith an effective use of unique playstyle mechanics for each gear and predictable, but challenging attack patterns for each enemy.

4.

statementOn-point soundtrack by Valmont, submitting a collection of adrenergic songs defensethat spice up the emotion of their respective segments significantly. A notable element are the guitar segments that predominate over all other instruments without vanquishing them out of the spotlight entirely, as seen with the track Prisoner's Awakening. equal value

Publishing the article

Before you publish your article, you should show your sandbox to the community (especially admins) on the main page's talk page for quality assurance.

A page can be approved for publishing from the community (especially admins), providing that:
  1. Its length in bytes is at least 1000-2000 or greater.
  2. The number of bad qualities is greater than that of good qualities by at least 3-5 if the page is on CGW and vice versa if it is on AGW.
  3. It makes good use of wikitext.
  4. The grammar on the page is not broken.
  5. All sentences, phrases on the page ends with punctuation.
  6. Capitalisation only occurs in proper nouns.

Once the page is approved for publishing, click the Move page button to publish your article into the wiki. On Vector (the default skin), it's hidden on the More dropdown menu.

Click on "User" then select "(Main)" then replace the contents in the text box with the page name.

Then, click "Move page".