📋 Summary Allow user created custom fields to be added as selectable columns within the LaunchBox game list view, alongside existing built in metadata columns. ❗ Problem LaunchBox currently supports custom fields for storing additional metadata, but these fields cannot be surfaced directly as columns in the main game list view. This limits their usefulness for users who rely on custom metadata for organization, filtering, workflows, or collection management. At the moment: Custom fields can only be viewed inside Edit Metadata windows Users cannot quickly scan or sort by custom field values in the game list Workflows relying on custom metadata become cumbersome for large collections 💡 Proposal Extend the game list column system to support custom fields. Features could include: Add custom fields to the existing column selector menu Support sorting by custom field values Preserve custom column layouts across views and theme

Retrofrogg 1 day ago

2

LaunchBox for Windows

📋 Summary Add the RetroRatio stat to the RetroAchievements section of the Game Details pane alongside the existing beaten and mastered playtime commitment information. ❗ Problem LaunchBox currently displays useful RetroAchievements stats such as: Beaten time commitment Mastered time commitment However, an important metric is missing: RetroRatio For many achievement hunters, RetroRatio is one of the most important factors when deciding what game to play next, as it helps indicate the score value and challenge relative to the time investment required. Without it, users must leave LaunchBox and check the RetroAchievements website manually. 💡 Proposal Add RetroRatio information to the Game Details pane: Display RetroRatio alongside: Beaten hours Mastered hours Pull the value directly from RetroAchievements data Present it in a clean, glanceable format within the existing RetroAchievements details section 🧩 Use Cases A user quickly evaluates whether a game is “worth hunting” before starting Achievement hunters compare challenge vs reward at a glance Users choose games based on both time commitment and score efficiency LaunchBox becomes a more complete RetroAchievements browsing experience 📦 Benefits Adds another highly valuable RetroAchievements metric Reduces need to manually check the RetroAchievements website Improves game discovery for achievement hunters Makes the Game Details pane more informative and useful ⚠️ Considerations Should fit cleanly into the existing RetroAchievements UI Needs reliable syncing with RetroAchievements metadata Could potentially be expanded with additional RA stats in the future

FurabioS 4 days ago

2

LaunchBox for Windows

📋 Summary Add the ability to sort platforms based on the release date of the platform itself, rather than the release dates of the games within it. ❗ Problem Currently, the generic “Release Date” sorting only applies to games: Users cannot sort platforms chronologically by when the hardware launched Difficult to browse gaming history in timeline order Exploring the evolution of gaming systems is cumbersome Existing platform sorting options do not support historical ordering While users can manually assign a custom Sort Title / Sort Order to platforms, this is entirely manual and becomes tedious to maintain for larger collections. 💡 Proposal Add a dedicated platform release date sorting option: Introduce: Platform (Release Date) Or Sort Platforms by Release Date Place it alongside existing filters such as: Platform Platform Category Use the platform’s actual hardware release date for sorting automatically 🧩 Use Cases A user browses systems from oldest to newest A user explores the “history of video game systems” chronologically Collections can be organized by gaming generation naturally Retro focused users get a more historically accurate browsing experience Users avoid maintaining large manual sort order lists ⚠️ Considerations Requires consistent platform release date metadata Could support ascending and descending sorting Should integrate cleanly with existing platform filters and views

TsikZak 6 days ago

3

LaunchBox for Windows

I recently came across this system whilst browsing some old catalogs and decided to add it to my LB collection. The console was produced by Memorex and distributed in collaboration with Tandy in the early 90’s. It took me a couple of weeks but I managed to locate covers, snaps and other media items for all the released software (about 50 CD’s). The system was similar in concept to the Philips CDi and 3D0 in that it was mainly educational/informational multimedia but had a few games. The VIS stands for “Video Information System”. I am using MAME as the emulator and it runs the software flawlessly. So I would like to share all of this unique and now complete collection with the LB community but am unsure how to do this. If one of the devs creates a new entry in the database I will happily upload all items and metadata to the new entry.

k1w1b1rd 8 days ago

LaunchBox Games Database

📋 Summary Add support for consumer cloud storage providers on Android, allowing users to access ROM collections stored in services such as Google Drive across multiple devices without relying on a self hosted NAS. ❗ Problem LaunchBox Android already supports NAS based libraries, but this requires users to: Own and maintain a NAS device Configure networking and remote access Keep a home server powered and available For many Android users, this is unrealistic or overly complex. At the same time: Android devices often have limited internal storage Users commonly own multiple handhelds, phones, or tablets ROM collections must currently be duplicated across devices Keeping libraries synchronized manually is tedious This creates a much bigger pain point on Android than on Windows PCs, where large local storage is far more common. 💡 Proposal Expand Android storage support to include consumer cloud providers: Allow LaunchBox Android to connect to: Google Drive Dropbox Microsoft OneDrive Enable users to: Browse ROMs directly from cloud storage Stream or temporarily cache games locally Share one centralized library across multiple Android devices Optionally support: Offline caching of favorite games Smart cache cleanup Future LaunchBox managed cloud storage solutions 🧩 Use Cases A user keeps a retro ROM library in Google Drive and accesses it from multiple Android handhelds A user avoids manually copying ROMs between devices A user without a NAS still benefits from centralized storage Smaller ROM collections become instantly portable across Android devices 📦 Benefits Makes centralized libraries accessible to far more users Removes the barrier of needing NAS hardware Reduces storage duplication across Android devices Improves convenience for handheld and mobile users Better suits the portable nature of Android gaming ecosystems ⚠️ Considerations Some emulators may require temporary local caching Network reliability and offline usage should be considered Clear cache management controls would be important Secure authentication handling for cloud providers is required ✅ Outcome Cloud storage provider support would make LaunchBox Android far more flexible and accessible, giving users a simple way to maintain one centralized game library across all their Android devices without requiring dedicated server hardware.

AstroBob 9 days ago

1

LaunchBox for Android

📋 Summary Improve how the main LaunchBox window scales and adapts on smaller, lower-resolution, portrait, handheld, streamed, and unusual display configurations. ❗ Problem The main LaunchBox window does not always scale or reflow properly when horizontal space is limited: The internal layout appears constrained below roughly 1440px wide On 1280x800, 1280x720, and some 1080p displays, content may not fit correctly Users may need to drag the window wider than the screen to see all information On vertical or portrait displays, top bar menu items can overlap each other Windows DPI scaling overrides do not appear to resolve the issue This creates friction for users on handhelds, streamed displays, virtual monitors, lower-resolution screens, and portrait setups. 💡 Proposal Update the main LaunchBox window to use a more responsive layout system: Allow the main window content to adapt below 1440px width Reduce fixed-width constraints where possible Let sidebars, game details panels, and central content shrink or collapse intelligently Prevent top bar items from overlapping on narrow or portrait displays Add overflow behavior for top bar menus and actions when space is limited Improve support for Windows DPI scaling and mixed display configurations Ensure layouts behave consistently across landscape and portrait orientations 🧩 Use Cases A user streams LaunchBox to a Steam Deck using Moonlight at 1280x800 A user runs LaunchBox on a 720p or compact 1080p display A user places LaunchBox on a vertical secondary monitor A handheld PC user launches and manages games without switching resolution A living room setup uses a virtual or non-standard display size 📦 Benefits Improves usability on modern handheld and streaming setups Better supports portrait and secondary monitor workflows Reduces the need for manual resizing or DPI workarounds Prevents menus and content from overlapping or being pushed off-screen Makes LaunchBox feel more polished across a wider range of displays ⚠️ Considerations Existing themes may rely on fixed layout assumptions Top bar overflow behavior should preserve access to all menu items Sidebar and game details resizing should avoid hiding important content unexpectedly Changes should be tested across common resolutions, DPI settings, and aspect ratios ✅ Outcome Improved LaunchBox window scaling would make the main interface more reliable, flexible, and comfortable to use across small screens, portrait displays, handheld devices, streamed sessions, and non-standard monitor setups.

AstroBob 9 days ago

LaunchBox for Windows

📋 Summary Allow multiple instances of LaunchBox to run simultaneously on the same system. ❗ Problem LaunchBox currently only allows a single active instance: Users cannot run multiple builds side by side Difficult to test different versions or configurations Limits workflows for developers, testers, and advanced users Requires fully closing one setup before opening another This creates friction for users maintaining separate environments. 💡 Proposal Add support for multiple concurrent LaunchBox instances: Allow separate LaunchBox installs to run simultaneously Ensure each instance maintains: Independent settings Separate databases Separate plugins and media paths Optionally include: Warning if two instances point to the same data folder Command line option to force multi-instance mode 🧩 Use Cases A user tests a beta build alongside a stable build A user maintains separate setups for arcade and console collections A developer tests plugins across different environments A content creator records or experiments without affecting their main build 📦 Benefits Improves testing and development workflows Supports advanced multi-build setups Reduces friction when experimenting with new versions Gives users greater flexibility in managing their environments ⚠️ Considerations Could require protections against conflicting writes Plugins and background services may need isolation between instances

AstroBob 13 days ago

LaunchBox for Windows

📋 Summary Add the ability to exclude files from automatic imports based on filename rules, such as ignoring BIOS files, tools, or other non-game entries. ❗ Problem Automatic imports currently bring in everything that matches the source folders: BIOS files and system files are imported as games Utility programs and non-playable content clutter the library No way to define rules to ignore certain files Users must manually clean up unwanted entries after import This reduces the usefulness of automatic imports, especially with curated sets. 💡 Proposal Introduce import filtering rules: Allow users to define ignore rules based on: Filename text (e.g. bios, test, program) File patterns or tags Apply these rules during: Automatic imports Manual imports (optional) Provide a simple UI to: Add, edit, and remove filters Optionally include: Presets for common exclusions (e.g. BIOS files) 🧩 Use Cases A user excludes BIOS files from No-Intro sets ROM management tools produce files not intended for LaunchBox A user filters out utilities or test ROMs Automatic imports stay clean without manual cleanup 📦 Benefits Cleaner game libraries Reduces manual maintenance Improves accuracy of automatic imports Better compatibility with ROM management tools ⚠️ Considerations Rules should be flexible but easy to understand Must avoid accidentally filtering valid games Could be expanded to support more advanced filtering in the future ✅ Outcome Import filtering ensures only relevant games are added to the library, making automatic imports more reliable and efficient.

HanzJWeasel 21 days ago

2

LaunchBox for Windows

📋 Summary Add an option to generate 3D box art directly from the 3D Model Viewer by capturing the current model view with a clean or transparent background. ❗ Problem Users can create custom 3D box art using the 3D Model Viewer, but the process is manual: Users must take screenshots themselves Background cleanup may be required afterward Creating consistent 3D box images takes extra time Bulk or repeated creation is cumbersome 💡 Proposal Add a capture button to the 3D Model Viewer: Capture the current 3D model angle Use a blank or transparent background Save the result as a 3D box image for that game Optionally allow users to choose output format and resolution 🧩 Use Cases A user creates missing 3D box art for a custom game A user captures consistent 3D boxes across a platform Theme creators quickly generate clean preview assets Users avoid manual screenshots and background editing 📦 Benefits Speeds up 3D box art creation Produces cleaner and more consistent assets Reduces reliance on external image editing tools Makes the 3D Model Viewer more useful for media creation ⚠️ Considerations Should preserve the user’s selected rotation and zoom Transparent background support would be useful for themes Could later support batch generation using default angles ✅ Outcome Generating 3D box art directly from the model viewer streamlines custom media creation and makes it easier to fill gaps in users’ collections.

EderatorEdhead 21 days ago

2

LaunchBox for Windows

We’re aware of an issue where GOG poster images may not download during a GOG game import, even when the GOG Poster image type is selected. What happens: After completing a GOG import, imported games may be missing their GOG Poster image. Expected behavior: When GOG Poster is selected during import, LaunchBox should download the GOG poster/box art and save it to the game’s images. We’re looking into the issue. In the meantime, other selected media types may still download normally.

AstroBob 22 days ago

1

Known Issue

+1

🐛

Bug Report

📋 Summary Add support for viewing manuals in Open Document Format (ODF), such as.odt, alongside existing formats like PDF and RTF. ❗ Problem Manual support is currently limited to a small set of formats: ODF files (e.g..odt) are not supported Users creating their own manuals cannot use this format Requires manual conversion to PDF or RTF Adds friction for users who prefer open or editable formats This limits flexibility for user created content. 💡 Proposal Expand supported manual formats: Add support for: .odt (OpenDocument Text) Ensure manuals can: Be opened from LaunchBox and Big Box Display correctly in the built-in viewer (or supported external viewer) Optionally allow users to choose a preferred application for opening unsupported formats 🧩 Use Cases A user creates custom manuals in.odt format A user prefers open formats over PDF Manuals are stored and viewed without needing conversion Community shared manuals can use a wider range of formats 📦 Benefits Greater flexibility for manual creation and usage Reduces need for file conversion Supports open standards Improves compatibility with user generated content ⚠️ Considerations May require integration with external viewers Rendering consistency should be considered Could be extended to other document formats in the future

erling1000 25 days ago

1

LaunchBox for Windows

📋 Summary Add the ability to merge (combine) and split (expand) games directly from the game list on the Android version of LaunchBox. ❗ Problem While this functionality exists on Windows, it is missing on Android: Users cannot merge games after import on Android No way to split previously merged titles Managing multiple regions or duplicate entries is difficult Libraries become cluttered and harder to organize This creates an inconsistent experience between platforms. 💡 Proposal Bring merge and split functionality to Android: Allow users to: Select multiple games and Combine Games Select a combined entry and Expand Games Support common use cases like: Merging different regions of the same game Cleaning up duplicate entries Optionally include: Long-press multi-select workflow Clear UI actions for combine and expand 🧩 Use Cases A user imports US and JP versions of a game and merges them A corrected metadata match should be merged with an existing title A user wants to split previously merged games back into individual entries Large Android libraries are cleaned up and organized more efficiently 📦 Benefits Brings feature parity between Windows and Android Improves library organization on mobile devices Reduces duplicate entries and clutter Supports multi-region workflows more effectively ⚠️ Considerations UI should be intuitive for touch controls Needs to handle large selections efficiently Should clearly indicate when games are combined ✅ Outcome Adding merge and split functionality to Android ensures consistency across platforms and gives users better control over organizing their game libraries on mobile devices.

Eyebrows Cat 27 days ago

4

LaunchBox for Android

Description: When manually adding a single game, the Platform field currently behaves as a freeform/editable field that only suggests platform names already present in the user’s library. If the desired platform does not already exist, it must be entered manually. I would like to request that this field use LaunchBox’s supported/canonical platform list instead, so users can select the platform from a standardized picker when adding a single game. Why this would help: Reduces typos and naming inconsistencies Makes manual game entry faster and easier Helps keep platform names aligned with LaunchBox’s supported platforms Improves metadata matching and emulator/platform association reliability Current behavior: When importing or manually adding a single game, the platform must be typed manually unless that exact platform name already exists in the library. Requested behavior: Provide a selectable drop-down or searchable picker populated from the supported platform list, while still optionally allowing custom manual entry if needed. That would make the single-game add flow more consistent with the rest of the import experience and easier for users who are adding games one at a time.

Eyebrows Cat 27 days ago

1

LaunchBox for Android

LaunchBox currently has partial support for archived games during RetroAchievements scans. .7z archives are already handled by temporarily extracting the archive and attempting to hash a game file from inside it. However, this same scan-time handling does not appear to apply consistently to other archive formats, such as .zip and .rar. As a result, games in those archive formats may fail to match during a RetroAchievements scan, even though the emulator can identify them correctly once the game is launched. The request is to expand LaunchBox’s RetroAchievements scan support so archived games are handled consistently across supported archive formats: Already supported: .7z archives are temporarily extracted during the RetroAchievements scan. Not fully supported: .zip and .rar archives do not appear to receive the same scan-time extraction and matching behavior. Remaining gap: some archive layouts may still fail if LaunchBox does not select the same game file that the emulator uses. Ideally, LaunchBox would use the same general approach for all supported archive formats: temporarily extract the archive during the RetroAchievements scan, identify the correct game file inside, hash that file for RetroAchievements matching, and then clean up the temporary files. This would let users keep games compressed while still allowing LaunchBox to display and track RetroAchievements data reliably.

duerra 27 days ago

3

LaunchBox for Windows

📋 Summary Add the ability to filter games based on the emulator they are assigned to within LaunchBox. ❗ Problem There is currently no way to easily view or manage games by emulator: Users cannot filter games assigned to a specific emulator Difficult to identify which games use a particular emulator or emulator version No visibility in audit tools for emulator usage Managing multi-emulator setups becomes cumbersome This makes troubleshooting and library organization more difficult. 💡 Proposal Introduce emulator based filtering and auditing: Add Emulator as a filter option in the game list Allow users to: View all games assigned to a specific emulator Filter by emulator version where applicable Include emulator data in the Audit tool/report, such as: Emulator name Associated platform Game count per emulator 🧩 Use Cases A user wants to see all games using SNES9x A user audits which titles are using a specific version of MAME or DOSBox-X A user migrates games from one emulator to another A user troubleshoots emulator specific issues across their library 📦 Benefits Improves visibility and control over emulator assignments Simplifies troubleshooting and cleanup workflows Enhances support for multi-emulator setups Makes audit tools more powerful and informative ⚠️ Considerations Should account for platform level vs game level emulator assignments UI should remain simple when handling multiple emulator versions Needs to integrate cleanly with existing filter and audit systems

Vesos! about 1 month ago

4

LaunchBox for Windows

📋 Summary Add a “ROM Name” field within the Edit Metadata window to allow users to rename ROM files directly for improved scraper recognition and consistency. ❗ Problem When ROM filenames are slightly incorrect: Scrapers fail to recognize the game Users must manually rename files outside of LaunchBox Small issues like spacing or special characters cause mismatches Rescanning can repeat the same issue if filenames aren’t corrected This creates unnecessary friction in the import and metadata workflow. 💡 Proposal Introduce a ROM renaming option in Edit Metadata: Add a “ROM Name” field beneath the Title Allow users to edit and rename the underlying file directly Ensure changes update the file on disk Optionally provide: Validation or warnings before renaming Support for batch renaming in the future 🧩 Use Cases A user corrects Disgaea3.iso → Disgaea 3.iso for proper scraping A game with special characters is renamed to match database standards A user avoids leaving LaunchBox to fix minor filename issues Rescans correctly identify games after renaming 📦 Benefits Improves scraper accuracy Reduces manual file management Streamlines metadata correction workflow Saves time when managing large libraries ⚠️ Considerations Must safely handle file renaming operations Should warn users about potential file path conflicts Needs to account for read only locations or permission issues ✅ Outcome Allowing ROM renaming directly within LaunchBox simplifies the correction process, improving scraping accuracy and overall user experience.

Dunkler2Engel about 1 month ago

3

LaunchBox for Windows

📋 Summary Allow users to reset or clear their cloud synced game statistics, giving them control to resolve sync issues or start fresh. ❗ Problem The current cloud stats system has no way to reset server data: Cloud stats can overwrite newer local progress when re-enabling sync No option to clear or reset cloud stored values Users can become stuck with incorrect or outdated data Only workaround is to manually fix values or abandon sync This creates frustration, especially when sync behaviour is unclear or incorrect. 💡 Proposal Introduce a cloud stats reset option: Allow users to: Clear all cloud stored game stats Optionally reset stats for individual games Provide this option within: LaunchBox settings Or user account / cloud settings Include confirmation prompts to prevent accidental data loss Optionally allow: “Reset and use local data” on next sync 🧩 Use Cases A user wants to fix incorrect cloud synced playtime A user switches devices and wants a clean sync state Sync issues cause mismatched or duplicated stats A user prefers to restart tracking from scratch 📦 Benefits Gives users control over their cloud data Resolves sync conflicts and inconsistencies Reduces support requests around stats syncing Improves trust in the cloud sync system ⚠️ Considerations Must clearly communicate that data will be permanently deleted Should include safeguards to prevent accidental resets May need to consider partial vs full reset options ✅ Outcome Providing a way to reset cloud stats gives users a reliable escape hatch for sync issues, improving confidence and usability of the system.

AstroBob about 1 month ago

LaunchBox Games Database

📋 Summary Allow users to request or suggest new platforms directly during the submission process when an appropriate platform does not already exist. ❗ Problem Contributors currently face friction when submitting content for unsupported platforms: No way to request a new platform during submission Submissions are rejected due to missing platform support Contributors are unsure where to submit edge case content Platform requests require separate forum posts or workflows This creates confusion and discourages contributions, especially for niche or emerging systems. 💡 Proposal Integrate platform requests directly into the submission flow: When selecting a platform: Provide an option like “Request New Platform” Allow users to submit: Platform name Basic description or context Queue platform requests for review Notify users when the platform is approved and available Optionally allow users to continue their submission once the platform is created 🧩 Use Cases A user submits content for a niche handheld or emulator based system A contributor encounters a missing platform and requests it immediately Platform requests are tied directly to real submission needs Users avoid needing to leave the flow to post on forums 📦 Benefits Reduces friction in the submission process Encourages contributions for new and niche platforms Streamlines platform request workflow Improves overall database coverage ⚠️ Considerations Requires moderation or approval workflow for new platforms Should prevent duplicate or low quality platform requests Platform creation may still need validation before being added ✅ Outcome Allowing platform requests during submission creates a smoother, more intuitive workflow, helping expand database coverage while reducing contributor friction.

AstroBob about 1 month ago

LaunchBox Games Database

📋 Summary Introduce automatic and assisted duplicate detection for media to reduce redundant uploads and improve database cleanliness. ❗ Problem Duplicate media is a recurring issue: Identical or near identical images are uploaded multiple times Duplicate entries clutter media categories Moderators must manually identify and resolve duplicates Users may download redundant or unnecessary assets This leads to inefficiency and reduced data quality. 💡 Proposal Implement duplicate detection systems: Detect duplicates during upload using: File hashing Image similarity checks Prompt users when a potential duplicate is found Allow moderators to: Flag and merge duplicates Easily remove redundant entries Optionally suggest replacing lower quality images with higher quality versions 🧩 Use Cases A user is warned before uploading an identical image A higher quality version replaces an existing lower quality image Moderators quickly resolve duplicate submissions Media categories remain clean and organized 📦 Benefits Reduces clutter and redundancy Saves moderation time Improves overall media quality Creates a cleaner and more efficient database ⚠️ Considerations Needs tolerance for small differences between images Should avoid blocking legitimate variations UI should clearly explain duplicate warnings ✅ Outcome Duplicate detection improves data quality and efficiency, reducing clutter while making moderation and uploads more streamlined.

AstroBob about 1 month ago

LaunchBox Games Database

📋 Summary Allow users to save incomplete submissions and return to them later, rather than requiring everything to be submitted in a single session. ❗ Problem The current submission flow requires users to complete everything at once: Large or complex submissions take significant time Contributors may lose progress if they leave or refresh No way to gradually build high quality submissions Discourages contributions for more detailed or niche entries This creates friction and reduces contribution quality. 💡 Proposal Introduce draft support for submissions: Allow users to: Save submissions as drafts Return and edit later Support drafts for: Game entries Media uploads Metadata edits Provide a simple “My Drafts” section for management Allow users to submit once ready 🧩 Use Cases A contributor gathers metadata over multiple sessions A user uploads media gradually instead of all at once A detailed submission is refined before being submitted Contributors avoid losing progress due to interruptions 📦 Benefits Encourages higher quality submissions Reduces frustration and lost work Supports more complex contributions Improves overall contributor experience ⚠️ Considerations Draft storage and cleanup policies may be needed UI should clearly distinguish drafts from submitted items Should remain simple and lightweight ✅ Outcome Draft support allows contributors to work more flexibly, leading to better quality submissions and a smoother contribution experience.

AstroBob about 1 month ago

LaunchBox Games Database