<mark>This post has been edited by a moderator. Please do not post spam.</mark>
*Original post. Click at your own discretion.
So here’s my take on the title of this post.
Challenge: break the engine. fix it. break it again. rinse and repeat!
I believe “find bugs, fix bugs” is already a standard approach for QA. What exactly are you suggesting?
That’s the basic premise of a flighting program. You release a build of the game, let people play it and discover the bugs in the system, fix those bugs, and repeat with subsequent flights.
Thx, now I know how to release a game. In lamen terms…