Before creating a new game page, check the games category to confirm that the page for such game does not already exist. Only one game page is created for all versions of a game. This means that all region IDs, demos, DLCs and special editions of a game will be grouped together in the same game page (see Catherine). Also, if game collections exist that bundle existing standalone PS3 titles, create a game page only for collection and record all game IDs (collection and standalone) in that single page (see God of War: Origins Collection).
To create a new game page, enter the game name in the text box below. If such a page does not exist in the wiki, you will be prompted with the option to create a new game with the game name as the page title. If a game has multiple titles in various languages, please use the English version in the page title. Where more than one English title exists, use the one that is more common (generally the US version). To prevent spam and incorrect page creation, all edits must be approved by a moderator prior to taking effect. Hence, when creating a new game page, users may have to wait until approval for their contributions to appear on the wiki.
Create new game page
Before creating a new game page, please read the requirements page carefully. If you're sure the this particular game does not have a game page already, you can create the page by entering the game title in the textbox below:
This is the box on the right-hand side of the page which summarises the basic information of the game. The infobox is also linked to its own set of categories which allows you to find games with similar information in a convenient manner. Game infoboxes use the vginfobox template, which contains parameters requiring various details. For guidance on how to fill the template, kindly read the documentation provided in its template page along with vgregion and gameid templates.
A description should be brief but include some basic information about what the game is and what its gameplay is like. Usually we put the name of the game fairly early in the description, and put it in '''''bold italics'''''. Links to relevant articles, such as prequels or sequels, are always good. Most of the time we just pull descriptions from wikipedia and tweak them a bit, removing things like references to other systems and release dates or other information already covered in the infobox.
This section uses the configuration template to capture non-default settings for maximum emulation accuracy or explicitly broken enhancement options on game pages. The complete list of default settings can be found here. An ideal configuration setup lists all the settings needed for flawless emulation regardless of performance. Each configuration entry can also include a "notes" entry to highlight any necessary information or explain the issue(s) addressed.
Recommendatory settings, like telling users with weaker CPUs to try Lower SPU thread priority, shouldn't be included. Such guidance applies to all games and has already been covered in the default settings pages. Also, if an unusual setting improves performance and does nothing else, it still shouldn't be included here, but a note may be placed under the Special Notes section.
Other improvements not related to compatibility should also be left off the configuration list. For example, if someone turns on the Anisotropic filter, they know what they are getting into. The exception to that is if it toggling such settings causes issues, like a crash or unusual sprites.
Please do not use this area for recommended controller configurations. What buttons are assigned to which binding varies based on the game, the controller being used, and personal tastes. It is up to users to figure that out.
This section should contain a list of issues that affect the latest master. Do not post issues here without discussing the same on forums and discord. Also, read the issue tracker on Github to check if such issues have been reported. Most problems users face can be resolved by using the appropriate settings for that title. If you are convinced the issue is valid, only document issues on the wiki after discussing the same with developers or moderators on forums or Discord.
Give the issue a title in bold. Where available, use the issues template to link the corresponding issue on Github. If an issue is fixed in the master repo, it should be moved to the bottom and the title of the issue should be crossed out with the slash
<s> tags (
<s>like this</s>) with a note describing how it was fixed and by which pull request if that info is known. Use the pull request template to link the corresponding PR on Github. On a periodic basis, all existing fixed issues are purged, so it is vital to fill out when and why an issue was fixed so it can be cleared later. Each issue is listed on its own without grouping, to make it easier to deal with. Issues are generally ordered with the most severe ones first, such as crashing or hanging bugs, then going to down to the least severe and fixed issues at the bottom.
This area is used to describe behaviors or information that aren't necessarily emulation issues (e.g. PSN version of Demon's Souls show the Blu-ray version's game ID on the game list, information on patches, etc.) but details which users may find useful. Information present in this section generally shouldn't affect the compatibility status of a given title. This section need not be shown if there's no suitable entries for that game, otherwise it's listed right after the Known Issues section.