Difference between revisions of "Voice Communications in PvP"

From Agony Unleashed
Jump to: navigation, search
(Archiving old BASIC material)
 
(23 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 
[[Category:Agony]]
 
[[Category:Agony]]
[[Category:PVP University/BASIC]]
+
[[Category:PVP University/Frigspec]]
 
[[Category:PVP_University/WOLFPACKS]]
 
[[Category:PVP_University/WOLFPACKS]]
 +
[[Category:PVP_University/FLEET COMMAND]]
 
[[Category:PVP University]]
 
[[Category:PVP University]]
<p align="Left"><small>
+
[[Category:Public]]
Original text by [http://www.agony-unleashed.com/user.php?id.1780 Spinward]<br>
+
Copyright Agony Unleashed
+
</small></p>
+
 
+
 
+
 
__TOC__
 
__TOC__
  
Line 14: Line 10:
 
=== Introduction ===
 
=== Introduction ===
  
A really well written article regarding what to expect and how to react in respects to voice communications in an Agony Training Gang. This was written by a student(Spinward) for other students, in an effort to make some of the jargon and concepts easier to get to grips with. If some of this goes over your heads whilst reading this, don't be too concerned, your instructor will cover this with you and it should all fall into place once you experience it firsthand.
+
This article covers the topic of voice communications in PVP-U fleets. It was originally written by a student, Spinward, who eventually joined Agony, in an effort to make some of the jargon and concepts easier to get to grips with. Don't be too concerned if you don't understand some of what is written here. When the class start on its 0.0 roam it will all fall into place once you experience it firsthand.
  
''First, the disclaimer: I'm not Agony. I'm not an instructor. I'm a week one noob who took a class!!!''
+
There's a lot of information here and it may take a few reads before it sinks in, but you're paying a lot to attend this class (ISK and time) and I think this will help you make the most of your investment. Besides, the more you know when you arrive, the easier it will be to focus on the fun stuff: bringing death and destruction to the enemy!
  
I just finished the accelerated PVP Basic course last night and thought I would share some of my notes with future students. Reading this post might make you a little more confident and save some time in class. Have a great time; I did.
+
=== IMPORTANT VOICE COMS TIPS ===
  
After attending a few more Basic courses as alumni, I'm now a three month noob! I have added a little more info and re-arranged the post to make it flow a little better. Even so, there's a lot of information here and it may take a few reads before it sinks in but you're paying a lot to attend this class (ISK and time) and I think this will help you make the most of your investment. Besides, the more you know when you arrive the easier it will be to focus on the fun stuff: bringing death and destruction to the enemy!
+
When you set up your push-to-talk button, '''do NOT''' set it to be one of the control (CNTRL) keys on your keyboard. If you do, every time you CNTRL-click to target a ship, you will key up in voice and drive everyone nuts and piss off the FC.
  
=== General ===
+
Avoid using desktop speakers and a microphone (especially a desktop microphone) at the same time.  Your microphone will pick up everything coming out of your speakers, which leads to loud and painful feedback.  This is true even with fancy noise-cancelling microphones.  Headsets are cheap - even a $10 headset is better than playing voice coms over your desktop speakers.
  
Voice communications (in this case vent) is an invaluable resource for a fleet. It allows you to act and react faster than the enemy. Good disciplined comms lets the Hydra Fleet to maximize its effectiveness because the FC (Fleet Commander) can coordinate the weight of weapons and EWAR on the enemy's vulnerabilities. The Fleet depends on mobility and surprise; both of these are hard to maintain without voice comms.
+
We love music, and we know you love music, too. Playing Eve to your favorite band is epic stuff. Please be aware that loud music (or television) in the background WILL be heard over your microphone. Use some common sense and good judgment in setting your background music volumes.
  
 +
Don't use voice modulators or voice changers.  While sounding like Daffy Duck is amusing, it is also extremely difficult - if not impossible - to understand anything you say.  It's also annoying and likely will get you muted, if not kicked out of a fleet.
  
=== Voice Comms vs Text Chat ===
+
=== General ===
  
There tends to be some confusion about when you should use voice comms and when you should use text chat. In general, voice is used in the theory section for answering questions and having a proper discussion with the instructor. Text chat can be used for administrative things such as late arrivals (try to avoid this), ventrillo problems (always seem to be a few) and asking for links to the Agony Fleet Manager Tool (you'll love this application when you see it).
+
Voice communications is an invaluable resource for a fleet. It allows you to act and react faster than the enemy. Good disciplined comms allows the Hydra Fleet to maximize its effectiveness because the FC can coordinate damage and EWAR on the enemy's vulnerabilities. The Fleet depends on mobility and surprise; both of these are hard to maintain without voice communications.
  
While training in low sec, you should still ask questions and carry on a discussion with the instructor. However, if the fleet is approaching a gate, don't use voice for questions so that the FC can listen for recon and intelligence reports. You always want to know what's on the other side of the gate and sometime reports come in at the last second. Keep using text chat for admin and it is great for easy to answer shorter questions. If you raise an important point in text, the instructor or one of the agony members will bring it up on vent so that everyone can benefit.
+
=== Voice Comms vs Text Chat ===
  
In 0.0, you have to be even more selective about when to talk on vent. However, it is your class so don't be afraid to use vent to ask questions. Just listen before you key your microphone so that you don't "step on" someone else's question. If you hear "break break", "recon" or "battlecomms", stay quiet until the urgency passes. The word "urgency" is really the key to using vent. Voice comms are used when things are urgent because seconds count and typing is too slow. If there's nothing "urgent" going on, get your questions going. These instructors have tons of information for you so dig it out of them.
+
There tends to be some confusion about when you should use voice comms and when you should use text chat. In general, voice is used for immediate information, intelligence, fleet orders, and other time-critical communications. Text chat can be used for administrative things such as late arrivals (try to avoid this), voice problems (there are always a few), questions, reporting non-time-critical intelligence, and general chit-chat.
  
'''Battle comms:''' When the FC (or for the purposes of a class, anyone) calls Battle comms, all students should be quiet and listen for orders. During this time, the FC will be hearing reports, issuing orders or just taking a moment to think. It's our time, as students, to hold questions on vent. If its something urgent, you can still use gang or squad chat to type your question.
+
During a roam, you have to be selective about when to talk in voice. It is important to listen before you key your microphone so that you don't "step on" someone else's question/reporting/etc. If you hear "recon," "break-break," "clear comms" or "battlecomms", stay quiet until the urgency passes. The word "urgency" is really the key to successful voice communications. Voice comms are used when things are urgent because seconds count and typing is too slow.  
  
'''Break Break:''' Someone has urgent information on the fleet's tactical situation for the FC. Everyone listen up; hopefully, it's your next victim.
+
'''Battle comms:''' When the FC (or for the purposes of a class, anyone) calls battlecomms, all members of the fleet should be quiet and listen for orders. During this time, the FC will be hearing reports, issuing orders or just taking a moment to think.  
  
'''Recon:''' The ships out ahead or behind the gang with key information will start their report by saying "recon". The gang leader needs this info so save your questions for later or put them in gang chat.
+
'''Break Break:''' Someone has urgent, emergency-level information on the fleet's tactical situation for the FC. Everyone listen up; hopefully it's about your next victim.  In a well-run, well-supported fleet, "Break Break" is used very, very rarely.
  
 +
'''Recon:''' The scouts that are flying ahead or behind the gang will start their report by saying "Recon". "Recon" is the equivalent of "Shut up!" :)  The FC needs to hear this info, and so do you, as it is information on our next victim!
  
 
=== You, Me and I ===
 
=== You, Me and I ===
  
Don't use these pronouns. Instead always identify yourself with your name. Refer to yourself in the third person (like that Seinfeld episode) "George is getting angry" and "Jimmie needs a new pair of shoes". It definately feels weird at first but start doing it every time you talk...even in the theory section. Just say "This is George. Why should jammers be on manual?" It makes it easier for the instructors to keep track of who's asking (they do watch the vent as well) but I also think it helps people get in the mindset for when they get into space. Now in 0.0, it becomes much more important. The FC needs to know who is talking or you are wasting valuable seconds by forcing him to ask "who said that".
+
Avoid speaking in the first person in voice. Instead always identify yourself with your character's name. Refer to yourself in the third person (like that Seinfeld episode) "George is getting angry" and "Jimmie needs a new pair of shoes". It definitely feels weird at first, but start doing it every time you talk in voice. Just say "This is George. Why should jammers be on manual?" It makes it easier for the instructors to keep track of who's asking and it also helps everyone get into the right mindset for when they get into 0.0 space. Now in 0.0, it becomes much more important. The FC needs will sometimes need to know who is talking. By not identifying yourself you are wasting valuable seconds of your FC's time by forcing him or her to ask "who said that??".
  
Once you have some more PvP experience, you should be able to get around 0.0 by yourself, and may not need help from the FC. If that is the case and vent is busy, just type your report/info into gang chat and say something along the lines of "no assistance needed". The FC may come pick you up anyway because he wants to look after all his students but he may not because there are 29 other students to look after as well.
+
'''Here's a couple examples of brevity or the lack thereof:'''
 
+
'''Here's a couple examples of brevety or the lack thereof:'''
+
 
+
'''Wrong:''' Did you jump? I think I missed the jump. The lag is killing me. Is everyone lagged?
+
'''Better:''' (if you need help): George is still in E-3 at the D-0 gate. Lagged. Request orders.
+
'''Best:''' (you don't need any help): George is lagged OR George is behind.
+
 
+
Now that's not the only right way but I hope it's a good example of brevity, precision and using the third person. It also leads me right to my next few points.
+
  
 +
'''Wrong:''' Did you jump? I think I missed the jump. The lag is killing me. Is everyone lagged?<br>
 +
'''Better:''' (if you need help): George is still in E-3 at the D-0 gate. Lagged. Request orders.<br>
 +
'''Best:''' (you don't need any help): George in E-3, system is friendly.<br>
  
 
=== Brevity and Precision ===
 
=== Brevity and Precision ===
  
Be precise when you make a report. Tell him who, where and what but keep it as short as possible. Eventually, you'll be a good PVP'r with a gang that knows you and you can cut it down even farther but in the class, no one knows your voice and the instructor is trying to keep 30 students on the move (read herding cats).
+
Be precise when you make a report. Tell the FC who, where, and what, but keep it as short as possible. If you practice PVP quite a bit and often fly with a particular gang in game, those players will come to remember your voice and you can cut your reporting down even more. However, in class, nobody knows your voice and the instructor is trying to keep 50+ students on the move (read herding cats).
 
+
Be very careful confusing warp and jump, especially if you are providing intel. Providing bad intel gets FCs ticked of very quickly.
+
  
=== Don't be a "narrator". ===
+
=== Don't Be a "Narrator" ===
  
 
In these examples, Jimmie is the tackler and George is in our fleet; Easy Meat is the target ship.
 
In these examples, Jimmie is the tackler and George is in our fleet; Easy Meat is the target ship.
  
'''Jimmie:''' "one point Easy Meat"
+
'''Jimmie:''' "point on Easy Meat"<br>
'''FC:''' "everyone warp to Jimmie"
+
'''FC:''' "everyone warp to Jimmie"<br>
'''George:''' "ok, I'm warping to the gate..... got him locked and webbed... ok missiles away... he's targetting me now.... he's shooting...I'm tanking pretty well, at 80% shields...into armor now....he's into structure...muhahaha I do crazy dps....he's dead"
+
'''George:''' "ok, I'm warping to the gate..... got him locked and webbed... ok missiles away... he's targeting me now.... he's shooting...I'm tanking pretty well, at 80% shields...into armor now....he's into structure...muhahaha I do crazy dps....he's dead"<br>
  
All the details are interesting to you, but there's zero reason to be broadcasting it on vent. Comms should be limited only significant details to the FC (namely ewar calls and immediately significant intel).  
+
All the details are interesting to you, but there's zero reason to be narrating them in voice. Comms should be limited to only those details that are significant to the FC.  
  
'''A better example might be:'''
+
'''A better example might be:'''<br>
  
'''Jimmie:''' "one point Easy Meat"
+
'''Jimmie:''' "Point on Easy Meat"<br>
'''FC:''' "everyone warp to Jimmie"
+
'''FC:''' "everyone warp to Jimmie"<br>
'''George:''' "web"...."Easy Meat is aggressed"
+
'''George:''' "web on Easy Meat"...."Easy Meat is aggressed"<br>
'''FC:''' "get the pod"
+
'''FC:''' "get the pod"<br>
 
+
This way, the FC knows that the target has a web on it and, since he has aggressed, cannot go through the gate. You haven't used up much time on vent so the FC is free to be thinking and listening for intel to plan our next kill.
+
  
 +
This way, the FC knows that the target has a web on it and, since he has aggressed, cannot go through the gate. You haven't used up much time in voice, so the FC is free to be thinking and listening for intel to plan the next steps.<br><br>
  
 
=== Saying the J word ===
 
=== Saying the J word ===
Line 87: Line 77:
 
'''''Jump is an order to be given by the Fleet Commander only.'''''
 
'''''Jump is an order to be given by the Fleet Commander only.'''''
  
As a student, I pretty clearly understood that there's no need for a student to ever say the J word. Try not to say it five times while talking back to the instructor about how "warping off instead of going through the gate wasn't your fault"...yeesh...it was not pretty. If there's time, the instructor will usually play it out to see how many times you'll say the J word before you realize it. I'm not sure but they may have a bet going every class!
+
There is a good reason for never using the J word. Imagine you are on a gate waiting for your scout to tackle someone on the other side. You are keyed up with the excitement of the upcoming kill (the adrenalin really starts flowing on those first few kills) and someone says "So when do we jump?". What your mouse finger heard was JUMP and you are gone, gone, gone. No calling it back; your brain is still translating the "blah blah blah JUMP" but not fast enough to stop that damn finger.
 
+
There is a good reason for avoiding the J word. Imagine you are on a gate waiting for your scout to tackle someone on the other side. You are keyed up with the excitiment of the upcoming kill (the adrenalin really starts flowing on those first few kills) and someone says "So when do we jump?". What your mouse finger heard was JUMP and you are gone, gone, gone. No calling it back; your brain is still translating the "blah blah blah JUMP" but not fast enough to stop that damn finger.
+
 
+
There are some euphemisms you can use instead of the J word: "We are 7 systems from our destination", "The target went out the gate", "go through the gate", "four gates to go" etc.
+
 
+
Someone does this every class so try not to let it be you by starting the habit now! (It does become a habit...I'm even hesitating before I type the J word in these notes)
+
  
 +
There are some euphemisms you can use instead of the J word: "We are 7 systems from our destination", "The target went out the gate", "go through the gate", "four gates to go," "I hopped out," etc.
  
 
=== The J word vs Warp ===
 
=== The J word vs Warp ===
  
Warping is done within a system while you have to use a gate to Jump. Don't get them mixed up when talking to the FC. It can be a completely different tactical situation when you report that the ship you are targetting "warped off" or "went through the gate".
+
Warping is done within a system, jumping is done between systems. Don't get them mixed up when talking to the FC. It is a completely different tactical situation when you report that the ship you are targeting "warped off" or "jumped through the gate".<br><br>
  
 +
=== Chatting ===
  
=== Chatting and Talking Back ===
+
If you have a question, ask it; I'll bet at least one or two other people have the same one but are afraid to ask. We are here to answer your questions.  It is important to ask questions, but even more important to do so appropriately. 
  
There's probably going to be a good Vent chit chat going on between the instructor, the Agony pilots and some course alumni. They know when to chat and when to keep their mouths shut. I didn't so I kept mine shut unless I had a question. If you have a question, ask it; if you have it, I'll bet at least one or two other people have the same one but are afraid to ask.
+
During our class days, the instructors will usually ask that you type a "Q" in fleet chat when you have a question, then will have you ask your question in voice the moment he/she is able to take the question.
  
This is the "talking back" portion. The instructors expect mistakes to happen. Why else would we be in the class? More important than any mistake is how you handle yourself afterwards. So if you do make a mistake, identify yourself and get to where you are supposed to be. It had to happen to someone and this time it's you. No big deal, next time it'll be someone else. If you need help, you'll get it (the other Agony pilots were a great help) but don't talk back or try to launch into a long explanation of what happened and how it isn't your fault. They've been teaching a long time an know that 'stuff' happens so just say "on my way" and get on with the grunt. That next kill might be just through the gate and we all want a piece of it.
+
During our roams, questions can always be asked freely in fleet chat, during bio breaks, and depending upon the situation, they may also be asked in voice during really slow portions of the roam (if any) - such as when we're traveling through friendly space, or sitting at a safe-spot and nothing else is going on. When in doubt, ask in fleet chat first if you can ask a question in voice.
  
Students Chatting and Vent -> By chatting, I mean shooting the sh... er... breeze (idle chit chat about pizza or wow or whatever). You can do it at the right times but if you can keep it in the text chat, you will keep your FC happy. The FC will call battlecomms if s/he needs vent clear.
+
=== Mistakes ===
  
 +
The instructors expect mistakes to happen. Even the most experienced pilots make mistakes!  More important than any mistake is how you handle yourself afterwards. So if you do make a mistake, identify yourself and get to where you are supposed to be. It had to happen to someone and this time it's you. No big deal, next time it'll be someone else. If you need help, you'll get it, but don't talk back or try to launch into a long explanation of what happened and how it isn't your fault. 'Stuff' happens so just say "on my way" and get on with it.
  
 
=== Going through a gate ===
 
=== Going through a gate ===
  
When you approach a gate, the Gang Leader will give you your orders. If he's busy and doesn't give orders, the default instruction is to orbit at 500m (1000m if previously directed). If you don't hear any orders, go with the default. If you think you missed or aren't sure you heard the order, ask "orders on the gate?" There were a few standard orders used in the class but they can also be mix and match depending on the Gang Leader.
+
When you approach a gate, the Fleet Commander will give you your orders. If he's busy and doesn't give orders, the default instruction is to '''Hold on Gate''', meaning you should orbit at 500m/1000m (i.e. well within jump range, which is 2500m). Other orders your FC is likely to use are:
  
'''Jump on contact''' - go through the gate as soon as you are out of warp
+
'''Jump on contact''' - go through the gate as soon as you land on the gate<br>
'''Jump and hold cloak''' - go through the gate immediately but do nothing to break your cloak on the other side. That means don't move or cycle weapons/ewar. The priority is keeping your cloak up so that you don't betray the fleet's position.
+
'''Jump and hold cloak''' - go through the gate immediately but do nothing to break your cloak on the other side. That means don't move or cycle weapons/ewar. The priority is keeping your cloak up so that you don't betray the fleet's composition. Remember: The first to decloak is the first to die!<br>
'''Align''' - bring your ship around to point at the next stargate (normally double click beside the gate. If everyone is heading the right direction, the warp looks fast and tight)
+
'''Align''' - bring your ship around to point at the next stargate.<br>
'''Jump and Align''' - go through the gate and quickly align to the next stargate
+
'''Jump and Align''' - go through the gate and quickly align to the next stargate<br>
'''Jump and Re-approach''' - go through, break cloak and use afterburner to get to the gate. Orbit at 500/1000m
+
'''Jump and Re-approach''' - go through, break cloak and use afterburner to get to the gate. Orbit the gate at 500/1000m<br>
 
'''Jump, Jump''' - go through the gate immediately
 
'''Jump, Jump''' - go through the gate immediately
  
The default for arriving on the other side without orders is to "Orbit 1000 and cycle weapons and ewar", so you are as ready as possible. Just make sure you didn't miss the "stay cloaked command or you could ruin your ambush. Personally, if I'm not 100% sure, I stay cloaked and ask. That said, usually the FC will say "reapproach" or "power reapproach" at least three or four times so you aren't likely to miss it.
+
The default order after going through a gate is to '''Hold Cloak''' (i.e. do not do anything - you'll remain cloaked for up to 60 seconds).
  
Do not shoot the gate. When cycling weapons and ewar, it is vital that you don't shoot the gate. If you do, you can end up aggressed and prevented from going through on the FC's orders. This holds up the class or ruins an ambush or gets you podded and you have to make a long run to catch up. If this happens, stay calm and make a report. You'll be given instructions. If the FC is busy in an attack and you're in immediate danger, warp away to stay safe and then catch up when you can. The instructors will help you as soon as they can. They really do want you to live, learn and kick butt during this class.
+
Do not shoot anything unless the FC has told you to. If you do, you will end up with a weapons timer ("aggressed") and unable to go through the gate for 60 seconds. This can hold up the class, ruin an ambush, or get you podded, and you'll have to make a long run to catch up. If this happens, say "Friendly out" in voice, stay calm and make a Recon report. You'll be given instructions. If the FC is busy in an attack and you're in immediate danger, warp away to stay safe and then catch up when you can. The instructors will help you as soon as they can. They really do want you to live, learn and kick butt during this class.
  
If you do end up aggressed and alone on a gate with enemies inbound, the best place you can warp to is an asteroid belt, planet or the star. On the way, create a midsafe bookmark, and immediately warp to it. Then you can proceed to make a safespot that is greater than 15 AU from any celestial object, and you should be relatively safe.
+
If you do end up aggressed and alone on a gate with enemies inbound, the best thing to do is get safe. Warp to a celestial object and make a safe-spot en route, or possibly even re-approach the gate and return to the fleet. What you should do is situational, so use what you have learned in the class and make your best judgement call.  
  
If you end up going through a gate alone and there's nothing but the enemy on the other side and have no idea what to do next, here's your plan. Don't break cloak. Do a scan. Warp out fast. (If you can warp out to a place that you are already aligned to, you're ahead of the game.) As soon as you arrive, warp out again to confound pursuit. While you're warping, read your scan and make a good report to the Gang Leader. For example, "Recon, two Raven and two frigates in K-T 100km off gate 7-U". After your second warp (third if you're worried), put your speed on so no one drops on top of you and figure out your next move.
+
If you end up going through a gate alone and there's nothing but the enemy on the other side and have no idea what to do next, here's your plan. Don't break cloak. Do a scan. Then warp out fast. (If you can warp out to a place that you are already aligned to, you're ahead of the game.) As soon as you arrive, warp to another location in system again to confound pursuit. While you're warping, drop a mid-safe bookmark and read your scan and make a good report to the FC. For example, "Recon, two Ravens, Hurricane, and two Raptors in K-T 100km off 7-U gate".  
 
+
If you are late going through a gate or joining the gang say "Friendly incoming" just to avoid an uncool panic or friendly fire accident. Actually, if vent is clear, you can start saying "Friendly incoming to X-70" as soon as you start getting close to catching up so the FC can keep track of where you are. He may have orders for you or ask for information.
+
  
 +
If you are late going through a gate or joining the gang say "Friendly in" just to avoid a panic or friendly fire accident.
  
 
=== Electronic Warfare Orders and Reporting ===
 
=== Electronic Warfare Orders and Reporting ===
  
You will be broken up into squads, Track Groups (Tracking Disruptors) and Damp Groups (Sensor Dampeners). When you go into battle, your group will be given targets for weapons and EWAR modules. Here's a quick list of the voice call that you use when a module is active on your assigned target. Don't make the call until your module is active but if you can't hold the module on target (ie running out of cap) let the EWAR leader know before it drops.
+
The fleet may be broken up into several EWAR groups: Track Groups (ships with tracking disruptors) and Damp Groups (ships with sensor dampeners). When you go into battle, your group will be given targets for weapons and EWAR modules. Here's a quick list of the voice calls that you use when a module is active on your assigned target.  
  
'''Active Module''' - what you say
+
'''Warp Disruptor''' - Point<br>
'''Warp Disruptor''' - Point
+
'''Warp Scrambler''' - Scram<br>
'''Warp Scrambler''' - Scram
+
'''Sensor Dampener''' - Damp<br>
'''Sensor Dampener''' - Damp
+
'''Stasis Webifier''' - Web<br>
'''Stasis Webifier''' - Web
+
'''Track Disruptor''' - Track<br>
'''Track Disruptor''' - Track
+
'''Target Painter''' - Paint<br>
'''Target Painter''' - Paint
+
'''Jammer''' - Jam<br>
'''Jammer''' - Jam
+
  
You might also hear such things as "Easy Meat is primary" or "get a point on him" or "web him". Most of the communications was pretty self explanatory but that list above was just the one word. When you're in Track Group One and you hear "Track Group One on Easy Meat", you get that TD on target and, once you see the icon on the target, you say "Track". The exception is for Jammers. You are not actually jamming until you see the grey countdown bar underneath the locked target. That's when you call "Jam". There's a lot more to jamming that most of the other ewar modules but you'll have to read about that elsewhere.  
+
You might also hear such things as "Easy Meat is primary" or "get a point on him" or "web him". When you're in Track Group One and you hear "Track Group One on Easy Meat", target Easy Meat's ship and put your TD on it. Once you see the icon on the target, say "Track". One exception is for Jammers. You are not actually jamming until you see the grey countdown bar underneath the locked target. That's when you call "Jam".
  
If things are going well or, alternatively, things go badly, you may end up engaged with more than one target. The procedures are the same but now the FC has to order and hear reports on two or more targets. For two targets, the orders might be "Easy Meat is primary. Damp Group Two on Easy Money." Everyone will be engaging Easy Meat except that Damp Group Two will be attacking Easy Meat while locking Remote Damps on Easy Money. This means that EWAR reports need to include the name of the target pilot. For example, you might hear the following reports: "Point on Easy Meat; Web on Easy Meat, Damp on Easy Money" and so on.... I think this is beyond the Basic class but you can see that it would be impossible for the FC to keep track of the situation without including the target's name in EWAR reports.
+
You may end up being engaged by more than one target. The procedures are the same but now the FC has to order and hear reports on more than one target. For two targets, the orders might be "Easy Meat is primary. Damp Group Two on Easy Money." Everyone will be engaging Easy Meat except that Damp Group Two will be attacking Easy Meat while locking Remote Damps on Easy Money. This means that EWAR reports need to include the name of the target pilot. For example, you might hear the following reports: "Point on Easy Meat; Web on Easy Meat, Damp on Easy Money" and so on....  
  
Now if you lose track, run out of cap, have to warp away or get podded, you have to inform the Gang that the EWAR module is down. That's when you would say "Minus one point" or "Lost damp". You'll also need to tell the leader if you are out of the fight or coming back. If possible, try to make the report before you actually lose track or run out of cap. Once again, jamming is a little different. Remember to call "lost jam" before the countdown timer runs out. That way another pilot can try to replace you before the point or web or damp is actually lost.
+
Now if you lose track, run out of cap, have to warp away or get podded, you have to inform the Gang that the EWAR module is down. That's when you would say "Minus one point" or "Lost damp". Jammers will call "lost jam" when they lose a jam on a target.
  
For example, Jimmie has been targetted by the Vagabond your fleet is killing:
+
For example, Jimmie has been targeted by the Vagabond your fleet is killing and has to warp off to avoid dying:
  
'''Jimmie:''' "Warping out, minus one point, will return"
+
'''Jimmie:''' "Minus one point"
 
+
Remember there are no reports for locking target, firing, losing shield or getting into armour. It seems to happen all the time and you can't take up time on Vent that's needed to coordinate the battle.
+
  
 +
Remember there are no reports for locking target, firing, losing shield or getting into armor. The FC does not need to know this information.<br><br>
  
 
=== Broadcast - the red-headed step child of Eve Communications ===
 
=== Broadcast - the red-headed step child of Eve Communications ===
  
People don't talk much about broadcast but it's used every gang. The broadcast window appears on the lower right hand portion of the overview underneath the Fleet Window. In PvP Basic, it is used primarily to send navigation orders.
+
People don't talk much about broadcasting, and it's not used nearly as much as it should be by many fleets. The broadcast window appears on the bottom of the fleet window. In PvP Basic, it is used primarily to send navigation orders.
 
+
The FC will say "destination broadcast" (or something like that) so you find it, right click and select set destination. Alternatively, the FC may say "waypoint broadcast". Now a waypoint and a destination look the same in the broadcast window so you have to listen. If the FC says "waypoint" you, find it, right click and select set waypoint.
+
 
+
There can be problems sometimes so here's a few tips. If you try to set destination and you get the error message "cannot set the same destination", don't stop there. Go back to the broadcast, right click the destination, select remove waypoint. Then try setting the destination again.
+
  
The other problem I've seen is when a destination and a couple waypoints are broadcast at the same time. Sometimes people set them in the wrong order and confusion sets in. Normally, the first one is the destination and the rest are waypoints. So set the first as destination, then set the next one above as a waypoint, then the one above that and so on. If you have any doubts, use gang text chat to confirm that the the destination is (for example) x-70 and there are 9 systems to go. If you're wrong it, you can sort it out before you align to the wrong gate and are tackled because incorrect alignment slowed down your warp.
+
The FC will say "destination broadcast."  Look at the bottom of your fleet window, right click on the broadcast and select set destination.  
  
 +
Your fleet window has a tab labeled "History" - here you can find a history of all broadcasts made throughout the fleet.  This is a good place to look if you missed an order or a broadcast.
  
 
=== Duties - just the basics ===
 
=== Duties - just the basics ===
  
There are a few of the duties that you'll hear talked about. It's unlikely you'll get one but it's nice to know what they are all about.
+
There are a few of the fleet roles you may here the FC mention:
  
'''XO''' - Executive Officer. A second in command who deals with administration, squads, damp/track groups etc. This frees up the FC to think about tactics. In Basic, this is an assistant instructor and the XO term may not even be used.
+
'''XO''' - Executive Officer. A second in command who deals with administration, squads, damp/track groups, fleet invites, fleet balancing, broadcasting, tracking of stragglers, and tracking non-time-critical intelligence, etc. This frees up the FC to think about tactics. Also known as "cat herder" and "fleet secretary." In Basic, this is often one of the instructors and the XO term may not even be used.
  
 
'''EWO or EWARO''' - Electronic Warfare Officer. If the Fleet is big enough you might have one of these who coordinates the ewar groups for the FC.
 
'''EWO or EWARO''' - Electronic Warfare Officer. If the Fleet is big enough you might have one of these who coordinates the ewar groups for the FC.
  
'''Scout, Recon, Skirmisher''' - these guys all do different things depending on their ships and skills but, for our purposes, they are all eyes in other systems finding us targets. Listening to how they report and the questions the FC asks them has really helped me.
+
'''Scout, Skirmisher''' - these guys all do different things depending on their ships and skills but, for our purposes, they are all eyes in other systems finding us targets.  
  
 
'''360 Scan''' - An agony pilot or alumni or two will be assigned the duty of constantly scanning for threats. Everyone should be doing this on a regular basis but by assigning the duty, the FC is just making sure he's always got someone scanning for targets/threats.
 
'''360 Scan''' - An agony pilot or alumni or two will be assigned the duty of constantly scanning for threats. Everyone should be doing this on a regular basis but by assigning the duty, the FC is just making sure he's always got someone scanning for targets/threats.
  
'''Local''' - An agony pilot or alumni will be watching local to see if the number goes up or down in your system. He or she will also try to find the incoming pilot's information for the FC. Ideally, the local pilot reports one new pilot in system, their name and alliance to the FC at the same time that the 360 scan pilot reports a new Iteron in system.
+
'''Local duty''' - An agony pilot or alumni will be watching local to see if the number goes up or down in your system. He or she will also try to find the incoming pilot's information for the FC. Ideally, the local pilot reports one new pilot in system, their name and alliance to the FC at the same time that the 360 scan pilot reports a new Iteron in system.
  
'''Probe Scan''' - Normally agony or alumni assigned to scan for probes that may be used to track down your fleet when in a safe. Alternatively, detecting these probes gives us the info that a cloaked covops is in system.
+
'''Probe duty''' - Normally agony or alumni assigned to scan for probes that may be used to track down your fleet when in a safe. Alternatively, detecting these probes gives us the info that a cloaked covops is in system.
  
 
'''Rear Guard''' - Normally an agony pilot assigned to follow the gang last through a gate. He's kind of the herder to bug you if you're slow to go through and to tell the FC when everyone is in the next system.
 
'''Rear Guard''' - Normally an agony pilot assigned to follow the gang last through a gate. He's kind of the herder to bug you if you're slow to go through and to tell the FC when everyone is in the next system.
 
 
That's all folks. Hope it was of some value.
 
 
Cheers. I hope to see you in my sights soon as you try to warp your pod away from my Rifter of Doom! Enjoy PvP; I am.
 

Latest revision as of 17:36, 5 March 2016

Communications in PvP

Introduction

This article covers the topic of voice communications in PVP-U fleets. It was originally written by a student, Spinward, who eventually joined Agony, in an effort to make some of the jargon and concepts easier to get to grips with. Don't be too concerned if you don't understand some of what is written here. When the class start on its 0.0 roam it will all fall into place once you experience it firsthand.

There's a lot of information here and it may take a few reads before it sinks in, but you're paying a lot to attend this class (ISK and time) and I think this will help you make the most of your investment. Besides, the more you know when you arrive, the easier it will be to focus on the fun stuff: bringing death and destruction to the enemy!

IMPORTANT VOICE COMS TIPS

When you set up your push-to-talk button, do NOT set it to be one of the control (CNTRL) keys on your keyboard. If you do, every time you CNTRL-click to target a ship, you will key up in voice and drive everyone nuts and piss off the FC.

Avoid using desktop speakers and a microphone (especially a desktop microphone) at the same time. Your microphone will pick up everything coming out of your speakers, which leads to loud and painful feedback. This is true even with fancy noise-cancelling microphones. Headsets are cheap - even a $10 headset is better than playing voice coms over your desktop speakers.

We love music, and we know you love music, too. Playing Eve to your favorite band is epic stuff. Please be aware that loud music (or television) in the background WILL be heard over your microphone. Use some common sense and good judgment in setting your background music volumes.

Don't use voice modulators or voice changers. While sounding like Daffy Duck is amusing, it is also extremely difficult - if not impossible - to understand anything you say. It's also annoying and likely will get you muted, if not kicked out of a fleet.

General

Voice communications is an invaluable resource for a fleet. It allows you to act and react faster than the enemy. Good disciplined comms allows the Hydra Fleet to maximize its effectiveness because the FC can coordinate damage and EWAR on the enemy's vulnerabilities. The Fleet depends on mobility and surprise; both of these are hard to maintain without voice communications.

Voice Comms vs Text Chat

There tends to be some confusion about when you should use voice comms and when you should use text chat. In general, voice is used for immediate information, intelligence, fleet orders, and other time-critical communications. Text chat can be used for administrative things such as late arrivals (try to avoid this), voice problems (there are always a few), questions, reporting non-time-critical intelligence, and general chit-chat.

During a roam, you have to be selective about when to talk in voice. It is important to listen before you key your microphone so that you don't "step on" someone else's question/reporting/etc. If you hear "recon," "break-break," "clear comms" or "battlecomms", stay quiet until the urgency passes. The word "urgency" is really the key to successful voice communications. Voice comms are used when things are urgent because seconds count and typing is too slow.

Battle comms: When the FC (or for the purposes of a class, anyone) calls battlecomms, all members of the fleet should be quiet and listen for orders. During this time, the FC will be hearing reports, issuing orders or just taking a moment to think.

Break Break: Someone has urgent, emergency-level information on the fleet's tactical situation for the FC. Everyone listen up; hopefully it's about your next victim. In a well-run, well-supported fleet, "Break Break" is used very, very rarely.

Recon: The scouts that are flying ahead or behind the gang will start their report by saying "Recon". "Recon" is the equivalent of "Shut up!" :) The FC needs to hear this info, and so do you, as it is information on our next victim!

You, Me and I

Avoid speaking in the first person in voice. Instead always identify yourself with your character's name. Refer to yourself in the third person (like that Seinfeld episode) "George is getting angry" and "Jimmie needs a new pair of shoes". It definitely feels weird at first, but start doing it every time you talk in voice. Just say "This is George. Why should jammers be on manual?" It makes it easier for the instructors to keep track of who's asking and it also helps everyone get into the right mindset for when they get into 0.0 space. Now in 0.0, it becomes much more important. The FC needs will sometimes need to know who is talking. By not identifying yourself you are wasting valuable seconds of your FC's time by forcing him or her to ask "who said that??".

Here's a couple examples of brevity or the lack thereof:

Wrong: Did you jump? I think I missed the jump. The lag is killing me. Is everyone lagged?
Better: (if you need help): George is still in E-3 at the D-0 gate. Lagged. Request orders.
Best: (you don't need any help): George in E-3, system is friendly.

Brevity and Precision

Be precise when you make a report. Tell the FC who, where, and what, but keep it as short as possible. If you practice PVP quite a bit and often fly with a particular gang in game, those players will come to remember your voice and you can cut your reporting down even more. However, in class, nobody knows your voice and the instructor is trying to keep 50+ students on the move (read herding cats).

Don't Be a "Narrator"

In these examples, Jimmie is the tackler and George is in our fleet; Easy Meat is the target ship.

Jimmie: "point on Easy Meat"
FC: "everyone warp to Jimmie"
George: "ok, I'm warping to the gate..... got him locked and webbed... ok missiles away... he's targeting me now.... he's shooting...I'm tanking pretty well, at 80% shields...into armor now....he's into structure...muhahaha I do crazy dps....he's dead"

All the details are interesting to you, but there's zero reason to be narrating them in voice. Comms should be limited to only those details that are significant to the FC.

A better example might be:

Jimmie: "Point on Easy Meat"
FC: "everyone warp to Jimmie"
George: "web on Easy Meat"...."Easy Meat is aggressed"
FC: "get the pod"

This way, the FC knows that the target has a web on it and, since he has aggressed, cannot go through the gate. You haven't used up much time in voice, so the FC is free to be thinking and listening for intel to plan the next steps.

Saying the J word

Jump is an order to be given by the Fleet Commander only.

There is a good reason for never using the J word. Imagine you are on a gate waiting for your scout to tackle someone on the other side. You are keyed up with the excitement of the upcoming kill (the adrenalin really starts flowing on those first few kills) and someone says "So when do we jump?". What your mouse finger heard was JUMP and you are gone, gone, gone. No calling it back; your brain is still translating the "blah blah blah JUMP" but not fast enough to stop that damn finger.

There are some euphemisms you can use instead of the J word: "We are 7 systems from our destination", "The target went out the gate", "go through the gate", "four gates to go," "I hopped out," etc.

The J word vs Warp

Warping is done within a system, jumping is done between systems. Don't get them mixed up when talking to the FC. It is a completely different tactical situation when you report that the ship you are targeting "warped off" or "jumped through the gate".

Chatting

If you have a question, ask it; I'll bet at least one or two other people have the same one but are afraid to ask. We are here to answer your questions. It is important to ask questions, but even more important to do so appropriately.

During our class days, the instructors will usually ask that you type a "Q" in fleet chat when you have a question, then will have you ask your question in voice the moment he/she is able to take the question.

During our roams, questions can always be asked freely in fleet chat, during bio breaks, and depending upon the situation, they may also be asked in voice during really slow portions of the roam (if any) - such as when we're traveling through friendly space, or sitting at a safe-spot and nothing else is going on. When in doubt, ask in fleet chat first if you can ask a question in voice.

Mistakes

The instructors expect mistakes to happen. Even the most experienced pilots make mistakes! More important than any mistake is how you handle yourself afterwards. So if you do make a mistake, identify yourself and get to where you are supposed to be. It had to happen to someone and this time it's you. No big deal, next time it'll be someone else. If you need help, you'll get it, but don't talk back or try to launch into a long explanation of what happened and how it isn't your fault. 'Stuff' happens so just say "on my way" and get on with it.

Going through a gate

When you approach a gate, the Fleet Commander will give you your orders. If he's busy and doesn't give orders, the default instruction is to Hold on Gate, meaning you should orbit at 500m/1000m (i.e. well within jump range, which is 2500m). Other orders your FC is likely to use are:

Jump on contact - go through the gate as soon as you land on the gate
Jump and hold cloak - go through the gate immediately but do nothing to break your cloak on the other side. That means don't move or cycle weapons/ewar. The priority is keeping your cloak up so that you don't betray the fleet's composition. Remember: The first to decloak is the first to die!
Align - bring your ship around to point at the next stargate.
Jump and Align - go through the gate and quickly align to the next stargate
Jump and Re-approach - go through, break cloak and use afterburner to get to the gate. Orbit the gate at 500/1000m
Jump, Jump - go through the gate immediately

The default order after going through a gate is to Hold Cloak (i.e. do not do anything - you'll remain cloaked for up to 60 seconds).

Do not shoot anything unless the FC has told you to. If you do, you will end up with a weapons timer ("aggressed") and unable to go through the gate for 60 seconds. This can hold up the class, ruin an ambush, or get you podded, and you'll have to make a long run to catch up. If this happens, say "Friendly out" in voice, stay calm and make a Recon report. You'll be given instructions. If the FC is busy in an attack and you're in immediate danger, warp away to stay safe and then catch up when you can. The instructors will help you as soon as they can. They really do want you to live, learn and kick butt during this class.

If you do end up aggressed and alone on a gate with enemies inbound, the best thing to do is get safe. Warp to a celestial object and make a safe-spot en route, or possibly even re-approach the gate and return to the fleet. What you should do is situational, so use what you have learned in the class and make your best judgement call.

If you end up going through a gate alone and there's nothing but the enemy on the other side and have no idea what to do next, here's your plan. Don't break cloak. Do a scan. Then warp out fast. (If you can warp out to a place that you are already aligned to, you're ahead of the game.) As soon as you arrive, warp to another location in system again to confound pursuit. While you're warping, drop a mid-safe bookmark and read your scan and make a good report to the FC. For example, "Recon, two Ravens, Hurricane, and two Raptors in K-T 100km off 7-U gate".

If you are late going through a gate or joining the gang say "Friendly in" just to avoid a panic or friendly fire accident.

Electronic Warfare Orders and Reporting

The fleet may be broken up into several EWAR groups: Track Groups (ships with tracking disruptors) and Damp Groups (ships with sensor dampeners). When you go into battle, your group will be given targets for weapons and EWAR modules. Here's a quick list of the voice calls that you use when a module is active on your assigned target.

Warp Disruptor - Point
Warp Scrambler - Scram
Sensor Dampener - Damp
Stasis Webifier - Web
Track Disruptor - Track
Target Painter - Paint
Jammer - Jam

You might also hear such things as "Easy Meat is primary" or "get a point on him" or "web him". When you're in Track Group One and you hear "Track Group One on Easy Meat", target Easy Meat's ship and put your TD on it. Once you see the icon on the target, say "Track". One exception is for Jammers. You are not actually jamming until you see the grey countdown bar underneath the locked target. That's when you call "Jam".

You may end up being engaged by more than one target. The procedures are the same but now the FC has to order and hear reports on more than one target. For two targets, the orders might be "Easy Meat is primary. Damp Group Two on Easy Money." Everyone will be engaging Easy Meat except that Damp Group Two will be attacking Easy Meat while locking Remote Damps on Easy Money. This means that EWAR reports need to include the name of the target pilot. For example, you might hear the following reports: "Point on Easy Meat; Web on Easy Meat, Damp on Easy Money" and so on....

Now if you lose track, run out of cap, have to warp away or get podded, you have to inform the Gang that the EWAR module is down. That's when you would say "Minus one point" or "Lost damp". Jammers will call "lost jam" when they lose a jam on a target.

For example, Jimmie has been targeted by the Vagabond your fleet is killing and has to warp off to avoid dying:

Jimmie: "Minus one point"

Remember there are no reports for locking target, firing, losing shield or getting into armor. The FC does not need to know this information.

Broadcast - the red-headed step child of Eve Communications

People don't talk much about broadcasting, and it's not used nearly as much as it should be by many fleets. The broadcast window appears on the bottom of the fleet window. In PvP Basic, it is used primarily to send navigation orders.

The FC will say "destination broadcast." Look at the bottom of your fleet window, right click on the broadcast and select set destination.

Your fleet window has a tab labeled "History" - here you can find a history of all broadcasts made throughout the fleet. This is a good place to look if you missed an order or a broadcast.

Duties - just the basics

There are a few of the fleet roles you may here the FC mention:

XO - Executive Officer. A second in command who deals with administration, squads, damp/track groups, fleet invites, fleet balancing, broadcasting, tracking of stragglers, and tracking non-time-critical intelligence, etc. This frees up the FC to think about tactics. Also known as "cat herder" and "fleet secretary." In Basic, this is often one of the instructors and the XO term may not even be used.

EWO or EWARO - Electronic Warfare Officer. If the Fleet is big enough you might have one of these who coordinates the ewar groups for the FC.

Scout, Skirmisher - these guys all do different things depending on their ships and skills but, for our purposes, they are all eyes in other systems finding us targets.

360 Scan - An agony pilot or alumni or two will be assigned the duty of constantly scanning for threats. Everyone should be doing this on a regular basis but by assigning the duty, the FC is just making sure he's always got someone scanning for targets/threats.

Local duty - An agony pilot or alumni will be watching local to see if the number goes up or down in your system. He or she will also try to find the incoming pilot's information for the FC. Ideally, the local pilot reports one new pilot in system, their name and alliance to the FC at the same time that the 360 scan pilot reports a new Iteron in system.

Probe duty - Normally agony or alumni assigned to scan for probes that may be used to track down your fleet when in a safe. Alternatively, detecting these probes gives us the info that a cloaked covops is in system.

Rear Guard - Normally an agony pilot assigned to follow the gang last through a gate. He's kind of the herder to bug you if you're slow to go through and to tell the FC when everyone is in the next system.