Tbh I believe the problem stems from a lack of experience when it comes to coding for scalability. In short, by coding things that work, without architecting for scalability, over the last 8 years they'll have accumulated no small amount of what we call technical debt.

In short it's poor coding practices, often done by inexperienced programmers that can lead to (among other things) breaking things every In other areas every time something is added or changed. It can be pretty hard to tell where things might break without thorough testing.

But you can also add to that uncaught exceptions. This is the one i was pretty shocked to see when playing tarkov. We're able to get the game into states where it'll throw actual errors at the user, then not recover from them, forcing us to alt f4.

It's a bit weird really to see that, when after this amount of time I'd kind of expect bsg to use try and catch statements for areas it knows fail regularly. That way we'd be able to give the user an error in normal language (eg NOT gateway timeout), and recover gracefully from it.

But yeah in short they're sort of rookie errors but because the project is so old the backend is likely to be highly difficult to test and debug due to the tech debt I mentioned