Skip to main content

Add Translation Patch Discovery and Management

šŸ“‹ Summary

Help users discover compatible fan translation patches and associate them with games in their LaunchBox libraries.


ā— Problem

Fan translations are often distributed across project websites, forums, and repositories. Users must find the correct patch, determine which ROM revision it supports, and configure it manually.

Using the wrong ROM version can cause a patch to fail or produce a corrupted game.


šŸ’” Proposal

Allow translation patch information to be associated with games in the LaunchBox Games Database.

Patch records could include:

  • Translation language

  • Translator or project name

  • Official source page

  • Patch format and version

  • Required original ROM hashes

  • Resulting patched-game hash

  • Installation or emulator requirements

When LaunchBox detects a matching ROM, it could show compatible translations in the game details.

Users could download the patch from its official source and associate the local patch file with the game as an additional version, such as English Fan Translation.

Where the selected emulator supports non-destructive soft-patching, LaunchBox could help configure the patch without modifying the original ROM.


🧩 Use Cases

  • Discover that a Japanese game has an English translation

  • Confirm that a patch supports the user’s exact ROM revision

  • Keep the translated and original versions under one game

  • Launch a translation without permanently modifying the original ROM

  • Credit and link users to the original translation project


šŸ“¦ Benefits

  • Makes fan translations easier to discover

  • Reduces incorrect patch and ROM combinations

  • Keeps original ROM files unchanged

  • Improves organization of translated versions

  • Directs users to the translators’ official pages


āš ļø Considerations

  • The Games Database should initially store patch metadata and official links rather than hosting patch files

  • Exact ROM compatibility should be verified using hashes

  • Soft-patching should only be offered for supported emulators and cores

  • Patch redistribution should require explicit permission from its creator

  • Support for automatic downloads could be considered later for approved sources

Status: Open To Community4 comments

Log in to comment and vote

Comments4

  • AstroBob changed status to Open To Community
    Team•

    Oct 4

    Pinned

    Hi there!

    Thanks so much for submitting this request and for taking the time to explain your use case — that context is always super helpful.

    I’ve gone ahead and fleshed out the main idea using the info you provided, and I’m opening it up to the community for further discussion and feedback. Please let me know if this fleshed-out version doesn’t match your original intended request.

    Feel free to let me know if you have any extra thoughts, examples, or edge cases you think might be relevant!

    Cheers,
    The LaunchBox team

  • SMASHINGblargharghar

    •

    Oct 4

    I like this idea. It also would make my previous suggestion of adding a category for fan-translated media for the original games unnecessary which I’m not opposed to — in fact, it would make submitting fan-translated media much cleaner and simpler than what I had suggested.

    There’s a few things that aren’t completely clear to me in your proposal and I was hoping you could help me and others better understand what you’re looking to have implemented.

    • Would these fan-translation patches and links all reside under that games original DB entry? Or would you have a separate DB entry for the fan-translation version(s)

    • If you are proposing that fan-translated games have their own separate DB entry from the original game, how would a game that is fan-translated into multiple languages be handled? Separate DB entries for each language, or all languages under a single DB entry?

    My only concern is that we’ll end up with 5 or 6 listings for the same game in multiple languages - but if all fan-translation languages and hashes go under a single fan-translated DB entry for that game, I think this would be a great solution.

    I love the idea of automatic downloads of patches - to my knowledge, no such solution currently exists in any front-end manager. While I’m sure it would be quite a bit of effort for the Launchbox devs, it would certainly be a feature that sets Launchbox apart from others.

    • Darklesh

      •

      Oct 4

      Ideally, they would be hosted in the same database; they tend to be tiny in size—far smaller than the average image file. There are no technical hurdles preventing them from being downloaded just like images during the scraping process. There are dozens of sites that commonly host these patches, always linking back to the translators' original pages and providing proper credit to avoid suspicion or takedown requests. They would be treated as media sources within the same entry, identified by language tags and metadata indicating the creator and version—just like images. Something along the lines of: TRANSLATION, ENGLISH, AEON GENESIS, 1.03.

    • AstroBob

      Team•

      Oct 4

      The scope is not set, the request it’s purely up for discussion from the community right now so all implementation ideas are welcome