aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Schadt <kingdread@gmx.de>2019-07-18 01:27:36 +0200
committerDaniel Schadt <kingdread@gmx.de>2019-07-18 01:27:36 +0200
commit782f70c1adb8b2a83214fbc973c2f889b2587860 (patch)
treee2281237a7884200f02b0253f1aeaf66adbd9adb
parentc61a1d1756e84066908af422288ae3772e14c0b6 (diff)
downloadopen-tt-guides-782f70c1adb8b2a83214fbc973c2f889b2587860.tar.gz
open-tt-guides-782f70c1adb8b2a83214fbc973c2f889b2587860.tar.bz2
open-tt-guides-782f70c1adb8b2a83214fbc973c2f889b2587860.zip
start a commanding guide
-rw-r--r--commanding/Makefile2
-rw-r--r--commanding/commanding.tex118
2 files changed, 120 insertions, 0 deletions
diff --git a/commanding/Makefile b/commanding/Makefile
new file mode 100644
index 0000000..ecd4795
--- /dev/null
+++ b/commanding/Makefile
@@ -0,0 +1,2 @@
+NAME=commanding
+include ../Makefile
diff --git a/commanding/commanding.tex b/commanding/commanding.tex
new file mode 100644
index 0000000..ce28d37
--- /dev/null
+++ b/commanding/commanding.tex
@@ -0,0 +1,118 @@
+\documentclass[a4paper]{article}
+
+\input{../preamble.tex}
+
+% Metadata
+\title{Triple Trouble Commanding Guide}
+\author{Peter Parker IV \& others}
+\date{2019-07-15 \color{gray}r0}
+
+\begin{document}
+
+\maketitle
+
+\input{../legals.tex}
+
+\begin{abstract}
+ This guide should give you an introduction of how commanding Triple Trouble works.
+ Furthermore, it can be used as a reference text if you need to look up some information related to the event or being a commander.
+
+ This guide is written from the perspective of a TTT\footnote{\textcolor{red}{Triple} \textcolor{yellow}{Trouble} \textcolor{blue}{Team}(speak), see \url{https://gw2ttt.com}} commander, but of course, a lot of information is generally applicable to the event and not limited to a specific team.
+\end{abstract}
+
+\newpage
+\tableofcontents
+\newpage
+
+\section{Introduction}
+
+If you are reading this guide, you have probably already joined the event as a \enquote{normal} participant and you are interested in learning more about the behind-the-scenes actions, or you are even thinking about trying to command yourself.
+This guide should explain some of the commander mechanics to you, and also act as a reference point regarding the mechanics which are involved.
+
+Some parts of this guide apply to Guild Wars 2 in general, some of them apply to Triple Trouble generally, and some of them apply to TTT specifically.
+As such, depending on your background and intentions, not everything that is said here will hold true for you.
+
+Generally speaking, your job as a commander consists of the following parts, which will be explained in greater detail below:
+
+\begin{itemize}
+ \item
+ \emph{Organizing}:
+ As a commander, it is your job to set up a squad, advertise it, get people into it and make sure that you have the minimum amount of people for your head and that you have all the special roles that you need.
+
+ \item
+ \emph{Explaining}:
+ Since we cannot assume that everyone who joins us knows about the event already or how the mechanics work, we start the event by doing a so-called \enquote{dry-run}, which consists of the commander walking the squad through the event in the in-game chat and/or on TeamSpeak.
+ Depending on the available time, those dry-runs can be very short and concise, but they can also be detailed and venturing into more general Guild Wars 2 combat mechanics (explaining boons, might stacking, \textellipsis).
+
+ \item
+ \emph{Leading}:
+ During the actual event, you are responsible for leading the squad.
+ It is on you to make the relevant calls, such as running kegs on Cobalt, killing the Abomination on Amber, filling Colors on Crimson, etc.
+
+ \item
+ \emph{Coordinating}:
+ Since coordination is key for this event, it is your job to stay in touch with the other commanders and keep them updated about the state of your wurm head.
+ Conversely, you should be aware of the state of the other two heads.
+\end{itemize}
+
+Depending on the team/community that you run wurms with, there can be some other organizational tasks such as keeping track of runs in a spreadsheet, or giving/receiving feedback with other commanders.
+
+
+\section{General (Squad) Mechanics}
+
+This section should give you an overview over some general game and squad mechanics that are applicable for more than just Triple Trouble.
+
+The wiki also has a good overview over a lot of squad mechanics, see \href{https://wiki.guildwars2.com/wiki/Squad}{the \emph{Squad} article}.
+
+
+\subsection{Tagging Up}
+
+The ability to tag up is an account-wide upgrade that you can purchase for 300 Gold and 250 Badges of Honor by buying either the \href{https://wiki.guildwars2.com/wiki/Commander%27s_Compendium}{Commander's Compendium} or the \href{https://wiki.guildwars2.com/wiki/Catmander%27s_Compendium}{Catmander's Compendium}.
+Depending on which compendium you bought, you will have access to either the normal tags, or the catmander tags.
+You can also buy both for a combined price of 450 Gold, giving you access to both types of tags.
+
+Note that there is no functional difference between the normal tag and the catmander tag.
+Only the icon above your head and on the minimap will be different.
+As such, you are free to decide for yourself which type of tag you prefer.
+
+Once you have bought the upgrade, you will be able to create squads by clicking the \enquote{party button} in the left side of the screen (default shortcut: P).
+By clicking \enquote{Create Squad}, you will activate the tag and open a squad.
+You can deactivate your tag again (\enquote{tag down}) by leaving the squad.
+Note that the tag and the squad are closely intertwined:
+It is not possible to show the tag without having a squad, and creating a squad will always activate your tag.
+
+Once you have created a squad, you can use the party UI to change a few squad settings.
+
+\begin{itemize}
+ \item
+ \emph{Raid Mode}:
+ This option will limit the squad members to 10 and allow you to enter raid instances with your squad.
+ For open world events, such as Triple Trouble, you want to leave this option \emph{off}.
+
+ \item
+ \emph{Lock All Subgroups}:
+ If you enable this option, players will not be able to move themselves between different subsquads anymore.
+ For open world events, it doesn't matter too much - the majority of players will stay in subsquad 1 anyway.
+ You can use this option if you notice some people moving around a lot without reason.
+
+ \item
+ \emph{Allow Members to Send Invites}
+ This option will allow other players to invite their friends into the squad.
+
+ \item
+ \emph{Allow uninvited players to join?}
+ Here you can select if you want other players to be able to join the squad without being invited.
+ For open world squads, you generally want this as \enquote{Yes, anyone can join}.
+\end{itemize}
+
+Additionally, you are able to select your tag color or switch between tag types here.
+
+
+\subsection{Subsquad Management}
+
+Each squad can be subdivided into up to 15 \enquote{subsquads}.
+For Triple Trouble, subsquads are mostly used to have the special roles (such as eggblockers or husk handlers) in their own group, so that it's easier to see them at a glance.
+Additionally, if you use the party chat while in a squad, it will only send the message to your current subsquad - this allows blockers to coordinate without affecting the rest of the zerg.
+If you want to message the whole squad, you can use the squad chat (\texttt{/squad} or \texttt{/d}).
+
+\end{document}