✅ Suggest new features, enhancements, or improvements to make our products better
🏆 Check out the existing list and vote for the most important changes
⚠️ Please check existing requests before posting to avoid duplicates
Help Us Improve LaunchBox Products!
Open To Community
Discover Game Saves Across All Compatible Emulators
📋 Summary Expand Game Saves to discover saves from every configured emulator that supports the game’s platform and Save Management, rather than only its currently assigned emulator. ❗ Problem Users may play the same game through different emulators or RetroArch cores. Checking only the assigned emulator can leave other saves undiscovered and make them harder to find after changing emulator assignments. 💡 Proposal Provide a combined Game Saves view that: Finds saves across supported emulator configurations for the selected game and its versions. Clearly identifies each save’s emulator configuration and RetroArch core, where applicable. Allows filtering by emulator while keeping existing saves and LaunchBox backups distinguishable. Avoids duplicate entries when configurations share the same save location. Preserves the source configuration of backups, even when the game’s assigned emulator changes. Restores backups through their recorded source configuration, building on the separate restore-routing fix. Provides Refresh, scan progress, and cancellation without blocking the interface. 📦 Benefits Find saves without repeatedly changing the game’s assigned emulator. Keep backups understandable when switching emulators or cores. Manage saves from multiple configurations in one place. ⚠️ Considerations Scanning should cover configured, supported integrations only, not search entire drives or every installed core. Unsupported, unavailable, or failed integrations should be identified without preventing other results from appearing. Existing backups must remain accessible. Where their original configuration cannot be identified, restoration should require a confirmed compatible destination rather than silently using the current emulator. This feature does not convert saves between incompatible emulators or cores.
Planned
Marquee functionality to assign specific monitor
It would be great if we could assigned the marquee screen to a specific device instead of just the number that is randomly assigned by windows. The current implementation is not very reliable if e.g. a third display is used, because bigbox only supports two displays. Using the third screen plugin does also not solve this, because things like screensaver mode do not work properly i.e. the plugin seems to not register the changes of screensaver mode properly. Cheers
Open To Community
Add Discord Rich Presence to LaunchBox for Android
📋 Summary Add optional Discord Rich Presence support so users can display the game they are playing through LaunchBox for Android on their Discord profile. ❗ Problem Discord activity support varies between Android emulators. Users cannot consistently share which game they are playing, particularly when their emulator has no built-in Discord integration. 💡 Proposal Add an opt-in Discord Rich Presence setting. When a game is launched through LaunchBox, the activity should display: Game title Platform Game artwork where available, with a generic fallback Keep the activity visible while the game is being played, update it when another game is launched, and clear it when the session ends or sharing is disabled. A LaunchBox Games Database match should help provide artwork, but should not be required to display the game title. 🧩 Use Cases Share what is being played on an Android handheld Display the game title when an emulator only identifies itself Provide activity sharing for emulators without native Discord support 📦 Benefits Provides a consistent sharing experience across supported emulators Makes friends’ current gaming activity easier to identify Reduces dependence on individual emulator integrations ⚠️ Considerations Sharing should be disabled by default and easy to turn off Session handling must account for returning to LaunchBox, device
Open To Community
Exclude Device Sleep from Android Playtime Tracking
📋 Summary Pause playtime tracking when an Android device sleeps, and resume tracking when gameplay resumes. ❗ Problem Putting a handheld to sleep during a game can cause the sleeping period to count toward its playtime. A short gaming session followed by several hours of sleep can therefore produce a heavily inflated total. 💡 Proposal Add Exclude Device Sleep from Playtime, enabled by default. When enabled: Stop counting time while the device is asleep Resume counting when the user resumes playing Handle multiple sleep and wake cycles within one session Preserve the time played before sleeping For example, playing for 20 minutes, sleeping for two hours, then playing for another 10 minutes should record 30 minutes.
Open To Community
Separate Play Status from Game Completion
📋 Summary Split Game Progress into two independent fields: Play Status: Whether the user is currently playing or finished with a game Completion: How much of the game the user actually completed ❗ Problem The current Game Progress field combines two different concepts. Finishing with a game does not necessarily mean completing it. A user might reach 60% of the story and decide they are finished playing, while another user might pause at the same point with plans to return. A single value cannot accurately represent both situations. 💡 Proposal Introduce two independently managed fields. Play Status Not Started Playing Paused Finished Playing Abandoned Completion Unfinished Beaten Completed Mastered Continuous or Not Applicable An optional completion percentage could provide additional detail. This would support combinations such as: Finished Playing + Unfinished Finished Playing + Beaten Playing + 60% Paused + Unfinished Abandoned + 40% Finished Playing + Mastered 🧩 Automation Automation could update each field independently: Launching a game could set Play Status to Playing Users could manually mark games as Paused, Finished Playing, or Abandoned Achievement integrations could update Completion without changing Play Status Manual selections should take priority over automatic rules 🧩 Use Cases Stop playing a game without claiming to have beaten it Pause a partially completed game and return later Finish the main story without completing every optional objective Continue playing after beating or mastering a game Track achievement completion separately from personal play status 📦 Benefits More accurately represents different playing habits Removes ambiguity between finishing and completing a game Improves backlog and active-game management Enables more useful filters, playlists, badges, and statistics Provides better information for timeline and play-history views ⚠️ Considerations Existing Game Progress values would need a clear migration path Custom progress values may require user-defined mappings Both fields should support filtering, bulk editing, playlists, badges, and syncing Completion percentages should identify whether they are manual or supplied by an external source
Open To Community
Avoid rom hack search and detection in default db search
I don't think I'm telling anyone anything new by pointing out that being so permissive with ROM hacks has turned the database into a cluttered mess of thousands of them. While these hacks are obviously of interest to many users, it is unacceptable that—when searching the database or scraping data—the original version of a game gets buried under hundreds of derivatives. I believe they shouldn't be visible or discoverable by default; instead, their visibility should be determined by a user-enabled setting within the database or application.
Improve searching by platform to avoid unwanted results due to partial matches
Problem: Because the search system works by partial matches rather than full matches, searching for “Nintendo Entertainment System” when using the “platform” tag will also display Super Nintendo Entertainment System games, which are unwanted results. Proposal: This can be curbed by instead selecting the platform from a drop-down menu. In order to keep the ability to search multiple systems at once, this theoretical drop-down menu could have the options be checkboxes.
Open To Community
Add a Community Ports, Recomps and Decomps Manager
📋 Summary Allow users to discover, install, update, and launch community-built ports, recompilations, and decompilation projects directly through LaunchBox. ❗ Problem Playable community projects are increasingly distributed through GitHub and similar services, but managing them currently involves: Finding the correct project and release Identifying the correct download Extracting and organizing its files Supplying original game data where required Manually adding the executable to LaunchBox Returning to the project page to check for updates This makes community ports difficult to discover and maintain, particularly as more projects become available. 💡 Proposal Add a curated Community Projects catalog to LaunchBox. From a game’s details, users could view compatible community versions and: Read information about the project Install the latest supported release Provide their legally obtained ROM or game data when required Launch the installed project Check for and install updates Open its installation folder Uninstall it safely Installed projects could be attached to the original game as additional launchable versions. For example, Ship of Harkinian could appear as a playable version of The Legend of Zelda: Ocarina of Time without creating an unrelated duplicate entry. 🧩 Use Cases Discover that a game in the library has a native community port Install a recompilation without manually navigating GitHub releases Choose between the emulated original and an installed native version Receive an update notification when a project publishes a new release Keep community projects organized alongside their original games 📦 Benefits Makes community ports and recompilations more accessible Reduces manual downloading and configuration Keeps related versions organized under the appropriate game Provides a consistent installation and update experience Helps users discover new ways to play games already in their library ⚠️ Considerations Version 1 should focus on: Windows-compatible packaged releases Stable releases from a trusted, curated catalog User-initiated installation and updates Projects that can be matched reliably to existing games Preserving saves and configuration files during updates Clear links to each project’s official repository LaunchBox should only download community project files. It should never distribute copyrighted ROMs or game data, and users should be prompted to provide their own files when a project requires them. Support for custom repositories, mods, prereleases, automatic updates, Linux, Android, and projects that require compilation could be considered later.
Open To Community
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
Open To Community
Add Missing Media Filters to the Audit Tool
Have the option of exporting the Audit results to an Excel file (.xlsx) and also give some filtering options to user of missing media, i.e the most common: Missing Video (shows only missing video titles) + Missing Box Art + Missing Clear Logo, etc.
Open To Community
Auto-Dim Big Box During Attract Mode
📋 Summary Add an option for Big Box to automatically dim its display after attract mode has been running for a configurable amount of time. ❗ Problem Attract mode can remain active for long periods on arcade cabinets, televisions, and home theater displays. Although users can reduce or mute attract-mode audio, the interface continues displaying at full brightness. This can be distracting in dark rooms and unnecessarily bright when a cabinet is left unattended. 💡 Proposal Add optional dimming controls to the Big Box attract mode settings. Users could configure: Whether automatic dimming is enabled How long attract mode runs before dimming The desired dimming level Big Box should gradually dim while continuing to run attract mode normally in the background. Any keyboard, mouse, or controller input should immediately restore normal brightness. 🧩 Use Cases Leave an arcade cabinet running without displaying at full brightness indefinitely Reduce distraction from a Big Box display in a home theater Keep attract mode active while making an unattended screen less prominent Restore full brightness instantly when someone approaches the cabinet 📦 Benefits Improves unattended cabinet operation Makes Big Box better suited to dark or light-controlled rooms Complements the existing attract-mode audio controls Avoids relying on monitor-specific brightness controls Keeps attract mode available without requiring the display to turn off ⚠️ Considerations Dimming should affect Big Box rather than changing the monitor’s hardware brightness The dimming overlay should work consistently across themes Normal brightness must be restored when attract mode ends or user input is received Multi-monitor users may need control over which Big Box displays are dimmed
Open To Community
New Platforms: Sharp MZ-700, MZ-1200 and MZ-1500
Add support for additional Sharp MZ computer systems to the LaunchBox Games Database. Currently, the database includes the Sharp MZ-2500, but several earlier systems from the MZ family are missing, including the Sharp MZ-700, MZ-1200 and MZ-1500. A growing amount of software for these systems has been preserved and made available, making the lack of database support increasingly noticeable for users cataloguing these libraries. Before adding them individually, we should investigate the compatibility between these systems and the wider MZ family to determine whether they should be represented as separate platforms or grouped under a broader Sharp MZ platform. Requirements Investigate the MZ-700, MZ-1200 and MZ-1500 and their compatibility with other Sharp MZ systems Determine whether each meets our criteria for a distinct platform Consider whether closely compatible systems should instead be grouped into a single Sharp MZ platform Ensure games currently missing from the database, including Sharp MZ versions of titles such as Pac-Man, can be correctly represented Keep the existing Sharp MZ-2500 platform separate if it represents a distinct hardware and software ecosystem
Open To Community
Download EmuMovies Media During Automatic Imports
📋 Summary Allow automatic ROM imports to download selected media from EmuMovies alongside LaunchBox Games Database media. ❗ Problem Games added through automatic import do not automatically receive EmuMovies media. Users must run a separate media download afterward to obtain items such as gameplay videos and manuals. This makes automatic importing feel incomplete and creates repetitive work for users who regularly add games to monitored folders. 💡 Proposal Add EmuMovies options under the existing automatic import media settings. Users with a configured EmuMovies account could choose which supported media types should be downloaded automatically, including: Gameplay videos Video themes Manuals Music Supported images These preferences should be applied whenever new games are detected and imported automatically. 🧩 Use Cases Add ROMs to a monitored folder and receive their videos automatically Import a few games regularly without running a second media download Automatically collect manuals alongside existing LaunchBox media 📦 Benefits Makes automatic imports more complete Eliminates a repetitive second download step Keeps newly imported games consistent with the rest of the library Provides more control over automatic media downloads ⚠️ Considerations EmuMovies downloads should require a valid configured account Existing media should not be replaced unless the user enables that behavior EmuMovies errors or unavailable media should not prevent the game from importing Automatic download limits should also apply to EmuMovies media where appropriate
Open To Community
Import Manuals and Documents into LaunchBox
📋 Summary Add an option to copy locally added manuals and documents into LaunchBox’s managed folders instead of only linking to their original locations. ❗ Problem When users select or automatically discover a local manual or document, LaunchBox may continue referencing the file from its original location. If that file is moved, renamed, or deleted, the document becomes unavailable in LaunchBox. This also makes portable installations and library transfers less reliable. 💡 Proposal When adding a manual or document, allow users to choose between: Copy the file into LaunchBox Keep the file in its current location Files copied into LaunchBox should be organized into appropriate platform folders and referenced using portable paths. The option should apply to files found during game imports as well as files added through game or platform editing. 🧩 Use Cases Keep manuals available after cleaning up the original ROM folder Move a LaunchBox installation without losing linked documents Maintain one organized location for game-related media Prevent links from breaking when source folders change 📦 Benefits Improves library portability Reduces broken manual and document links Provides more consistent media management Makes backups and migrations more reliable ⚠️ Considerations Copying should not delete or move the original file Users should be able to retain externally managed document libraries Duplicate filenames and existing files should be handled safely A future migration tool could copy existing externally linked documents into LaunchBox
Open To Community
Refresh “Continue Playing” During Big Box Sessions
📋 Summary Automatically refresh the Discovery Center’s Continue Playing section after a game is launched from Big Box. ❗ Problem Games played during the current Big Box session do not immediately appear in Continue Playing. The section only reflects the updated play history after Big Box is restarted. This is particularly inconvenient for users who leave Big Box running continuously. 💡 Proposal Refresh Continue Playing whenever the user returns to or reopens the Discovery Center after launching a game. The refreshed section should: Add newly played games Move replayed games into the correct position Preserve the existing sorting and filtering Update regardless of where the game was launched within Big Box Avoid duplicate entries 🧩 Use Cases Returning to the Discovery Center after finishing a game Quickly resuming a game played earlier in the same Big Box session Keeping an always-running arcade or living-room setup up to date 📦 Benefits Keeps Continue Playing accurate throughout the session Removes the need to restart Big Box Makes recently played games immediately accessible Better matches user expectations for dynamic Discovery Center content ⚠️ Considerations Refreshing should occur when the Discovery Center becomes active rather than continuously The update should not unnecessarily rebuild unrelated Big Box views
Completed
Can't search for "&" character
An "&” character in a search terminates the string. For example, search for: plat:Game & Watch This will result in a search for: plat:Game
Open To Community
Add Hierarchical Categories to More Metadata Fields
📋 Summary Allow hierarchical, collapsible values in additional metadata fields using the same structure currently supported by Genres. ❗ Problem Genres can be organized using values such as: Role-Playing / Action RPG This creates a parent category with a collapsible subcategory. Other fields, including Series and custom fields, currently appear as flat lists even when users need several related values. Large collections can therefore produce long and difficult-to-navigate filter lists. 💡 Proposal Extend hierarchical value support to other compatible metadata fields, particularly: Series Custom fields Play Mode Other multi-value fields displayed in the sidebar Users could enter values such as: Final Fantasy / Main Series Collection / Fan Translations Multiplayer / Cooperative LaunchBox would display these as collapsible parent and child entries throughout applicable filters. 🧩 Use Cases Organize a large franchise into main games, spin-offs, and remakes Create structured custom categories for hacks, translations, or collections Group related values without filling the sidebar with separate entries Browse large libraries using more meaningful hierarchies 📦 Benefits Improves navigation in large collections Makes custom fields significantly more flexible Provides consistent organization across metadata fields Reduces clutter in sidebar filter lists ⚠️ Considerations Hierarchies should only apply to fields where nested values make sense Existing values containing slashes must continue to work correctly Editing, filtering, and bulk editing should recognize the same hierarchy Parent selections should optionally include items assigned to their child values
Open To Community
Add a Game Soundtrack Music Player
📋 Summary Add a dedicated music player for game soundtracks inside LaunchBox and Big Box. ❗ Problem LaunchBox can already play game music, but soundtrack support is limited compared to a full music player experience. Users may have full albums or soundtrack collections for their games, but there is no dedicated way to browse and play multiple tracks as an album from within LaunchBox. 💡 Proposal Add a soundtrack music player that allows users to attach multiple audio files or albums to a game. Supported features could include: Multiple tracks per game Album or soundtrack folders MP3, FLAC, WAV, OGG, and other common formats Play, pause, next, previous, shuffle, and repeat controls Track list display from the game details view Optional Big Box support for controller-friendly playback 🧩 Use Cases Listen to a full game soundtrack from the game details page Attach OST albums to favorite games Browse and play music collections in Big Box Use LaunchBox as a lightweight game music library 📦 Benefits Expands existing game music support Makes soundtrack collections easier to enjoy Adds value for users who collect game OSTs Improves LaunchBox as a media-rich game library ⚠️ Considerations This should build on existing game music support rather than replace it. A first version could focus on multiple tracks per game and simple playback controls before expanding into broader music library features.
Open To Community
Add Platform Filters to the Moderation Queue
📋 Summary Add platform show/hide filters to the LaunchBox Games Database moderation queue. ❗ Problem Moderators often have platforms they are more familiar with, and others they are not interested in or do not feel qualified to review. Currently, they may need to repeatedly skip submissions for platforms they do not want to moderate, which slows down the process and adds unnecessary friction. 💡 Proposal Allow users to configure platform filters for the moderation queue. This could support: Showing only selected platforms Hiding selected platforms Saving the filter preferences per user Quickly editing or clearing the platform filter list 🧩 Use Cases A moderator focuses only on platforms they know well A user hides platforms they do not want to review Moderators avoid repeatedly using “Skip for 24 hours” on the same platforms Database changes are reviewed by users with more relevant knowledge 📦 Benefits Speeds up moderation Improves review quality Reduces repetitive skipping Lets contributors focus on areas where they have expertise Makes the moderation queue more pleasant to use ⚠️ Considerations Filters should not permanently remove items from the queue. They should only customize what each moderator sees, and users should be able to reset or adjust them at any time.
Open To Community
Expand Android Storefront Import Support
📋 Summary Add broader storefront-style import support to LaunchBox for Android, similar to the storefront integrations available in LaunchBox for Windows. ❗ Problem Users may have Android games installed from multiple sources, such as: Google Play Amazon Appstore Epic Games Other Android app stores Currently, it can be difficult to organize these games together in LaunchBox for Android with storefront-aware metadata and media. Users who already use LaunchBox on Windows expect a similar experience where games from multiple sources can be collected into one library. 💡 Proposal Expand Android storefront import support so LaunchBox for Android can better detect and import games from Android storefronts. For supported stores, this could include: Importing installed games from each storefront Identifying which storefront a game came from Applying storefront-specific metadata or media where available Updating imported Android games when new games are installed Launching imported Android games directly from LaunchBox A later version could explore importing owned-but-not-installed games if a storefront provides reliable access to that library. 🧩 Use Cases Import Google Play games into LaunchBox for Android Import Amazon Appstore games on Android devices Import Epic Games Android titles View Android-native games alongside emulated platforms Keep Android games organized in one frontend across handhelds, tablets, and Android TV devices 📦 Benefits Makes LaunchBox for Android feel closer to the Windows experience Improves organization for native Android games Reduces manual setup for Android storefront games Supports users with games from multiple Android stores Makes Android devices better all-in-one gaming frontends ⚠️ Considerations Some storefronts may limit access to owned library data, install source information, metadata, or media. Version 1 should focus on reliably importing installed Android games, with deeper storefront account integration considered separately where technically possible.