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 1 day ago

1

LaunchBox for Android

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

LaunchBox Games Database

📋 Summary Require moderators to provide structured, standardized feedback when rejecting submissions to improve clarity and consistency. ❗ Problem Rejection feedback is currently inconsistent: Some rejections include little or no explanation Feedback varies widely in quality and detail Contributors struggle to understand what went wrong Repeated mistakes occur due to lack of clear guidance This leads to frustration and unnecessary resubmissions. 💡 Proposal Introduce structured feedback requirements for rejections: Require moderators to select a reason when rejecting: Incorrect category Incorrect region Duplicate Low quality Other (with optional note) Allow optional additional comments for more context Standardize feedback format across all rejections Surface this feedback clearly to submitters 🧩 Use Cases A contributor quickly understands why their image was rejected Common mistakes are reduced through consistent feedback Moderators spend less time writing repetitive explanations Submissions improve in quality over time 📦 Benefits Improves clarity and transparency Reduces repeated errors and resubmissions Creates a more consistent moderation process Helps educate contributors over time ⚠️ Considerations Should not overly slow down moderation workflow Predefined options must be clear and comprehensive Additional comments should remain optional ✅ Outcome Structured feedback ensures contributors receive clear, actionable guidance, improving both submission quality and overall database consistency.

AstroBob 11 days ago

LaunchBox Games Database

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

LaunchBox for Windows

📋 Summary Establish clear standards and system improvements for region tagging to ensure consistent usage and predictable media downloads. ❗ Problem Region tagging is currently inconsistent and often misused: Media is incorrectly tagged as “World” instead of a specific region Duplicate images are uploaded for identical assets across regions Contributors apply personal preferences rather than consistent rules Users receive unpredictable downloads when using region priorities Ongoing moderation conflicts around what constitutes the “correct” region This creates confusion and reduces the reliability of the database. 💡 Proposal Improve region tagging through a combination of standards and system support: Define clear guidelines for region usage: When to use specific regions vs “World” How to handle identical assets across regions Introduce validation or prompts during submission: Flag potential duplicate region uploads Suggest merging into a single “World” entry where appropriate Provide clearer visibility of region usage during moderation Ensure consistent handling of region priorities in media downloads 🧩 Use Cases Identical logos for NA and EU are tagged once as “World” Region specific box art is clearly differentiated and tagged correctly Contributors follow consistent rules instead of personal preference Users can reliably control downloads based on region priorities 📦 Benefits Improves consistency across the database Reduces duplicate or redundant media Minimizes moderation conflicts Creates predictable and reliable media downloads ⚠️ Considerations Needs clear and agreed upon definitions Must balance flexibility with standardization Should integrate with future tagging system ✅ Outcome Standardized region tagging improves consistency and predictability, making the database more reliable for both contributors and users.

AstroBob 11 days ago

LaunchBox Games Database

📋 Summary Introduce tools that allow moderators to communicate, discuss, and collaborate on submissions directly within the Games Database. ❗ Problem Moderation is currently isolated and lacks collaboration: No way for moderators to discuss unclear or controversial submissions Decisions are made independently, often leading to conflicts Repeated “edit wars” occur without resolution No shared space to ask questions or get second opinions This leads to inconsistency and frustration among moderators. 💡 Proposal Introduce lightweight collaboration tools for moderators: Add a discussion or comment thread on submissions Allow moderators to: Ask questions Provide reasoning Flag uncertainty Optional “needs discussion” or “review required” state Keep discussions structured and tied to specific submissions 🧩 Use Cases A moderator is unsure how to classify media and asks for input Conflicting votes are resolved through discussion instead of repetition Moderators share knowledge on edge cases or unclear rules Complex submissions receive more consistent decisions 📦 Benefits Reduces moderation conflicts and inconsistencies Encourages knowledge sharing among moderators Improves quality of decisions Reduces repeated submission cycles ⚠️ Considerations Should remain lightweight, not a full forum replacement Discussions should be easy to follow and not overly noisy May need moderation to prevent misuse ✅ Outcome Moderator collaboration tools create a more consistent and informed moderation process, reducing conflict while improving overall database quality.

AstroBob 11 days ago

LaunchBox Games Database

📋 Summary Introduce versioning and change history for media entries, allowing moderators and contributors to track, review, and revert changes to assets over time. ❗ Problem Media changes are currently difficult to track: Images are frequently deleted and reuploaded No visibility into who changed what and why Ongoing “edit wars” between contributors and moderators Lost assets can be difficult or impossible to recover Moderation decisions lack historical context This leads to frustration and instability in the database. 💡 Proposal Add versioning and history tracking for media: Track all changes to media entries: Uploads Deletions Edits (type, region, etc) Provide a visible change history log per asset Allow moderators to: View previous versions Restore or revert changes Optionally show reason for change where applicable 🧩 Use Cases A deleted image can be restored without needing reupload Moderators review past changes before making decisions Repeated disputes over the same asset are easier to resolve Contributors understand why an image was changed or removed 📦 Benefits Reduces moderation conflicts and repeated work Prevents loss of valuable media Increases transparency and accountability Improves overall stability of the database ⚠️ Considerations Storage implications for version history UI needs to remain simple and readable Access to revert functionality may need restrictions ✅ Outcome Media versioning provides transparency and control, reducing conflicts while protecting valuable contributions within the database.

AstroBob 11 days ago

LaunchBox Games Database

📋 Summary Introduce curated “default” media sets for platforms that can be optionally locked or prioritized, ensuring users always have access to a consistent, high quality baseline of assets. ❗ Problem Media quality and consistency can vary significantly: Official categories are often mixed with fanart or inconsistent assets High quality community sets exist but are not standardized in the database Media can be repeatedly changed, moved, or overwritten Users may end up with incomplete or inconsistent downloads This creates an unpredictable experience when scraping media. 💡 Proposal Introduce curated default media sets: Define a “default” set of high quality assets per platform: Box art, carts, logos, etc Allow these sets to be: Prioritized in downloads Optionally locked to prevent frequent changes Credit contributors where applicable Allow users to choose between: Default curated sets Full database (including fanart and alternatives) 🧩 Use Cases A user wants a clean, consistent SNES library with minimal setup A contributor’s high quality set becomes the default baseline A user avoids downloading inconsistent or low quality media Moderation disputes are reduced for “baseline” assets 📦 Benefits Improves consistency and quality for all users Reduces clutter and unpredictability in downloads Highlights high quality community contributions Provides a better out of the box experience ⚠️ Considerations Requires clear criteria for what qualifies as a default set Needs moderation or admin oversight Should not restrict user customization ✅ Outcome Curated default media sets provide a reliable foundation for users, improving consistency while still allowing flexibility for customization.

AstroBob 11 days ago

LaunchBox Games Database

📋 Summary Create a fully updated, centralized set of moderation and submission guidelines hosted on the LaunchBox Help Center, replacing outdated and fragmented documentation. ❗ Problem Current moderation guidelines are: Outdated and scattered across old forum posts Difficult to find and not centrally maintained Inconsistent or unclear on key topics Not aligned with how the database is used today This leads to: Conflicting moderation decisions Ongoing disputes around naming, regions, and media types Confusion for new contributors Reduced trust and consistency in the database 💡 Proposal Rebuild the moderation and submission guidelines as a dedicated Help Center resource: Create a centralized, easy to navigate documentation hub Clearly define standards for: Naming conventions (games, developers, publishers) Region tagging Media classification and usage When to accept, reject, or modify submissions Include real examples and edge cases where relevant Keep documentation versioned and regularly updated Link directly to these guidelines from the Games Database interface 🧩 Use Cases A new contributor quickly understands how to submit media correctly A moderator references clear rules when reviewing a submission Disputes are reduced because expectations are clearly defined Contributors feel more confident their submissions will be handled fairly 📦 Benefits Improves consistency and quality across the database Reduces moderation conflicts and ambiguity Lowers the barrier to entry for new contributors Builds trust within the community Creates a scalable foundation for future improvements ⚠️ Considerations Guidelines should remain clear and concise, not overly complex Should evolve alongside features like tagging and new media types Requires ongoing ownership to keep documentation up to date ✅ Outcome A modern, centralized Help Center for moderation guidelines creates a shared standard for contributors and moderators, improving consistency, clarity, and overall database quality.

AstroBob 11 days ago

1

LaunchBox Games Database

📋 Summary Introduce a standardized system for developer and publisher naming, including optional parent company linking to group variations under a single entity. ❗ Problem Developer and publisher names are currently inconsistent across the database: Multiple variations exist for the same company, for example: Capcom, Capcom Ltd, Capcom Co., Ltd. No clear standard for naming conventions Difficult to filter, search, or group games accurately Moderators often conflict on what the “correct” name should be This leads to fragmented data and poor discoverability. 💡 Proposal Introduce a structured system for developer and publisher entities: Define a standardized “primary name” for each company Allow aliases or variations to map to that primary name Introduce optional parent company relationships: For example, subsidiaries grouped under a parent entity Apply consistent naming rules across the database Provide guidance within moderation tools for naming decisions 🧩 Use Cases All variations of “Capcom” are grouped under a single canonical entry Users can filter games by a developer without missing entries due to naming differences Subsidiaries can optionally roll up under a parent company Moderators no longer debate minor naming differences 📦 Benefits Improves search, filtering, and organization Reduces duplicate or fragmented entries Creates consistency across the database Simplifies moderation decisions ⚠️ Considerations Defining parent relationships can become complex Clear boundaries are needed to avoid overcomplication Migration of existing data will require careful handling ✅ Outcome A standardized naming system improves data integrity and usability, making the database more reliable and easier to navigate.

AstroBob 11 days ago

2

LaunchBox Games Database

📋 Summary Introduce a lightweight appeals system that allows submitters to respond to rejection feedback and provide additional context before a final decision is made. ❗ Problem Currently, there is no way for submitters to respond to feedback on their submissions: Rejection feedback is one-directional Submitters cannot clarify intent or provide additional context Misunderstandings often result in unnecessary rejections Contributors feel disconnected from the moderation process This can lead to frustration and reduced contribution quality over time. 💡 Proposal Add a simple appeals and feedback loop to the submission system: Allow submitters to respond to rejection feedback Provide an “Appeal” or “Add Context” option on submissions Surface this response to moderators during review Keep interactions structured and limited to avoid abuse 🧩 Use Cases A contributor explains why an image was categorized a certain way A submitter provides a source or reference that validates their submission A misunderstanding is resolved without needing resubmission Moderators can make more informed decisions with added context 📦 Benefits Improves communication between contributors and moderators Reduces unnecessary rejections and resubmissions Encourages higher quality contributions Builds trust and transparency in the moderation process ⚠️ Considerations Appeals should be limited to avoid spam or misuse Moderators should not be required to engage in long discussions A simple, structured format is preferred over open-ended threads ✅ Outcome A lightweight appeals system creates a more collaborative moderation process, improving submission quality while reducing frustration for contributors.

AstroBob 11 days ago

LaunchBox Games Database

📋 Summary Allow moderators to see each other’s feedback and reasoning during the review process to improve consistency and reduce conflicting decisions. ❗ Problem Moderators currently review submissions without visibility into each other’s reasoning: Votes are visible, but the reasoning behind them is not Moderators may make conflicting decisions on the same submission The same edge cases are repeatedly debated across different submissions There is no shared context to help align decisions This leads to inconsistent moderation and unnecessary friction. 💡 Proposal Enhance the moderation interface to surface shared context: Display rejection reasons and comments to all moderators reviewing the same item Allow moderators to leave optional short notes explaining their decision Surface this information directly within the moderation queue Keep feedback lightweight and easy to scan 🧩 Use Cases A moderator sees why another moderator rejected an image before voting Conflicting decisions are reduced because context is visible upfront Moderators align on edge cases without needing external discussion Repeated debates on the same topics are minimised 📦 Benefits Improves consistency in moderation decisions Reduces conflicting votes and back-and-forth changes Helps establish shared standards across moderators Speeds up decision-making by providing context ⚠️ Considerations Feedback should remain concise to avoid clutter Participation can remain optional to keep workflows fast Basic guidelines may be needed to ensure constructive notes ✅ Outcome Providing moderators with shared context during review leads to more consistent decisions, less friction, and a more aligned moderation process.

AstroBob 11 days ago

LaunchBox Games Database

📋 Summary Add clear, accessible submission and moderation guidelines directly within the Games Database interface to ensure consistency and reduce confusion. ❗ Problem Current guidelines for submissions and moderation are difficult to find, outdated, or buried in forum posts. This leads to: Inconsistent moderation decisions across contributors Confusion around what is considered acceptable data or media Frequent disputes over naming conventions, regions, and media types New contributors struggling to understand expectations Repeated mistakes that could be avoided with clearer guidance This lack of visibility contributes heavily to moderator burnout and declining contribution quality. 💡 Proposal Introduce inline guidelines directly within the Games Database UI, available during both submission and moderation. Display contextual guidance when editing fields (e.g. Developer, Publisher, Region, Image Type) Provide clear examples and best practices for common scenarios Include rules for: Naming conventions Region tagging Media categorisation Handling fanart vs official assets Add quick access links to full documentation where needed 🧩 Use Cases A contributor adding a new game can immediately see correct naming conventions A moderator reviewing media can reference guidelines without leaving the page Users unsure about region tagging can quickly confirm the correct approach New contributors can onboard without needing to search forum posts 📦 Benefits Improves consistency and quality of submissions Reduces moderation conflicts and subjective decision-making Speeds up onboarding for new contributors Decreases reliance on external documentation and forum discussions Helps align the community around a shared standard ⚠️ Considerations Guidelines should be concise and easy to scan More detailed rules can be linked out to full documentation Content should be regularly maintained and updated ✅ Outcome Providing clear, inline guidance ensures contributors and moderators are aligned, reducing confusion and improving the overall quality and consistency of the Games Database.

AstroBob 11 days ago

LaunchBox Games Database

📋 Summary Introduce a flexible tagging system for media, allowing items like fanart, AI generated, reconstructed, or region specific variants to be tagged instead of forcing them into rigid categories. ❗ Problem The current category based system is too rigid and leads to ongoing issues: Fanart is often uploaded into official categories due to lack of alternatives Reconstructed or cleaned media has no clear place, causing inconsistency Categories become cluttered with mixed content types Users receive unpredictable downloads when scraping media Moderation conflicts arise due to unclear classification rules This has been a long standing source of frustration and inconsistency across the database. 💡 Proposal Move from rigid category structures to a tagging based system: Keep core media types simple, for example Box Front, Clear Logo, Screenshot Introduce two types of tags: Official tags (structured, curated by LaunchBox), for example: Fanart Reconstructed AI Generated Cleaned or Restored Region specific Community tags (freeform, user defined): Allow contributors to add additional context or descriptors Enable more granular categorization without bloating core systems Allow moderators to apply or correct official tags as part of moderation Enable LaunchBox to use tags in media management, including: Include or exclude tags in Media Priorities Filter downloads based on tags Control scraping behaviour (for example, exclude AI generated or fanart) 🧩 Use Cases A reconstructed SNES cartridge image is tagged as “Reconstructed” instead of miscategorized A cleaned version of damaged box art is tagged as “Restored” A fan made logo is tagged as “Fanart” while still being a Clear Logo A user excludes AI generated media from their downloads A contributor adds community tags like “Custom Spine” or “Alt Style” Users tailor their media downloads based on preferences and quality expectations 📦 Benefits Reduces moderation conflicts and ambiguity Keeps categories clean and predictable Gives users granular control over what media is downloaded Supports both structured data and flexible community input Scales better than continuously adding new categories Improves overall quality and consistency of the database ⚠️ Considerations Official tags should be clearly defined and limited in scope Community tags may require moderation safeguards to prevent misuse UI updates will be needed for filtering and visibility Migration from existing categories will need careful handling ✅ Outcome A hybrid tagging system, combining official and community tags, creates a scalable and flexible foundation for media organization, improving both moderation clarity and user control.

AstroBob 11 days ago

1

LaunchBox Games Database

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

LaunchBox for Windows

Hi LB team, In terms of Windows games, there are a lot of source ports/reimplementations and engine updates for old games that have come up over the years. I’m not sure the best game type to list them under; they really aren’t Homebrew because they often use original assets, and I think Unlicensed doesn’t work particularly well either. As more and more of these get released over the years, a Source Port category could be helpful to keep track of these new engines and updates that come out. Thanks!

TheNewClassics 13 days ago

LaunchBox Games Database