Editing Calling
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help pages.
Latest revision | Your text | ||
Line 6: | Line 6: | ||
==Basics== | ==Basics== | ||
− | Calls play an essential part in competitive play, so they should be treated as such and given special attention and work. Calling isn't often trained or practiced and most of the calling attributes a player has come from actual competitive experience, so it is natural for new players to feel overwhelmed by it or not being able to make proper calls | + | Calls play an essential part in competitive play, so they should be treated as such and given special attention and work. Calling isn't often trained or practiced and most of the calling attributes a player has come from actual competitive experience, so it is natural for new players to feel overwhelmed by it or not being able to make proper calls. |
'''A call should be concise and clear, only with relevant information and no gibberish.''' It should also be spoken in a calm way that is understood by everyone, raging or shouting often only leads to a worse team atmosphere. | '''A call should be concise and clear, only with relevant information and no gibberish.''' It should also be spoken in a calm way that is understood by everyone, raging or shouting often only leads to a worse team atmosphere. | ||
Line 27: | Line 27: | ||
=== Main Calling in 6v6 === | === Main Calling in 6v6 === | ||
− | The main caller is usually the [[Soldier | Pocket Soldier]], the [[ | + | The main caller is usually the [[Soldier | Pocket Soldier]], the [[Medic]] or the [[Demoman]]. This is because most 6v6 teams will focus their play around their combo to make use of über and general health advantages. That being said, a class that plays a big part in or around the combo is often recommended as a maincaller. However this is not true for all cases, as there are teams which have far more experienced players on flank positions that have good main calling abilities. |
=== Main Calling in Highlander === | === Main Calling in Highlander === | ||
Line 34: | Line 34: | ||
== Communication system == | == Communication system == | ||
− | The in-game voice system is virtually unused in competitive play as it isn't perfect nor offers the amount of audio quality and customization the players need. So there are plenty of alternatives used, from TeamSpeak to Ventrillo | + | The in-game voice system is virtually unused in competitive play as it isn't perfect nor offers the amount of audio quality and customization the players need. So there are plenty of alternatives used, from TeamSpeak to Ventrillo, but the one that has become the staple of the competitive Team Fortress 2 community is [http://mumble.sourceforge.net/ '''Mumble'''], as it is very lightweight, open source, and also offers good audio quality and customization. Most teams will use this software to communicate and even the most active [[Glossary#PUG.2C_Pickup | PUGs]] or [[Glossary#Mix | Mixes]] channels/websites will enforce it, so it is an essential piece of software to the competitive scene. |
[[Category:Mechanics]] | [[Category:Mechanics]] |