📋 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 3 days ago

📋 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 7 days ago

📋 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 14 days ago

2

📋 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 15 days ago

2

📋 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 18 days ago

1

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 21 days ago

3

📋 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! 24 days ago

4

📋 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 24 days ago

3

This is dependant on @Tag-Based Media System for Flexible Asset Classification in order for it to be useful 📋 Summary Allow users to filter and control media downloads based on more advanced criteria, such as quality, type, and source, improving customization and predictability. ❗ Problem Current media download controls are limited: Users can only prioritize by media type and region No way to exclude specific types of content, for example: Fanart AI generated images Low quality assets Downloads can include unwanted or inconsistent media Users must manually clean up after scraping This results in a less controlled and often frustrating experience. 💡 Proposal Expand media filtering and download preferences: Integrate with the tagging system to allow: Include or exclude tags such as Fanart, Reconstructed, AI Generated Add additional filtering options: Minimum resolution or quality thresholds Preferred image formats or sources (optional) Allow users to: Define stricter download rules Save custom media preference profiles 🧩 Use Cases A user downloads only official, high quality media A user excludes AI generated or fanart content A collector prefers reconstructed or cleaned assets for consistency Users avoid manual cleanup after scraping 📦 Benefits Gives users full control over their media Reduces unwanted downloads and cleanup effort Improves overall user experience Complements the tagging system ⚠️ Considerations Requires integration with tagging and metadata systems UI should remain simple despite added complexity Default settings should work well for most users ✅ Outcome Advanced filtering gives users precise control over their media downloads, creating a more predictable and customizable experience.

AstroBob about 1 month ago

Description: As a user, I want the ability to view and manage the version of manually installed emulators within the Manage Emulators interface, so that I have better control and visibility over the versions installed on my machine. Acceptance Criteria 1. Version Field in Edit Emulator Modal Add a free-form text field labeled Version to the Edit Emulator modal. The field shall support up to 32 characters (final limit TBD) and allow all standard text input. The field shall be: Enabled and editable for manually managed emulators (i.e., not managed by LaunchBox plugins). Auto-populated and read-only for plugin-managed emulators. If the selected executable contains version metadata: The field shall be auto-populated with the detected version. The user shall still be able to edit the value (for manually managed emulators only). 2. Executable Version Detection When an executable is added or updated in the modal, the system shall attempt to detect and retrieve its version metadata. This detection may occur: During file selection, or During the save operation (final behavior TBD). The detection method shall align with the existing approach used by LaunchBox plugins. No external or offsite services shall be used for version detection of manually managed emulators. 3. Version Display in Manage Emulators View The existing Version column in the Manage Emulators view shall be leveraged. For manually managed emulators: The Version column shall display the value from the Version field in the Edit Emulator modal. If no version is defined or detected, the field may remain empty or display a default value (TBD). For plugin-managed emulators: Existing behavior shall remain unchanged. The Version column shall remain read-only. Note / Justification Quality-of-life improvements like this reduce reliance on external tracking methods and make it easier for users to manage emulator versions directly within the LaunchBox ecosystem.

Bloodd Trail about 1 month ago

📋 Summary Create a web based high score hub where users can view, share, and optionally publish both LaunchBox leaderboard scores and their own local high scores online. ❗ Problem LaunchBox already supports high scores within the application, but visibility is limited: Scores are primarily viewed locally inside LaunchBox There is no dedicated online space to browse or share them Users cannot easily showcase their own high score activity outside the app Local high scores and LaunchBox leaderboard scores are not presented in a unified, shareable way This limits the social and community potential of the feature. 💡 Proposal Create an online high score website or web portal with support for: Public LaunchBox leaderboards View scores online by game Browse players, rankings, and recent activity Optional personal high score pages Let users upload or sync their own local high scores Keep these private by default, with an option to publish them Customizable presentation Use game media such as fanart or backgrounds for visual flair Display scores in a clean, themed profile or leaderboard format 🧩 Use Cases A user wants to publicly show off their best scores online A player browses LaunchBox leaderboards without opening the app A user keeps local scores private, but chooses to publish selected ones High score pages become a showcase for arcade cabinets or personal collections 📦 Benefits Expands high scores into a more social and community driven feature Gives users a way to share achievements outside of LaunchBox Makes leaderboards more accessible and engaging Adds value to both local and cloud based score tracking ⚠️ Considerations Privacy controls should be clear and user controlled Local score uploads should be opt in Public and private score types should be clearly separated Needs a clean visual design that works well with existing game media

DemmyTree about 1 month ago

2

📋 Summary Add an option in Big Box to use a custom folder of videos for the screensaver, allowing users to play personal content such as music videos or curated clips. ❗ Problem The Big Box screensaver currently relies on game related media: Users cannot easily use their own video collections There is no way to point the screensaver to a custom directory This limits personalization for setups like arcade cabinets or living room displays Users who want a more tailored experience must rely on external tools or workarounds. 💡 Proposal Add a setting to define a custom video source folder for the screensaver: Allow users to select a folder containing video files Play videos from this folder during screensaver mode Support optional behaviors such as: Shuffle playback Looping Mixing with game videos or using only custom videos 📦 Benefits Enables highly personalized screensaver experiences Supports use cases like music videos, attract mode clips, or themed collections Reduces reliance on external media players or hacks Enhances Big Box as a living room or arcade display 💡 Notes Should support common video formats already handled by LaunchBox Default behavior should remain unchanged unless a custom folder is set Could optionally support multiple folders or playlists in the future

Zombinati about 1 month ago

1

📋 Summary Add an option in LaunchBox to make grouped library views collapsible, allowing users to collapse and expand sections for faster browsing in large collections. ❗ Problem Navigating large libraries can become slow and difficult, especially when arranging media by grouped fields such as: Developer Genre Publisher Region Release Date Year Source Title (A to Z) With many groups expanded at once: Browsing takes longer Scrolling becomes less efficient Large views can feel cluttered and harder to manage 💡 Proposal Add collapsible group headers for grouped library views: Allow each group to be expanded or collapsed individually Add Collapse All and Expand All controls Support keyboard shortcuts for: Collapse All Expand All This would make it easier to jump through large libraries without keeping every section open. 📦 Benefits Makes grouped views faster and easier to browse Reduces clutter in large libraries Helps users focus only on the groups they want to view Could improve responsiveness by reducing how much content is expanded at once 💡 Notes Should be optional, with current behavior unchanged by default Group collapse state could potentially persist while browsing Keyboard shortcuts would make this especially useful for power users

KevinInSeattle about 1 month ago

2

Users importing ROM collections with hacks, translations, prototypes, revisions, and other variants need a way to preserve the original ROM filename as the game title instead of having LaunchBox normalize the title to a database match. Today, imported files such as Final Fantasy (Translation v1.2).nes can end up displayed simply as Final Fantasy, which makes multiple variants appear identical in the game list. This is especially problematic for curated or archival collections where the filename contains the important identifying information. This request is to add a true “raw import” option that uses the ROM filename as the title, improve version visibility in Big Box, and allow bulk editing of the Title field. User Impact Variant-heavy collections become hard to browse because many entries appear with the same base title. Important identifying information from the ROM filename is not visible in the main list. Users may only be able to tell variants apart by opening details and checking the Version field. Manually fixing hundreds of imported titles is slow and defeats the purpose of bulk import. Example ROM filename: Final Fantasy (Translation by Demo Team v1.2).nes Current result: Title: Final Fantasy Expected result: Title: Final Fantasy (Translation by Demo Team v1.2) Requested Changes Add an import option to preserve ROM filenames as titles Suggested option names: Use ROM filename as game title Do not database-match imported titles Recommended behavior: Use the filename without extension as the imported Title Do not replace the title with a database-normalized base title Keep metadata/artwork lookup separate from title preservation if possible Improve Big Box visibility for variants Recommended behavior: Allow the Version field to be shown in the main Big Box game list Make it easier to distinguish variants without opening the details view Add Title to bulk edit Recommended behavior: Expose Title as a bulk-editable field Allow users to rename imported entries in batches after import Use Cases ROM hacks Fan translations Prototype and beta collections Revision-based sets Archival collections where exact source naming matters Acceptance Criteria The import flow includes an option to preserve the original ROM filename as the imported game title. When enabled, LaunchBox uses the ROM filename without extension instead of a database-normalized title. Variant-heavy ROM imports remain visually distinct in the game list. Big Box can show enough version/variant information for users to distinguish similar titles in the main list. Users can bulk edit the Title field for multiple selected games. Existing import behavior remains unchanged for users who prefer normalized database titles.

ZombieMaulie about 1 month ago

2

📋 Summary Add support for storing a MobyGames ID and link on LaunchBox Games Database entries. ❗ Problem Currently, LaunchBox database entries do not include a direct reference to MobyGames. This means: Users cannot quickly jump from a LaunchBox entry to its MobyGames page There is no consistent way to map entries between the two databases Helpful external reference data is harder to verify or cross-check For users who rely on both databases, this creates unnecessary friction. 💡 Proposal Add a dedicated MobyGames ID or URL field to Games Database entries: Store the MobyGames ID for each game Display a clickable MobyGames link where appropriate Allow this field to be used as a reference point for moderation and data verification 📦 Benefits Makes it easier to cross-reference LaunchBox entries with MobyGames Improves research and verification when editing database entries Adds a useful external reference for users and moderators 💡 Notes Should be optional and only used when a matching MobyGames entry exists Could be hidden from normal users if primarily intended as reference data

chinagreenelvis about 2 months ago

3

📋 Summary Expand Pause Menu support for Additional Apps so users can launch external viewers for files like images, CBZs, walkthroughs, maps, and strategy guides while in game. ❗ Problem The Pause Menu currently has limited support for Additional Apps: PDF based items can be displayed, but other useful formats are harder to use If an Additional App relies on an external viewer or emulator, the Pause Menu may show the item but fail to pass the needed commands or parameters This makes it difficult to use image viewers or comic readers for maps, cheatsheets, manuals, and guides As a result, users can set these workflows up in LaunchBox, but not reliably access them from the Pause Menu in Big Box. 💡 Proposal Improve how the Pause Menu handles Additional Apps: When building the Pause Menu, check the relevant file extension to decide whether the item should appear If the Additional App uses an emulator or external viewer, do not exclude it for that reason alone Instead, look at the target content path and launch it with the correct app and parameters Support common use cases such as: images for maps and cheatsheets CBZ files for manuals or guides third party viewers such as ImageGlass or comic readers 📦 Benefits Makes the Pause Menu much more useful for reference material Allows users to check maps, walkthroughs, and manuals without leaving the game flow Expands Additional App support beyond PDFs Better matches real world Big Box cabinet and couch gaming use cases 💡 Notes Ideal flow is: pause game, open guide or map, close viewer, return to Pause Menu, then return to the game Existing PDF behavior should remain unchanged This would improve compatibility with third party viewers already supported in normal LaunchBox workflows

shredder_guitarist about 2 months ago

2

📋 Summary Add a faster rendering mode for the LaunchBox image grid that improves scrolling performance in large libraries, even if it uses a simpler and more uniform layout. ❗ Problem The image grid can become laggy with large libraries, especially during fast scrolling. A major reason for this is the current layout behavior, where LaunchBox performs heavy per-row calculations to: Find the tallest image in each visible row Resize the row to match that height Align text consistently across the row This creates a nicer looking layout, but it adds significant overhead while scrolling. The result is that: Scrollbar movement can lag behind user input Fast scrolling feels less responsive Large libraries become noticeably less smooth to browse 💡 Proposal Introduce an optional performance focused image grid mode that prioritizes responsiveness over perfect visual alignment. Possible approaches: Use fixed size containers for all grid items Or use a small number of predefined size buckets for different box shapes Reduce or remove per-row height calculations Let text sit directly beneath each image instead of forcing row-wide alignment This would allow much smoother one-to-one scrollbar movement and faster grid rendering. 📦 Benefits Dramatically improves scrolling performance in large libraries Makes the scrollbar feel more responsive and accurate Reduces lag when browsing image heavy platforms Gives users the choice between visual polish and speed 💡 Notes This could be an optional “Performance Mode” rather than replacing the current grid The main tradeoff is less consistent text alignment and potentially more whitespace A simplified but smooth image grid would likely be preferable for many users with very large collections

AstroBob 2 months ago

See @Show Sort Groupings in Big Box Views for a similar request, related to sorting groups in Big Box 📋 Summary Allow Big Box to sort game lists by fields other than Title, such as release date, star rating, or play count, even if this requires temporarily disabling the alphabetical index. ❗ Problem Big Box currently relies heavily on the alphanumeric index, which assumes lists are sorted by title. Because of this: Sorting by other fields (release date, rating, play count, etc.) is not supported Users cannot easily browse collections in ways that LaunchBox already allows Many users want alternative sorting methods for playlists or platform views For example, users may want to browse: Games by release date Games by star rating Games by play count or last played 💡 Proposal Allow flat sorting in Big Box by additional fields, such as: Release date Star rating Play count Last played Date added When a non-title sort is selected: The alphabetical index could be temporarily disabled Big Box could display a simple indicator showing the active sort field 📦 Benefits Brings Big Box sorting capabilities closer to LaunchBox Enables more meaningful ways to browse large libraries Supports playlist views such as “Top Rated” or “Most Played” Gives users greater flexibility in how their collections are explored 💡 Notes Grouped sorting (like LaunchBox’s category groupings) is a separate, more complex problem Initial scope focuses only on flat sorting of lists UI context indicators may be needed to avoid confusion when the alphabetical index is disabled

AstroBob 2 months ago

📋 Summary Add a search bar to LaunchBox preferences, allowing users to quickly locate specific settings without manually browsing through every category. ❗ Problem LaunchBox has a large and growing number of configuration options, but currently: Users must manually navigate through many tabs and categories to find a setting It can be difficult to remember where a specific option lives New users especially may struggle to locate certain preferences Many modern applications provide a search function in their settings to solve this problem. 💡 Proposal Add a search field at the top of the Options / Preferences window that: Filters settings based on keywords Highlights or jumps directly to matching options Shows results across all preference categories 📦 Benefits Makes settings much easier to discover and access Reduces time spent navigating through menus Improves usability for both new and experienced users Aligns LaunchBox with modern application UX patterns 💡 Notes Results could display as a filtered list or jump directly to the relevant section Should search setting names and possibly descriptions Existing navigation structure would remain unchanged

AstroBob 2 months ago

1

📋 Summary Add Hidden status as a filter option in LaunchBox, allowing users to temporarily filter and view only hidden games without toggling global visibility. ❗ Problem Currently, hidden games are controlled via a global toggle: Users must enable or disable View > Hide Games to show or hide all hidden titles There is no way to filter only hidden games within the library When un-hiding games, they are mixed back into the full library, making them hard to locate again This limits more granular library management 💡 Proposal Add Hidden as a filterable field in LaunchBox: Allow users to filter: Hidden games only Non-hidden games only Integrate into existing filter systems (search, sidebar filters, or advanced filters) Allow Hidden to be combined with other filters (e.g., platform, favorites, genre) 📦 Benefits Enables more granular library management Makes it easy to review or clean up hidden games Avoids constantly toggling global visibility on and off Improves usability for large collections 💡 Notes Should not replace the existing global toggle Could be especially useful when combined with other filters (e.g., Hidden + Platform) Behavior should remain intuitive alongside current visibility settings

gamer85 2 months ago

5