Leaderboard

Tried doing some logos of my own. Right now I'm not that good with text. The Secret Saturdays: Beasts of the 5th Sun (DS, Wii, PS2, PSP) PQ: Practical Intelligence Quotient (PSP) And here is Spectre

Critical Mass

Crossword Magic

Crime Stopper: The Hijacked Heiress Caper

Create with Garfield!

Computer Foosball

few more done

It does indeed look someone took a shot at it😁

where oh where to put the chapter text 😁

Space Quest II

Space Quest

Space Quest IV

Did this one before, just enlarged it.

Broderbund...one of my all time fav producers. Raid on Bungeling Bay, lode runner...my God,...does time fly

CrossCheck

Close as I can get it.

Craps

Crisis Mountain

Cosmos Mission

Computer Napoleonics: The Battle of Waterloo

Computer Gin Rummy

Computer Statis Pro Baseball

Doki Majo Plus - GBA (submitted to db)

more done, releasing soon 4 more to do then part 1 is ready a-c

Computer Baseball

Doki Doki Majo Shinpan! Doki Doki Majo Shinpan!2

🧠 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.

I think this means Twinkle Dream デ・ジ・キャラット

Clue: Master Detective

Clowns & Cars

Elemental Monster エレメンタルモンスター ～五柱神の謎～

Breath: Toiki wa Akaneiro (ブレス 吐息は茜色)