I waited a good amount of time to play a 5v5, the game starts, 10 seconds go by, and all of my teams 5 comms light up the sky in a huge explosion. Someone obviously hit "C" and "delete," and just like that, the game was over. Can there be some kind of longer delay for a commander self-detonation, or perhaps an abort button or a tone that sounds when its been set to blow? It's quite infuriating when someone deliberately ruins the game by doing this.
Uber already shown alliance mode, soon griefers won't be problem, but currently possibility to destroy commanders it's not bad thing because it's at least not take more time to join new game.
I'd recommend not playing Army with randoms. It's better to play army with people you know and with on comms.
At the very least we could use a 'Player X Self destructed a Commander' message so we know not to play with that person any more.
This + support for a feature that lets you put players on a list with notes. I usually keep my own list on pencil and paper of people to avoid playing with in the future but I always wish it was just built in. Right click player, "add to list", type "detonated all comms at the start of the match", designate the color to be red and next time I see him in the room, he has a red name and I can click him to read my note. [I could also mark someone's name in green and type "is cool guy, would play with again" so it doesn't have to be purely a list of people to avoid...] "Don't play with randoms" is simply not a realistic solution for a mass market game. The fact is that the huge majority of people will [and do] play with randoms and this must be supported with a proper framework. I'll accept that we don't have this now because it's beta but I think it's very important to have this stuff, and seems relatively simple to do. The list could be stored client-side, even, and then it's just a little bit of UI work to implement it.
