Slaughter mode was actually fun until the server booted everybody

[Buff_Archer]

First match, Adders were actually winning by a lot, team having a good time and getting achievements for first kill (and yes does seem to be killshot based, but that's for another thread). Got LB'd, revived at landing, and went to transporter but it didn't work. Couldn't dismount etc, figured ok great its a Frontline 90k Special coming up. But got disconnected after maybe half a min with a different error message. Couldn't reconnect like with a standard Frontlines 90k, had to close game and reopen, when I returned I was out instance and found out from party members I had joined with that it booted everyone. The thought was maybe too many were at mid and it brought the server down for the entire instance.

Let's assume that's the cause of it- can't really coordinate across the three GC's how many people go mid to prevent a server crash. And really there should have been enough stress testing on the system to be sure it could handle all that.

Wasted time sitting in queue, for an instance that provided 0 rewards because simply ended itself after a few minutes. This is not a Qualty of Life issue with the game, it's a big freaking deal. Why would I run Frontlnes roulette if I'm going to have a high probability of going into an instance that will crash and give me nothing for my trouble?

[Defeat]

Can confirm this, haven't happened to me ( Never getting a queue pop. ), but other people and my other FC members went through that. Frontlines servers need some fixing, seriously.