Compared to other directions in GameDev, MMO has one giant plus for QA. Namely, these are projects that are just starting to live after release. Those. The usual igruha after release is remembered by the developer as a bad dream, or close to it. Of course, this very release should be as good as possible, but in principle, how to maintain the code or data structure, few people think, and it is not always necessary. βWorks, checked? Well, don't touch anything. β- Very frequent logic. The MMO is completely different. After release, the game should just be in that state when it is convenient and easy to maintain. Accordingly, it is logical to keep the game in this state almost all the time of development, which means that the fans of βAfter us at least a floodβ have very big problems. And not at all because from the point of view of a technical person it is wrong to do so, but because supporting such decisions is usually more expensive and more hemorrhagic, which does not enthuse the management. Naturally, the balance between quality and timing remains, but ... still a very good argument is added to quality here.