How to Contribute a Game Request or List Update to The BIG List of Video Game Randomizers

The BIG List of Video Game Randomizers accepts contributions through its GitHub repository, which the site announced as open source. According to the site, contributors can post game requests and list updates there, and the full announcement is linked from the site itself. If you want a randomizer added or an existing entry corrected, GitHub is the channel the site points to.

What the site says about contributing

The site's own wording is narrow and worth taking literally:

• The list is described as an "exhaustive list of all known video game randomizers."
• A heading on the page reads "Now open source!"
• Under it: "Contributors can post game requests & list updates to the GitHub repository."
• A link to "the full announcement" is provided on the site.

That is the entire documented contribution path. Anything beyond it — review timelines, formatting rules, whether requests are guaranteed to be added — is not stated on the page, so treat those as unknown rather than assumed.

What counts as a game request vs. a list update

The site draws a distinction between the two, and it matters for how you frame a submission.

The site is explicit that it does not track when randomizers themselves are updated — only when its own information about them is updated. So a "list update" is about the list's data, not about announcing a new version of someone's randomizer.

Reading the update dates before you submit

Every entry carries an "Updated" date, and the page states plainly: "We do not track when randomizers are updated, we only track when our info for them is updated."

This has a practical consequence. If you see an old date next to a game, it does not mean the randomizer is abandoned — it means the list's entry for it hasn't been touched. Before filing a list update, check whether what you're reporting is a change to the list's information (a dead link, a renamed author, a moved repository) rather than a new release of the randomizer itself.

The most recent revision shown on the page is 30 August, 2026, and individual entries carry their own dates, such as:

• Super Mario Bros. 3 — updated 2026-08-30
• Mega Man 3 — updated 2026-08-26
• GoldenEye 007 — updated 2026-08-25
• Sonic Racing: CrossWorlds — updated 2026-08-24

Where Discord fits

The page lists Discord alongside GitHub in its header links. The site does not describe what the Discord is used for or state that it accepts contributions. Treat it as a linked community channel, not as a documented submission route — the site's own instruction names GitHub specifically.

A practical submission checklist

Because the site gives no template, base your submission on what the list itself records for each entry:

1. Identify the game by the title the list would use.
2. Name the randomizer and its author, matching the style of existing entries (for example, "MottZilla's SotN Integrated Rando" or "bropacman's Shadow Man Remastered").
3. Note platform or version constraints where they exist — several entries specify them, such as "For use with the NTSC North American Playstation version" or a browser-based randomizer that "runs on Windows, macOS, Linux or mobile with nothing to install."
4. Include the link the list should point to.
5. Say whether it's a new game request or an update to an existing entry.
6. Post it to the GitHub repository, which is the channel the site names.

Common sticking points

• Submitting a randomizer update as a list update. The list doesn't track randomizer version changes, so a "new release" report may not be actionable.
• Assuming a response time. The site states no review process or turnaround.
• Using Discord as the submission channel. The site points to GitHub for requests and updates; Discord is only listed as a link.
• Expecting the list to be complete on its own. It calls itself exhaustive, but "all known" depends on people filing requests — which is exactly what the open-source setup is for.