Results 1 to 20 of 76
Thread: [VS] Outfit guide
05-04-2013, 06:08 PM #1
[VS] Outfit guide
The guide will be collaboratively produced and then this first post updated with the final product.
Design brief is here:
This is not collaborative, though I will make any additions and changes that are needed if people suggest them.
Collaborative guide is here:
Please add to that and comment. I want this to be a joint effort. We can all write, so the barrier to engagement is very low. If I end up writing this mostly myself, I will not be pleased.
The guide will be hosted on the website
LINKS TO BE PLACED HERE.
Last edited by Cooper; 02-06-2013 at 01:38 AM.Originally Posted by CROCONOUGHTKEY
05-04-2013, 06:24 PM #2
05-04-2013, 06:50 PM #3
Looks good as an outline. I'll see if I can contribute some suggestions for content once my new system drive is installed and I'm off this bloody phone.
So happy to see this coming about!
05-04-2013, 06:57 PM #4
- Join Date
- Dec 2012
Looks absolutely spot on.
05-04-2013, 09:38 PM #5
Little bit on outfit history, perhaps?
If not for the guide, we still need this for the website id say, so it might be worth having a section for this in some collaborative document.
NOTE TO COOPER: As ive said before, I set up an email to be used for "rpsgiraffey" things, and its the one i use for the youtube.. If we want to use this as a port of call and general contact/enquiries I can give you access to it cooper... It is "firstname.lastname@example.org" though, so im not sure if you would want that as our contact or not.. Up to you
08-04-2013, 03:34 PM #6
Starting to collect comms guides that have been witten:
I CANNOT FIND THESE GUIDELINES
And bugger me if I'm gonna trawl 50+ pages of outfit discussion to find them.
If you have written comm guidelines before, please post a link below so they can be added to the reference document.
Originally Posted by CROCONOUGHTKEY
08-04-2013, 04:02 PM #7
Added link to guide to edit in front post.
Anyone can edit, Google account or no.Originally Posted by CROCONOUGHTKEY
08-04-2013, 05:10 PM #8
Dunno if this is useful in any way:
'Tis a guide to basic radio communication. Not sure how intricate we are gonna make things but it never hurts to know a bit about basic radio comms."Time is a companion, travelling with us on the journey of life, to remind us to cherish each moment as it will never come again. What we leave behind is not as important as how we lived."
12-04-2013, 11:18 AM #9
A guide to squad Radio Operators (ROs)
A short guide to becoming an accomplished radio operator. I have enough confidence in my own abilities in this role to type something up about it. Have a look and feed back any comments or observations you might have!
What a Radio Operator is:
The radio operator (RO) is the player in a squad who is connected to the platoon command channel. ROs from the squads in a platoon share a channel with the Platoon Leader (PL), this channel is called the platoon command channel.
The RO's job is to relay orders from PL to the Squad Leader (SL), so that the SL can implement the orders. RO also relays intel and situational reports (sitreps) and any requests from the SL (reinforcements, permission to switch objectives etc) to the PL.
The RO's purpose is to allow the SL to focus entirely on directing his/her troops on the battlefield.
What your job is:
- Receive orders from command
- Relay orders to squad
- Report in when arriving at objective
- Give sitreps, relay intel and requests as needed during the mission
- Report progress to command
- Request new orders in good time, so that the squad can move on once the objective has been completed or know where to regroup if it fails
How to be a good RO:
- Edit: Your first priority is relaying PL's orders to your squad and its SL and to keep your PL informed of your squad's progress. You will be less effective as a soldier, and this is to be expected.
- State your squad name in all communication ("Charlie requesting new orders")
Orders and objectives:
- Acknowledge orders ("Charlie to Sungrey West satellite, roger")
- When arriving at objective, report in ("Charlie arrived at The Ascent, no resistance")
- Ask for new orders when it is evident that the current objective is achieved, which is often well before the cap has gone through ("Charlie here, The Bastion is ours soon, requesting new objective")
- Give sitreps from time to time, to keep PL informed of what is going on
- State your location when giving sitreps ("Charlie arrived at The Ascent, no resistance")
- Relay sitreps from other squads to your squad, your squaddies will thank you for it
- When you spot or encounter a significant enemy or friendly force, relay that intel to the platoon command channel ("Charlie spotted significant enemy air above Sungrey")
- Be specific when relaying intel ("Charlie meeting heavy resistance at Blackridge, at least three squads of infantry")
- ROs should be the only squad members in the platoon command channel, to free SLs up from the command chatter.
- ROs and PL should be made Priority Speakers in Mumble, so that command chat gets a priority over squad banter.
- Brevity! Think before speaking. Formulate a good, short reply, request or report before you start talking.
Last edited by EsotericReverie; 03-05-2013 at 06:22 PM. Reason: Added a note on brevity
12-04-2013, 11:31 AM #10
12-04-2013, 11:32 AM #11
- Join Date
- Mar 2013
So this isn't meant to be a how-to-play-the-game guide. Do we currently have a how-to-play-the-game guide of some sort? ie recommendations on class builds and weapon buys and various tricks its useful to know.
I know this stuff is available elsewhere, but if you don't know what you're looking for it's damn hard to separate the good advice from the bad.
12-04-2013, 11:36 AM #12
Absolutely excellent Esoteric"Time is a companion, travelling with us on the journey of life, to remind us to cherish each moment as it will never come again. What we leave behind is not as important as how we lived."
12-04-2013, 11:52 AM #13
Thanks for the feedback! If you find something you'd like to add or clarify or something you don't agree with, let me know. I've just added a section with a checklist of tasks:
Last edited by EsotericReverie; 12-04-2013 at 11:54 AM.
12-04-2013, 01:10 PM #14
Esoteric, in my opinion you should certainly consider continuing to write these guides. You seem to have a real knack for it. Theyre easy to understand and very informative. Only if you want to though, of course. I would post one about SL or PL myself, but due to my recent absences i'm completely out of the teamplay bubble. Given that fact though, i will certainly add suggestions for you to include when my memory is inevitably sparked.
12-04-2013, 01:50 PM #15
Relay sitreps from other squads to your squad, your squaddies will thank you for it - These can also be highly relevant, if a squad in a neighbouring base meets heavy resistance in form of air or armor, it will give your squad leader an opportunity to reorder his squad with bursters/heavies etc. as he sees fit.
12-04-2013, 02:57 PM #16
12-04-2013, 02:58 PM #17
12-04-2013, 04:13 PM #18
Guide to Squad Leaders (SLs)
What a Squad Leader is:
The Squad Leader (SL) is the person who directs the squad towards achieving its objectives, and makes and implements any tactical decisions. The SL calls for vehicle spawns and loadout changes as required to implement whatever tactics he or she is pursuing.
The SL also places squad spawn beacons, that can be used to direct drop pods for squad members.
As SL, your primary responsibility is to make sure that your squad is working together, making what progress you can, and most of all feeling engaged and having fun. The SL is generally not on the platoon command channel.
What your job is:
- Receive orders from your Radio Operator (RO)
- Decide how to best achieve your objectives
- Decide on any pertinent squad tactics (smoke cover, tank rush, stealth etc.)
- Ensure the appropriate squad setup (classes, loadouts, vehicles)
- Ensure that your squad works together towards your objective
- Added: Coordinate with other squad leaders using your SL-to-SL chat!
- Ask your RO to relay any information or request you might have to command
- And most importantly: try to ensure that everyone is having a good time
How to be a good SL:
- Squad cohesion (sticking together) is incredibly important, both for your effectivenes as a unit, and for your sense of companionship
- Remember to use your spawn beacon!
- Most people won't mind being told what to do (to a certain extent); it gives a sense of purpose, and being part of a greater whole
- When playing with newer players, make sure that they understand what's going on, and that they get to feel useful despite being new to the game
Earning your squad's respect:
- Have a plan, it must not be a good plan, but have one
- Be assertive, but not aggressive! ("OK, Charlie squad, this is how we're gonna do it!")
- Talk a lot; make it clear that you are present and dedicated to the squad's performance and well-being
- Lead by example, be the first into the breach, the first to the landing zone etc.
- Having forward spawns cannot be overestimated. Always ensure that there is a Sundedrer near your objective. Enemy Sunderers are priority targets.
- Aggression is effective, even across open ground against tanks and aircraft, if you can back it up with good medics and/or nearby Sunderers
- Be proactive with anti-air capability; always bring a burster
- Enforce swift redeployment, whether it is by Galaxy or Sunderer or Flash mob. 60 seconds is more than enough for a tight unit to load up and get going. Start a countdown if time is of the essence!
- Know where you are expected to go next, and make sure that you have the transportation needed considering the terrain etc.
- Having a dedicated Galaxy pilot never hurts
Last edited by EsotericReverie; 03-05-2013 at 06:20 PM. Reason: Added an entry about the SL-to-SL comms.
12-04-2013, 04:22 PM #19
- Join Date
- Jul 2012
- Switzerland, GMT+1
Wouldn't it be good if the requirements of those different roles were written also? So people can identify what they need to work on?
Like SL needs a basic knowledge of classes and of what weak against what and such
while RO needs a little training at multi-tasking (with the standard attention span of RPS readers, it shoudn't be a problem...)
12-04-2013, 04:26 PM #20