I wasn’t slamming the idea entirely. But I’m pretty broke, so that’s partly where my self-restraint is coming from. I think what’s more important than an automated system of submitting projects / games for testing is corrections and how-to’s for the engine features, in-depth articles on how to do particular things in the engine, and what’s involved in properly preparing a game for its targeted platforms (from the beginning of creating it moreso than at the end when it’s almost finished). I’m still seeing a slew of the same problems / ‘bugs’ regarding the newest versions of UE posted in the Rendering and ArchViz forums. About half of the stuff could be covered in a few to several how-to articles, available in the forum or elsewhere on the site (other than AnswerHub), and would drastically reduce the time and effort that regular repliers in the forum spend helping on those same issues. I understand certain issues can have different causes and different solutions, so it’s why I’m suggesting a few to several articles which pinpoint the issue(s) and suggest the different workarounds and solutions that have worked for others consistently. And then, perhaps, Epic would notice a change in forum activity and most-posted issues and be capable of developing and improving UE5 according to how that approach to forum help is going.