Has anyone else had the situation where you drop in an 11-man and the 12th is automatically assigned company command?
I've seen it twice with my unit. Both times the person didn't realize that they had it and were happy to give it up, but it seems like a problem. It should at least start open, if not go to the leader of the largest group.


Solo Player Taking Company Command?
Started by Darwins Dog, Dec 15 2014 01:17 PM
7 replies to this topic
#1
Posted 15 December 2014 - 01:17 PM
#2
Posted 15 December 2014 - 01:22 PM
I've had it randomly assign to people. It's why we instantly grab it. Granted, we also mark our plans out on the fly in the map.
#3
Posted 15 December 2014 - 01:24 PM
I think its a bug where hitting JJ can sometimes take command.
You can drop in CW with 11? That's cool. I thought it would cap @ 10 but I guess that wouldn't really matter outside the group MM queue.
You can drop in CW with 11? That's cool. I thought it would cap @ 10 but I guess that wouldn't really matter outside the group MM queue.
#4
Posted 15 December 2014 - 03:46 PM
What's funny is I've actually seen guys try to do that themselves with our 10man. One random PUG seriously thinks he's gonna order around a 10man group with comms.....
#5
Posted 15 December 2014 - 05:32 PM
hitting spacebar in a non jump jet mech will give yourself command. i do it al the time when i switch to a non JJ mech and brain fart.
#6
Posted 15 December 2014 - 05:36 PM
Ph30nix, on 15 December 2014 - 05:32 PM, said:
hitting spacebar in a non jump jet mech will give yourself command. i do it al the time when i switch to a non JJ mech and brain fart.
It also happens with JJ-equipped Mechs under (what I consider) mysterious circumstances.
#7
Posted 15 December 2014 - 05:43 PM
Happened to me this weekend as a scrub pug that got dropped into an 11 man WoL team. I didn't even realize it until right before the first drop door came up, and I quickly gave up command and told them I'd follow whatever they wanted.
I thought maybe that it was because I was the "first one" that had been waiting in the que? But no idea really. I certainly hadn't tried to take command.
And WoL took the victory, inspite of having to carry me as well.
I thought maybe that it was because I was the "first one" that had been waiting in the que? But no idea really. I certainly hadn't tried to take command.
And WoL took the victory, inspite of having to carry me as well.

#8
Posted 15 December 2014 - 05:49 PM
This is not a new bug, it's been happening since closed beta. At that time the general theory was that opening the battlegrid caused it sometimes. If it's the spacebar well, at least that explains what causes it.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users