Jump to content

What It Means To Pug Command


4 replies to this topic

#1 ValdnadHartagga

    Member

  • PipPipPipPipPipPip
  • 422 posts
  • LocationBehind enemy lines

Posted 05 August 2013 - 05:39 PM

I just got a really good feeling from playing this round and got inspired to post this.

Posted Image

Command means having a full load of ammo and no weapons hits from directing a very successful defensive play near the end of the round. Giving the "search and destroy" order when only one enemy remains, and letting the rest of the team have the fun of finding him playing dead amidst two DCs on the opposing base, while watching home base just in case. Command is the joy of watching seven random PUG players choose to come together and risk following a plan (and having some of them ask you to be their friend/leader). It's also about typing very quickly and bringing up the Battlegrid every ten seconds. I don't use voicecomm because I want to be able to reach every player on the team.




Some things I would suggest for every commander:
  • Don't just plug a command into the Battlegrid. Use chat to reinforce your tactics - repeat the order and coordinates. If possible, give a reason why. Be a person, not an icon on the minimap.
  • Assign individual tasks when possible. People love being part of a team if they have something to contribute - ask scouts to investigate or cap areas by name. Make an assault player the center of your advance force. And always ask or suggest until you know your team trusts your decisions ("Player, suggest you scout tunnel" or "Player, think you can scout the tunnel for us?"), rather than force them to listen to you. Not everyone likes being told what to do, but asking doesn't hurt anybody's feelings.
  • Accept teammate input. Just because no one else stepped up to command doesn't mean they don't know the map or have a good tactic that works. If you don't think a player has a good plan, explain why. Encourage players to become lance leaders.
  • Get dirty/pull double duty. Sometimes you have to be in the thick of it to give the best tactical advice. My command 'Mechs are a CPLT-C4 and CN9-D. In the Cat, I'm providing midrange direct missile support and commanding between salvos, in the Cent I'm scouting or skirmishing. Don't command the team to do anything you wouldn't risk in your own 'Mech. Sacrifice yourself for the team if need be.
  • Advise your commander if you don't have company command (and take the lance command if it means something to you). At the end of the day we're all just random players in a game, but respecting the chain of command encourages other commanders to be better at what they do and sets an example for the rest of the team.
  • Accept that not every PUG wants to be commanded. Sometimes being a leader means stepping back - if they're not playing along with you, play along with them.
  • Thank the team, no matter what happens.
Kudos to everyone who chooses to command, and those who choose to follow. You guys make this game awesome.

Edited by ValdnadHartagga, 05 August 2013 - 05:40 PM.


#2 Tesunie

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • The Seeker
  • The Seeker
  • 8,610 posts
  • LocationSeraphim HQ: Asuncion

Posted 05 August 2013 - 06:38 PM

You make great points, and I've had teams that worked just like you said. I've had other teams out right ignore and do the opposite of suggestion. But still, command is not an easy job, and I think you nailed a lot of it on the head.

As for me, I found it was too much work to try and relay a detailed plan, but when I did and people listened, oh my... One of the first matches I won on Alpine was when I took command and gave suggestions of a plan. We followed the plan, and we won. (Not saying my plans are always good, but some plan is better than none most times.)

#3 Master Q

    Member

  • PipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 440 posts

Posted 05 August 2013 - 07:06 PM

What it really means to PUG command:
  • Take command.
  • Issue an initial battle plan
  • Watch the 3-4 guys on a teamspeak team utterly ignore you and run off.
  • Watch another guy try to run off the map and sigh heavily.
  • Watch the brain-donor "testing his weapons" shoot 3 friendlies in the back armor.
  • Give up ever PUG-commanding again.


#4 Bartholomew bartholomew

    Member

  • PipPipPipPipPipPipPipPip
  • Urban Commando
  • Urban Commando
  • 1,250 posts
  • LocationInner sphere drop point

Posted 05 August 2013 - 07:37 PM

Sometimes it works, and it is a beautiful thing when it does. When it doesn't, shrug and try to do what it takes to win.

#5 Caswallon

    Member

  • PipPipPipPipPipPipPip
  • Survivor
  • Survivor
  • 540 posts
  • LocationArboris

Posted 06 August 2013 - 04:42 AM

View PostMaster Q, on 05 August 2013 - 07:06 PM, said:

What it really means to PUG command:
  • Take command.
  • Issue an initial battle plan
  • Watch the 3-4 guys on a teamspeak team utterly ignore you and run off.
  • Watch another guy try to run off the map and sigh heavily.
  • Watch the brain-donor "testing his weapons" shoot 3 friendlies in the back armor.
  • Give up ever PUG-commanding again.

  • Deep breath
  • agree
  • Been there, wish them luck...
  • Have T-SHirt for this
  • Drink heavily and wish Team killing was not against the T&C
  • TRY AGAIN NEXT TIME as sometimes you get a realley great bunch of N00bs that appreciate the direction and do well..
As an aside. I would like to publically thank the other 5 players in a PUG I led two days ago on Alpine. 6-2 Victory (I was one of the kills leading by example [blatent plug I know but pertanent to the OP's point])

If I could recall your names I'd pin a medal on each of you for restoring my faith that occasionally PUG commander gets a good crew.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users