Add support for additional Sharp MZ computer systems to the LaunchBox Games Database. Currently, the database includes the Sharp MZ-2500, but several earlier systems from the MZ family are missing, including the Sharp MZ-700, MZ-1200 and MZ-1500. A growing amount of software for these systems has been preserved and made available, making the lack of database support increasingly noticeable for users cataloguing these libraries. Before adding them individually, we should investigate the compatibility between these systems and the wider MZ family to determine whether they should be represented as separate platforms or grouped under a broader Sharp MZ platform. Requirements Investigate the MZ-700, MZ-1200 and MZ-1500 and their compatibility with other Sharp MZ systems Determine whether each meets our criteria for a distinct platform Consider whether closely compatible systems should instead be grouped into a single Sharp MZ platform Ensure games currently missing from the database, including Sharp MZ versions of titles such as Pac-Man, can be correctly represented Keep the existing Sharp MZ-2500 platform separate if it represents a distinct hardware and software ecosystem
An "&” character in a search terminates the string. For example, search for: plat:Game & Watch This will result in a search for: plat:Game
📋 Summary Add platform show/hide filters to the LaunchBox Games Database moderation queue. ❗ Problem Moderators often have platforms they are more familiar with, and others they are not interested in or do not feel qualified to review. Currently, they may need to repeatedly skip submissions for platforms they do not want to moderate, which slows down the process and adds unnecessary friction. 💡 Proposal Allow users to configure platform filters for the moderation queue. This could support: Showing only selected platforms Hiding selected platforms Saving the filter preferences per user Quickly editing or clearing the platform filter list 🧩 Use Cases A moderator focuses only on platforms they know well A user hides platforms they do not want to review Moderators avoid repeatedly using “Skip for 24 hours” on the same platforms Database changes are reviewed by users with more relevant knowledge 📦 Benefits Speeds up moderation Improves review quality Reduces repetitive skipping Lets contributors focus on areas where they have expertise Makes the moderation queue more pleasant to use ⚠️ Considerations Filters should not permanently remove items from the queue. They should only customize what each moderator sees, and users should be able to reset or adjust them at any time.
📋 Summary Add a way to submit new games, metadata updates, and media updates to the LaunchBox Games Database directly from within LaunchBox. ❗ Problem Users often add or improve game metadata and media inside LaunchBox, then have to repeat the same work manually on the LaunchBox Games Database website. This creates unnecessary double work when: A game is missing from the Games Database A game has incomplete metadata Media has been added or improved locally A user wants to contribute corrections back to the community 💡 Proposal Add a Games Database submission wizard inside LaunchBox. From a game’s details or edit screen, users could choose: Add Game to Games Database for games with no database match Submit Updates to Games Database for games already linked to a database entry The wizard could let users review and select which local changes to submit, such as: Title Platform Release date Developer / publisher Genres Series Notes / description Alternate names Images and other supported media Submissions would go into the normal Games Database moderation queue before becoming public. 🧩 Use Cases Add a missing game after entering its details locally Submit corrected metadata without retyping it on the website Upload locally added box art, screenshots, or clear logos Help fill gaps in the Games Database while managing a LaunchBox library 📦 Benefits Reduces duplicate work for contributors Encourages more database submissions Improves metadata and media coverage over time Makes Games Database contribution feel like part of LaunchBox Helps users share improvements they already made locally ⚠️ Considerations Users should be signed in to a Games Database account before submitting The wizard should clearly show what will be submitted Users should be able to choose specific fields and media, not submit everything blindly Duplicate detection would be important for new game submissions Media submissions still need normal moderation and quality checks Some local-only fields may not map cleanly to Games Database fields
See also @Tag-Based Media System for Flexible Asset Classification 📋 Summary Add dedicated Fan Translation tags for Games Database media so translated logos, box art, cartridges, and other assets can be categorized consistently. ❗ Problem Fan-translated games often have custom translated media, but there is no clear place to assign these assets in the Games Database. Currently, contributors may use regions like North America, United States, or World for fan-translated media. This causes problems because: It can imply the game had an official release in that region Users in other English-speaking regions may not scrape the translated media correctly Improved fan translations can conflict with official English releases Different contributors may use different region choices for the same type of asset Non-English fan translations have no consistent tagging approach 💡 Proposal Add dedicated fan translation media tags based on translation language. Examples: Fan Translation - English Fan Translation - Spanish Fan Translation - Portuguese Fan Translation - French Fan Translation - German Fan Translation - Italian These would be used for media created for fan-translated versions of games, without incorrectly marking the game as an official regional release. 🧩 Use Cases A Japanese-only game receives an English fan translation and translated clear logo A game with an official English release also has an improved fan translation Spanish, Portuguese, French, or other fan translation projects need matching media Contributors need a consistent place to submit translated logos, boxes, carts, and discs 📦 Benefits Prevents fan-translated media from being misclassified as official regional media Gives contributors clearer submission guidance Improves scraping for translated assets Supports multilingual fan translation projects Reduces inconsistency across Games Database submissions ⚠️ Considerations This should likely apply to media tagging, not necessarily the game’s main region field. Users may also need a way to prioritize fan translation media in their region/media priority settings. A friendly naming format such as Fan Translation - English may be clearer than language-code labels like Fan Translation-en.
📋 Summary Improve consistency and quality control for Arcade fanart box fronts and arcade cabinet media in the LaunchBox Games Database. ❗ Problem Some Arcade media categories contain inconsistent or low-quality images, such as CD jewel case-style box fronts, arcade cabinets with mismatched angles, non-transparent backgrounds, or visibly pixelated artwork. This can make Arcade libraries look uneven, especially in LaunchBox and Big Box views that rely on consistent artwork presentation. 💡 Proposal Create clearer media standards for Arcade artwork and use them to clean up or deprioritize unsuitable images. This could include: Avoiding CD jewel case-style images for Arcade fanart box fronts Preferring cabinet images with transparent backgrounds Encouraging consistent cabinet perspective and angle Flagging or replacing low-resolution and heavily pixelated images Providing clearer submission guidance for Arcade media categories 🧩 Use Cases Make Arcade game views look more consistent Improve Big Box themes that display cabinet artwork Help contributors understand what Arcade media should look like Reduce mismatched artwork in downloaded media sets 📦 Benefits Cleaner visual presentation for Arcade libraries More consistent artwork across games Better guidance for database contributors Higher-quality media downloads for users ⚠️ Considerations Existing media should be handled carefully so useful artwork is not removed without suitable replacements. A safer first step may be improving submission standards and allowing lower-quality media to be flagged, replaced, or deprioritized.
📋 Summary Add a way to identify Commodore 64 Games System compatible titles within the existing Commodore 64 platform. ❗ Problem The Commodore 64 Games System was a keyboardless console variant of the Commodore 64. Some Commodore 64 cartridge games were designed or adapted for joystick-only controls, making them suitable for C64GS-style setups. Currently, users may need to track these games manually. 💡 Proposal Add metadata, filtering, or playlist support for C64GS-compatible Commodore 64 games. This could allow users to: Mark games as C64GS compatible Filter C64GS-ready cartridge games Create a dedicated C64GS playlist without duplicating database entries Store notes about joystick-only controls or required emulator settings 📦 Benefits Avoids duplicate Commodore 64 database entries Supports users who want C64GS-style collections Preserves the distinction without splitting the platform unnecessarily Improves organization for cartridge-focused Commodore 64 users ⚠️ Considerations This should remain part of the Commodore 64 platform rather than becoming a separate Games Database platform, since the software library overlaps heavily with standard Commodore 64 cartridge releases.
📋 Summary Add Zeebo as a platform within LaunchBox and the LaunchBox Games Database. ❗ Problem Zeebo was a digital-only home console released in Brazil and Mexico in 2009, based on Qualcomm BREW technology. Currently: Users may need to manually create or standardize the platform in LaunchBox Zeebo titles may be difficult to organize consistently Metadata and media management is less organized without a dedicated Games Database platform Digital-only games are harder to preserve and document because the original store is no longer available As Zeebo emulation and preservation efforts improve, more users may want to catalog these titles properly. 💡 Proposal Add Zeebo as an official platform in LaunchBox and the Games Database. This would allow: Dedicated platform metadata Platform-specific media Consistent organization across user collections Easier contribution and moderation of Zeebo titles Better preservation of a digital-only console library Where appropriate, any existing Zeebo-related entries could be reviewed and assigned to the standardized platform. 📦 Benefits Improves support for preserved digital-only console libraries Provides a proper scrape target for Zeebo games Helps document a historically unusual Brazilian/Mexican console Makes metadata and media contribution easier Supports growing interest from emulator and preservation communities ⚠️ Considerations Platform naming should be standardized as Zeebo Any existing partial platform support should be reviewed for consistency Platform icons, clear logos, and metadata would need to be added or verified Because the platform was digital-only, available media may vary by title
📋 Summary Add Apple Bandai Pippin as a platform within LaunchBox and the LaunchBox Games Database. ❗ Problem Apple Bandai Pippin was a PowerPC-based multimedia console released in the mid-1990s. Currently: Users may need to manually create the platform in LaunchBox Pippin titles may be grouped under broader Macintosh or custom platforms Metadata and media management is less organized without a dedicated platform There is no standard platform entry for users to contribute to or scrape against Although the library is small, Pippin has a distinct hardware and software identity that makes it useful to catalog separately. 💡 Proposal Add Apple Bandai Pippin as an official platform in LaunchBox and the Games Database. This would allow: Dedicated platform metadata Platform-specific media Consistent organization across user collections Easier contribution and moderation of Pippin titles Better preservation of a historically unusual console library Where appropriate, existing Pippin-related entries could be reviewed and reassigned to the new platform. 📦 Benefits Improves support for obscure commercial console platforms Helps preserve and document Apple/Bandai Pippin software Provides a proper scrape target for Pippin titles Reduces reliance on generic Macintosh categorization Improves consistency for collectors of rare console libraries ⚠️ Considerations Platform naming should be standardized, likely as Apple Bandai Pippin The library includes both games and multimedia software, so inclusion rules may need review MAME support is still preliminary, so the request should focus on cataloging and preservation rather than mature playability Platform icons, clear logos, and metadata would need to be added or verified
📋 Summary Add Bandai Playdia as a platform within LaunchBox and the LaunchBox Games Database. ❗ Problem Bandai Playdia was a Japanese CD-ROM console released in 1994 with a small but distinct library of interactive FMV and children’s titles. Currently: Users may need to manually create the platform in LaunchBox Playdia titles may be grouped under custom or less accurate platforms Metadata and media management is less organized without a dedicated platform There is no standard platform entry for users to contribute to or scrape against Because the Playdia library is finite and well documented, it is a good candidate for database completeness. 💡 Proposal Add Bandai Playdia as an official platform in LaunchBox and the Games Database. This would allow: Dedicated platform metadata Platform-specific media Consistent organization across user collections Easier contribution and moderation of Playdia titles Better cataloging of preserved Playdia CD-ROM software 📦 Benefits Improves support for obscure Japanese CD-ROM consoles Provides a proper scrape target for Playdia titles Helps preserve and document a complete niche software library Reduces reliance on custom platform entries Improves consistency for collectors of rare console libraries ⚠️ Considerations Platform naming should be standardized, likely as Bandai Playdia The library includes interactive FMV and children’s software, so inclusion rules may need review Platform icons, clear logos, and metadata would need to be added or verified
📋 Summary Add Capcom CPS Changer as a platform within LaunchBox and the LaunchBox Games Database. ❗ Problem Capcom CPS Changer was a Japan-only home arcade system released by Capcom in 1994. Currently: Users may need to manually create the platform in LaunchBox CPS Changer titles are usually grouped under Arcade or Capcom CPS platforms Metadata and media for the home-format releases are harder to manage separately There is no standard platform entry for users who collect CPS Changer releases specifically Although closely related to Capcom’s arcade CPS hardware, the CPS Changer was sold as a consumer home system and has collector interest as its own format. 💡 Proposal Add Capcom CPS Changer as an official platform in LaunchBox and the Games Database. This would allow: Dedicated platform metadata Platform-specific media Consistent organization for CPS Changer collections Easier contribution and moderation of CPS Changer-specific releases Where appropriate, CPS Changer-specific versions could be reviewed separately from standard arcade CPS entries. 📦 Benefits Supports collectors of rare home arcade hardware Separates CPS Changer releases from generic Arcade/CPS entries Improves metadata and media organization for this specific format Provides consistency with other arcade-at-home platforms ⚠️ Considerations The library is very small, so this may be lower priority than broader missing platforms Most games overlap heavily with existing CPS arcade titles Platform naming should be standardized, likely as Capcom CPS Changer Existing CPS1/CPS2/Arcade entries should not be duplicated unnecessarily
📋 Summary Add filtering options to the LaunchBox Games Database Changes Status page so users can view changes by status. ❗ Problem The Changes Status page can contain many submitted changes across multiple pages. Users currently have to manually scan through large lists to find specific types of changes, such as pending, approved, or denied submissions. This makes it harder to review contribution history or check the status of recent database submissions. 💡 Proposal Add status filter options to the Changes Status page. Filters could include: All Pending Approved Denied The selected filter should reduce the list to only changes matching that status. 🧩 Use Cases View only pending submissions that still need review Check which recent submissions were approved Find denied changes without paging through unrelated items Review contribution history more efficiently 📦 Benefits Makes the Changes Status page easier to navigate Reduces time spent scanning through multiple pages Improves transparency for Games Database contributors Helps users track their submissions more efficiently ⚠️ Considerations Filters should work with pagination so users can browse filtered results across multiple pages without losing the selected status.
📋 Summary Create a consistent standard for when arcade hardware families should receive their own platform in LaunchBox and the LaunchBox Games Database. ❗ Problem Some arcade hardware families are treated as dedicated platforms, while other comparable systems are grouped under the generic Arcade platform. This can create confusion for users who collect, emulate, or contribute metadata for later arcade hardware systems such as Sega Chihiro, Sega Lindbergh, Sega RingEdge, Sega RingWide, Namco System 246/256, Namco System 357/369, and similar systems. Without a clear standard, requests for new arcade platforms are handled one system at a time, which can feel inconsistent. 💡 Proposal Establish a public guideline for when an arcade hardware family should be added as a dedicated platform. Possible criteria could include: Distinct arcade hardware family Meaningful number of supported games Active or growing emulator support Different setup needs from general MAME/Arcade imports Enough metadata/media value to justify a separate platform Clear benefit for scraping, browsing, and organizing games Once the standard is defined, existing and future arcade hardware requests could be evaluated consistently. 🧩 Use Cases Decide whether examples such as Sega Lindbergh should be a dedicated platform @New Platform: Sega Lindbergh Handle RingEdge/RingWide and Namco arcade hardware requests consistently Help contributors know where arcade game metadata should belong Reduce debate around whether a system should be Arcade or its own platform 📦 Benefits More consistent Games Database organization Clearer expectations for users and contributors Better handling of newer arcade emulation setups Reduces one-off platform debates Improves metadata and media organization for arcade hardware collectors ⚠️ Considerations This does not mean every arcade board should automatically become a separate platform. The goal is to define a practical standard so only arcade hardware families with clear user value and enough support are separated from the general Arcade platform.
📋 Summary Add an optional way for LaunchBox Games Database contributors to create a shareable showcase page of their approved media submissions. ❗ Problem Media submissions to the LaunchBox Games Database are anonymous, which is valuable for privacy and should remain the default. However, some users work together on community media projects, such as clear logos, translated logos, fan translation artwork, or other curated media sets. When recruiting collaborators, it can be difficult to show examples of approved work without manually finding and sharing old local files. 💡 Proposal Allow users to opt in to a public contributor showcase page that displays their approved media submissions. The showcase could include: Approved images submitted by the user Game title and platform Media type, such as Clear Logo, Box Front, Screenshot, etc. Optional filtering by media type or platform A shareable public link A profile setting to enable, disable, or hide the showcase at any time By default, submissions should remain anonymous unless the user explicitly chooses to make their approved media visible on their showcase page. 🧩 Use Cases Share examples of logo work before joining a community project Browse a contributor’s approved media submissions Recruit artists for themed media projects Avoid manually digging through old local files to find examples 📦 Benefits Helps community media projects organize and recruit contributors Gives contributors an optional way to showcase their work Preserves anonymous submissions by default Makes approved media easier to reference and share ⚠️ Considerations This should be fully opt-in, with clear privacy controls. Users should be able to disable their showcase or hide specific items if needed.
📋 Summary Add support for linking related game images together as matched packaging sets in LaunchBox and the LaunchBox Games Database. ❗ Problem Some games have multiple official box variants within the same region, such as original releases, Greatest Hits, Player’s Choice, or other re-release packaging. When multiple fronts, backs, and spines exist for the same game, LaunchBox may combine images from different variants when displaying box art or generating 3D boxes. For example, an original front cover could be paired with a Player’s Choice spine or back cover. 💡 Proposal Allow images in the Games Database to be grouped into named or numbered sets. Example: Set 1: Original release front, back, and spine Set 2: Player’s Choice front, back, and spine LaunchBox could then use images from the same set when displaying related artwork or building 3D box views. 🧩 Use Cases Keep original release box images together Keep re-release box images together Avoid mismatched front, back, and spine artwork Improve accuracy for 3D box presentation 📦 Benefits More accurate box art matching Better 3D box results Cleaner Games Database organization Improved preservation of different official packaging variants ⚠️ Considerations The database would need a simple way for contributors or moderators to assign images to the correct set without making image submission too complicated.
📋 Summary Add Sega Lindbergh as a platform within LaunchBox and the LaunchBox Games Database. ❗ Problem The Sega Lindbergh platform has become increasingly relevant to emulation enthusiasts following the release and continued development of the Lindbergh Loader project for Windows. Currently: Users must manually create the platform in LaunchBox Games are typically categorized under the generic Arcade platform Metadata and media management is less organized than dedicated arcade hardware platforms There is no standard platform entry for users to contribute to or scrape against As support and compatibility improve, more users are beginning to add Sega Lindbergh titles to their collections. 💡 Proposal Add Sega Lindbergh as an official platform in LaunchBox and the Games Database. This would allow: Dedicated platform metadata Platform-specific media Consistent organization across user collections Easier contribution and moderation of Lindbergh titles Where appropriate, existing Lindbergh games currently categorized under Arcade could be reviewed and reassigned to the Sega Lindbergh platform. 📦 Benefits Improves organization of modern arcade hardware platforms Provides consistency across LaunchBox collections Makes media and metadata management easier Reduces reliance on generic Arcade categorization Supports the growing interest in Sega Lindbergh emulation ⚠️ Considerations Existing Arcade entries may need review to determine whether they should remain under Arcade or move to Sega Lindbergh Platform naming should align with existing LaunchBox platform standards Platform icons, clear logos, and metadata would need to be added to support the new platform
📋 Summary Add a dedicated Base Game (or Hack Of) field to the LaunchBox Games Database that allows ROM hacks to be linked directly to the original game they are based on. ❗ Problem The LaunchBox Games Database contains an increasing number of ROM hacks, fan modifications, translations, and enhancement projects. However, there is currently no structured way to identify which original game a hack is based on. As a result: Users may not know what game a hack requires It can be difficult to understand the context of a ROM hack ROM hacks cannot easily be grouped by their source game Database relationships between original games and their derivatives are lost For example, a user browsing ROM hacks may not immediately know whether a particular hack is based on: Super Mario World Pokémon FireRed The Legend of Zelda: A Link to the Past without manually researching it. 💡 Proposal Add a new database field: Base Game Or Hack Of This field would: Link directly to another Games Database entry Identify the original game the hack is based on Be available through scraping and metadata downloads Support filtering, grouping, and playlist creation Potential future enhancements could include: Viewing all hacks associated with a specific game Displaying related hacks on a game's database page Creating dynamic playlists such as: "All Super Mario World Hacks" "All Pokémon FireRed Hacks" 🧩 Use Cases A user wants to see all ROM hacks based on a particular game A user discovers a hack and wants to know the original title it requires Collections can be organized around popular hack communities Theme developers can surface related hacks alongside the original game Database contributors can establish clearer relationships between entries 📦 Benefits Improves ROM hack discoverability and organization Creates meaningful relationships between database entries Helps users understand hack dependencies and origins Enables smarter filtering, searching, and playlist generation Lays the foundation for richer metadata relationships in the future ⚠️ Considerations Should support linking to an existing Games Database entry rather than using free text Some hacks may be based on multiple source games or projects Similar relationship systems could potentially be expanded later for: Fan translations Remakes Ports Total conversions Homebrew derivatives
📋 Summary Add support for series/franchise metadata within the LaunchBox Games Database, allowing games to be associated with one or more series that can be synced directly into LaunchBox. ❗ Problem Currently, the Series field in LaunchBox is entirely user managed and is not populated from the Games Database. As a result: Users must manually assign series information Series organization is inconsistent between collections Large libraries require significant manual maintenance Users cannot benefit from community curated franchise information However, series classification is often subjective and can vary depending on the user's goals. For example: A user may want: Mario Another user may prefer: Mario Kart Mario Party Mario Sports Others may want both simultaneously There is no universally accepted hierarchy for many franchises. 💡 Proposal Add series support to the Games Database while accommodating different levels of franchise organization. Potential approaches could include: Option A: Multi-Level Series Structure Games can belong to: Primary Series Sub Series Examples: Super Mario Kart Primary Series: Mario Sub Series: Mario Kart Mario Party 3 Primary Series: Mario Sub Series: Mario Party Option B: Multiple Series Assignments Games can have multiple series tags: Mario Mario Kart This provides flexibility while allowing users to filter or group based on either level. Option C: Series Taxonomy System A more advanced hierarchy where: Mario Mario Kart Mario Party Mario Sports Paper Mario can coexist within a parent-child structure. 🧩 Use Cases Users automatically receive franchise information when scraping metadata Collections can be grouped by franchise without manual work Smart playlists can be built around series data Users can browse all entries in a franchise across platforms Big Box themes can surface franchise collections more effectively 📦 Benefits Reduces manual metadata management Creates more consistency across collections Enables richer filtering, searching, and playlist creation Supports franchise based browsing and discovery Opens the door for future series focused features throughout LaunchBox ⚠️ Considerations Series definitions can be subjective and sometimes controversial A simple single value field may not be sufficient for complex franchises The database should support both broad and granular franchise groupings Clear moderation guidelines would be needed to ensure consistency
Java ME / Java Phone Games is currently missing from the LaunchBox Games Database and would be a valuable addition as a dedicated platform. Before Android and iOS became dominant, Java ME was one of the most important mobile gaming platforms of the 2000s. Many phones supported Java-based games, and the platform had a large library of commercial releases, licensed titles, ports, and original mobile games. Examples include: God of War: Betrayal Doom RPG Wolfenstein RPG Bounce Tales Gameloft titles EA Mobile titles Gangstar series Currently, users may be forced to place these games under Android, Apple iOS, or other fallback platforms, which does not accurately represent the original platform or era. Adding Java ME / Java Phone Games as its own platform would allow: Dedicated platform metadata More accurate organization of mobile game history Proper contribution of Java phone game entries Separate media and metadata from Android and iOS titles Better preservation of early mobile gaming libraries This platform represents a significant part of mobile gaming history and deserves its own dedicated entry in the LaunchBox Games Database.
📋 Summary Add dedicated Play Mode metadata to the LaunchBox Games Database so games can be categorized by how multiplayer actually works. ❗ Problem LaunchBox can display Play Mode locally, but the Games Database does not appear to store detailed Play Mode values for regular game entries. Instead, Play Mode is generally inferred from broader metadata such as whether a game is cooperative or how many players it supports. This makes it difficult to accurately track and search for specific multiplayer types, such as: 3-player simultaneous 4-player simultaneous 2-player alternating Competitive player-versus-player Cooperative multiplayer 💡 Proposal Add Play Mode as a proper editable metadata field in the LaunchBox Games Database. Supported values could include: Single player 2-player simultaneous 3-player simultaneous 4-player simultaneous 2-player alternating 4-player alternating Cooperative Player versus player These values should be available for database contributors to submit, edit, and correct. 🧩 Use Cases Find all 4-player simultaneous games on a platform Separate co-op games from competitive multiplayer games Improve metadata for platforms where multiplayer details are currently vague Let contributors correct missing or incomplete multiplayer information 📦 Benefits More accurate multiplayer metadata Better filtering and playlist creation More useful Games Database search results Improved community data over time ⚠️ Considerations Play Mode values should have clear definitions so contributors apply them consistently. Broad values like “Multiplayer” may still be useful when exact behavior is unknown.