Submitting Game Updates

You should submit a game update when an existing Games Database record is close, but something about it is wrong, missing, outdated, or unclear. Updating the existing game keeps the database cleaner than creating a duplicate and helps LaunchBox match, scrape, and display games more accurately.

Common examples include a missing release year, the wrong developer, an incomplete overview, a regional title that is not listed as an alternate name, a publisher attached to the wrong version, an incorrect player count, or a game that has good metadata but needs a clearer Wikipedia or video link. Even a small correction can help the next person who imports that game into LaunchBox.

If the game is not in the database at all, use the add-game workflow instead. If the record is a duplicate or should not exist, use the deletion workflow. If the game exists and needs better data, this is the right place to start.

Start from the existing game

Before editing, make sure you are on the correct game record. Check the title, platform, release information, and images so you do not accidentally submit changes to a different version of the game.

This matters most when several games share a similar name, when a game exists on many platforms, or when regional releases have different titles. For example, a search for Contra may return different games and platforms, while a title like Final Fantasy VI may also be known by another regional or historical name.

If the game you found is a duplicate or should not exist at all, use the deletion workflow instead. If the record is correct but incomplete, use the edit workflow.

Open the edit form

From the game details page, choose the edit action. The edit form is where you can propose changes to the game's metadata, such as the title, release details, game type, player count, cooperative status, ESRB rating, developers, publishers, genres, overview, links, and alternate names.

You do not need to change every field. A focused update that fixes one known issue is better than a large update that includes guesses. If you only know the correct developer, update the developer. If you only know a missing alternate name, add the alternate name and leave everything else alone.

Update names carefully

The main title should match the game's official title for that platform as closely as possible. Use the title shown on the box art, official store page, manual, or another reliable source.

Avoid changing titles just for sorting or personal preference. For example, use The Legend of Zelda rather than Legend of Zelda, The. Use punctuation that matches the official title where possible, such as DOOM 3: Resurrection of Evil rather than DOOM 3 - Resurrection of Evil.

If a title is valid but not the main title, add it as an alternate name instead of replacing the primary name.

Add useful alternate names

Alternate names help LaunchBox match games during imports, especially when a user's files use a regional title, subtitle variation, translated name, or common shorthand.

Good alternate names are names that someone might reasonably have in their LaunchBox library. Examples include:

• Biohazard as an alternate name for a game known as Resident Evil in another region.

• Final Fantasy III as an alternate name for a release later known as Final Fantasy VI.

• Kirby's Fun Pak as a regional alternate name for Kirby Super Star.

• Probotector as a regional title used for some Contra releases.

When an alternate name applies only to a specific region, select that region. If it is a general spelling variation or common name, use the most appropriate region setting available.

Do not add jokes, abbreviations that are not commonly used, file naming clutter, scene release tags, ROM set suffixes, or personal collection names as alternate names.

Use accurate release information

If you know the full release date, use the release date field. If you only know the year, use the year-only option rather than inventing a month or day.

For example, if a trusted source only confirms that a game released in 1994, enter 1994 as the release year. Do not enter January 1, 1994 just to fill a complete date.

Release information should match the specific game and platform record you are editing. A game may have different release dates across arcade, console, handheld, computer, or regional versions.

Choose developers, publishers, and genres consistently

When adding developers, publishers, or genres, use the existing suggestions from the form where possible. This helps prevent duplicate names and keeps the database easier to search.

Only add companies or genres that apply to that specific game record. If a company published one regional release but not another, make sure the value fits the version represented by the page.

For genres, choose what best describes the game rather than every category that could loosely apply. A cleaner, more accurate genre list is more useful than a long one.

Write a useful overview

The overview should describe the game clearly, neutrally, and in your own words. It should help someone understand what the game is, how it plays, or what makes this version notable.

Avoid copied marketing text, review language, personal opinions, walkthrough details, and unsupported claims. A good overview reads like database metadata, not a sales pitch.

For example, a useful overview might mention that a game is a side-scrolling action platformer, that it supports two players, or that it is an expanded home version of an arcade game. It should not say that the game is "the best ever" or include long plot spoilers unless they are essential to identifying the game.

Add links only when they help identify the game

Wikipedia and video links should point to relevant public pages for the specific game. A good link helps moderators and users verify what the game is.

Use the exact game's page when possible, not a broad franchise page. For videos, choose a relevant trailer, gameplay video, or official video that represents the game well.

If you are not sure a link belongs to the exact game record, leave it out.

Explain your submission

A reason is required for game updates. Use it to tell moderators what changed and why. This does not need to be long, but it should give enough context for someone else to review the change confidently.

Good reasons include:

• Corrected release year from 1995 to 1994 based on the manual and publisher page.

• Added European alternate title shown on PAL box art.

• Updated developer to match in-game credits.

• Rewrote overview to remove copied marketing text and describe gameplay neutrally.

Weak reasons include fixed it, wrong info, or looked better. If you used a source, mention it in the reason when practical.

Submit and track the change

After you submit, the update goes into moderation. Moderators compare your proposed change against the current record, the reason you provided, and any sources or context that help verify it.

Your change will be approved if it improves the record and follows the database standards. It may be rejected if it is inaccurate, unclear, unsupported, duplicated, entered in the wrong field, or submitted against the wrong game.

You can check your submitted changes from the changes/status area of the website. Pending changes are still waiting for review. Approved changes become part of the Games Database. Rejected changes do not apply to the public record.

What to do if a field is locked

Some fields may be locked to protect data that has already been reviewed or corrected. If a field is disabled, leave it unchanged and submit updates only to the fields that are available.

If you believe a locked field is wrong, gather clear evidence and use the appropriate support or community channel to raise it rather than working around the locked field.

Good habits for game updates

• Check that you are editing the correct game and platform before changing anything.

• Fix known issues instead of guessing unknown values.

• Use alternate names for regional or historical titles instead of replacing the main title incorrectly.

• Use existing developer, publisher, and genre suggestions when available.

• Write neutral overview text in your own words.

• Explain what changed in the submission reason.

• Use the moderation guidelines when you are unsure what counts as good data.