Leaderboard

Kings Quest II - Romancing the Throne

Kings Quest

Kings Quest II - Romancing the Stones

Could do with some minor touchup's, but that will have to be for someone else

Curious George in Outer Space

CUBIK

last of the first pack done

@goofers That should be enough for now. 😉 More later...

Leisure Suit Larry - Looking for Love

Leisure Suit Larry 1

Leisure Suit Larry - Love for Sail!

Leisure Suit Larry in the Land of the Lounge Lizards

Even if it were to work in Lutris,Proton etc what about the emulators? Wouldn't we need to a wrapper to use the naive Linux versions?

Wait, I think I found the issue on my end. When compressing to zips, I found a couple that didn't rename correctly (did in bullk). I'll re-test mine, but think that was it. Don't know why it missed the 4 or 5 that it did. Sorry @faeran. Will post again, if it is still issue on my end

i've added the game and pics (front, gameplay, background etc) manually into launchbox, so yeah... its not important for me now, but perhaps for others who might run into the same issue, thats why I've made a topic about it.

Could be because it didn't have the Steam App ID associated with it. Tomorrow run the "Force Update Games Database" from the Tools > Download menu inside of LaunchBox and then try again and let me know if you still run into the issue.

CUBIT

Kings Quest VII - The Princeless Bride

Kings Quest I - Quest for the Crown

Hi everyone, LaunchBox for Android 1.21 beta has started, and we have a number of new features and improvements (with more to come) that we could use help testing. Game Progress Tracking has finally made its way over to Android, complete with manual controls, automation rules, and full customization. We have also added a new NAS Management section for users with networked game libraries, and we are continuing to improve performance and fix bugs across the board. If you are able to test this build, here’s what we would love your feedback on: Game Progress Tracking – Manual Updates From any game's menu, tap Progress to change its progress state. Try selecting one of the default values, then try again after customizing your progress states. You can customize them by going to Options > Game Progress Organization. Try creating a new category or value, assigning it to a game, and restarting the app to confirm it sticks. Game Progress Automation – Rule Behavior Go to Options > Game Progress Automation and test the automation system. There are two default rules: Games played for over 30 minutes move to Active / In Progress Games not played for 30 days move to Active / Paused Try customizing the time values and the target progress states. You can also disable automation entirely and confirm that game progress is no longer updated automatically. NAS Management – IP Repair and Guest Access If you have imported games from a network share (SMB), a new NAS Management page will be nice to test under Options. You can test features like: Scanning for updated IP addresses Manually updating an IP address Adjusting saved credentials or switching to a Guest account Let us know if all your networked games launch correctly after making changes. Loading Page Performance Startup times should now be noticeably faster for large game libraries. For example, a library of 5000 to 8000 games should see about a 60% improvement in startup speed compared to previous versions. Sorting and Filter Behavior Sorting issues should now be resolved. Try different sorting options and filters across multiple views and confirm that games are being sorted correctly in all cases. Beta 1 Changelog Game Progress Tracking has arrived on Android, giving you full control to manually update your game's progress status right from the game menu Added a new Game Progress Automation page that can automatically update a game's progress based on custom rules you define Added a new Game Progress Organization page with drag and drop support to reorder or customize your progress states using defaults or your own values Added a new NAS Management page under Options where you can view your mapped drives, check their connection status, and repair broken links by scanning or updating the IP address Improved performance on the loading page to reduce wait times for large game libraries Fixed an issue where the Banner Filter view could jump or shift when the list was shorter than the device width on newer versions of Android Fixed an issue where sorting games did not always arrange them in the correct order Known Issues Beta 1 You can delete Categories and Values from the Game Progress Organization section right now when you shouldn't. If a game is using one of those values, deletion should not be allowed. This will be fixed in Beta 2 Game Progress Automation for moving games to Active / Paused after a number of days only works under specific conditions. A startup check to apply this more broadly is planned for Beta 2 Thanks all. Every beta tester helps shape the future of LaunchBox for Android. Your testing and feedback make all the difference.

I have a stupid question... How do I install these overlays? I have a lot of them, but I don't know how to use them?! When I start RetroArch and go to Overlays, there are 0 entries?! Where do the .cfg files and PNG images belong?

🧠 Beta Spotlight Feedback – Suggestions for Improving the Experience First off, I wanted to say thank you for implementing the Beta Spotlight window feature. I think we had a conversation about this idea only last week, and it’s great to see it make its way into the beta so quickly. It’s a fantastic addition that helps testers understand what’s new, where to focus, and how to provide meaningful feedback. After reviewing the new 13.25 beta 1 rollout and the Spotlight window, I wanted to share a few ideas for refining it further and making it even more intuitive for a broad range of testers—especially those who may not think like developers or QA professionals. 💡 Suggested Improvements Display the Beta Version Number Include the current beta version number directly in the Beta Spotlight modal window (e.g., “LaunchBox 13.25 Beta 1” at the top). This helps testers quickly confirm which build they’re testing when reporting findings or referencing specific behavior. Refine the Layout – Split into Two Clear Sections Top Section: “Welcome to the Beta” – a brief overview, general testing guidelines, and instructions on how to provide feedback. Bottom Section: When future betas release, consider adding a tabbed layout, where each tab corresponds to a specific beta version (e.g., 13.25b1, 13.25b2, etc.). Each tab could contain: New Features Improvements Fixes / Performance Updates Areas Where Feedback Is Most Helpful Why Version Tabs Matter Having separate tabs per beta helps users correlate when certain changes were introduced. For example, if a user joins the beta program at beta 4 and something behaves differently than expected, they might not realize that behavior changed back in beta 3. With a per-version tab structure, testers can look back through previous beta notes and quickly identify when a feature or behavior changed, reducing confusion and improving the quality of feedback provided. Clarify the Testing Language The current “What We’d Love You to Test” phrasing is friendly but might sound a bit directive to some users. Suggestion: Reframe it as “Areas Where Feedback Is Most Helpful” or “Things You Can Help Us Test” to emphasize collaboration rather than obligation. Add a Section for Feedback Guidance Many users may not know what kind of details the team needs when submitting reports. Adding a brief “How to Give Useful Feedback” section could help, with examples like: Steps to reproduce Expected vs. actual results Platform or theme in use Screenshots or logs (if applicable) Future Consideration – Access to Previous Betas It might be valuable to give advanced testers the option to download older beta versions for testing or comparison. For instance, if a tester is on beta 4, they could choose to download and install beta 2 in a separate directory to verify when a change occurred. This would be a useful tool for seasoned beta users who want to perform regression testing or isolate when a specific bug or change was introduced. If implemented, it would be important to include a clear note reminding users not to install an older beta over their current one in the same folder, to avoid version conflicts or data corruption. 🧩 Overall Impression The new Beta Spotlight feature is a major step forward in structured testing and communication. It provides clarity, direction, and a stronger feedback loop between the community and development. With a few layout refinements and some added context around version tracking, it could become an even more powerful tool for guiding testers and gathering high-quality, actionable feedback.