Direct Games Database Lookup for Metadata Scraping

📋 Summary

Add an option for LaunchBox to query the online Games Database directly when scraping metadata, instead of always downloading a local copy of the database first.

❗ Problem

LaunchBox currently downloads a local copy of the Games Database before scanning for metadata. This has useful benefits, especially for offline setups, but it also creates friction for users who are always online:

• Users are prompted to download a fresh database copy regularly

• Metadata scans are delayed while the database file downloads

• New or recently updated database entries are not available until the local copy is refreshed

• The workflow can feel unnecessary on machines with constant internet access

For some users, especially those regularly importing or updating games, waiting 20–30 seconds each time adds up.

💡 Proposal

Add a metadata lookup option that allows LaunchBox to query the online Games Database directly.

Possible options:

• Use Online Games Database Lookup

  • Query the live database during scraping

  • Always access the latest metadata and updates

• Use Local Games Database File

  • Keep the existing offline-friendly workflow

  • Continue supporting arcade cabinets and offline builds

This could be exposed as a preference, allowing users to choose the workflow that best fits their setup.

🧩 Use Cases

• A user with an always-online PC wants faster metadata scans without downloading the database first

• A contributor adds or updates a game and wants those changes available immediately

• An arcade cabinet user keeps the current offline local database workflow

• Users choose between speed, freshness, and offline reliability based on their setup

📦 Benefits

• Reduces friction during metadata scans

• Makes new database updates available immediately

• Preserves existing offline workflows

• Gives users more control over how LaunchBox interacts with the Games Database

• Improves day-to-day usability for online systems

⚠️ Considerations

• Online lookup should gracefully handle connection failures

• Local database mode should remain available for offline users

• Caching could still be used to reduce repeated requests

• Server load and API performance would need to be considered