From 794ff4078f6122eee2ab12045a53679b24a2658f Mon Sep 17 00:00:00 2001
From: Daniel Schadt <kingdread@gmx.de>
Date: Sun, 21 Jul 2019 13:24:12 +0200
Subject: [commanding] some smallish fixes

---
 commanding/commanding.tex | 34 +++++++++++++++++++++++-----------
 1 file changed, 23 insertions(+), 11 deletions(-)

(limited to 'commanding/commanding.tex')

diff --git a/commanding/commanding.tex b/commanding/commanding.tex
index adfc551..d381364 100644
--- a/commanding/commanding.tex
+++ b/commanding/commanding.tex
@@ -197,7 +197,7 @@ First of all, you should find a map.
 All the groups and communities that organize Triple Trouble on a regular basis use the \emph{IP Coordination Spreadsheet} in order to not clash with each other.
 If you organize a run, make sure that you are on a map that is not yet claimed, and make sure that you claim the map for your group.
 
-In order to find out on which IP you are on, you can use the \texttt{/ip} in-game command.
+In order to find out which IP you are on, you can use the \texttt{/ip} in-game command.
 This will give you back a bunch of numbers separated by a dot, and a \texttt{:0} at the end.
 This IP allows you to identify the map instance that you are on.
 Normally, the last part before the colon is enough to uniquely identify the map, which is why we only care about that - it is easier to keep one number in mind than 4.
@@ -208,6 +208,12 @@ Normally, the last part before the colon is enough to uniquely identify the map,
   \caption{IP output. In this example, \emph{98} would be the relevant number.}
 \end{figure}
 
+\begin{infobox}[Split IPs]
+  In very rare circumstances, it can happen that two different map instances share the same IP address.
+  This case is rare enough that you can safely ignore it, but it is useful to have heard about.
+  We call this situation a \enquote{split IP}, and you will notice if the other group has tagged up already, but you can't see the tags on your map.
+\end{infobox}
+
 Make sure to divide the wurm heads between the commanders, so that each commander has a head assigned.
 There are no set rules on how to decide, so communicate if you have specific preferences!
 As for TTT, keep in mind that trainees have the first pick over fulltags.
@@ -227,6 +233,12 @@ You can advertise your squad on the LFG tool, usually in the \emph{Open World} $
 You can use the map and say chat to advertise the run to people already on the map and get them to join one of the squads.
 And if you are on TeamSpeak or Discord, you can post your \enquote{sqjoin} there, so people can use it to join your squad.
 
+\begin{infobox}[Taxi Names]
+  If you use the \texttt{/sqjoin} command, you do \emph{not} have to use the character that you are currently on!
+  Any character name that belongs to your account works, so you can choose the shortest one or the one that is easiest to type out.
+  Some commanders even create special character names just for that purpose.
+\end{infobox}
+
 While you are waiting for people to join, make sure that you have the special roles (egg blockers and husk handlers) that you need, and ensure that people in your squad are actually on the correct map as well.
 
 Note that this part should be done about 30 minutes before the event starts.
@@ -264,9 +276,9 @@ If the eggs will not be destroyed in time, they will hatch into \href{https://wi
 If eggs will hatch, focus on clearing the remaining eggs first - remember that eggs can always produce more larvae, but larvae will not produce any more eggs.
 You can use projectile reflection or destruction skills to block the larvae's attacks.
 
-Generally, you want to move the whole squad forwards to the next egg location, while only leaving one person behind to \enquote{escort} the NPC.
+Generally, you want to move the whole squad forwards to the next egg location, while leaving only one person behind to \enquote{escort} the NPC.
 This single person is enough to get rid of any stray mobs, while the zerg can focus on clearing the eggs as soon as possible.
-When the eggs spawn, they will be invulnerable, however they will turn vulnerable once the NPC is close by, which happens fairly fast on Cobalt and Amber.
+When the eggs spawn, they will be untargetable, however they will turn targetable once the NPC is close by, which happens fairly fast on Cobalt and Amber.
 
 On each path, there will be a single \href{https://wiki.guildwars2.com/wiki/Champion_Partially_Digested_Husk}{\emph{husk}} appearing.
 Keep in mind that husks have a very high toughness, so you cannot hurt them by using power damage.
@@ -518,11 +530,11 @@ However, if your keg running is slow, you will end up in a situation where the s
 And even if the keg will be removed, it will already have started a new explosion timer, which means the problem can self-amplify if you're not careful.
 
 It can therefore be worth waiting a bit longer before you attempt to get another burn phase, just to make sure that all the explosion timers will have expired.
-It also means that the longer the keg run is (that is the time between placing the first keg and the final keg), the longer the time period in which you will have kegs disappearing is.
+It also means that the longer the keg run is (that is the time between placing the first keg and the final keg), the longer the time period in which you will have kegs disappearing will be.
 This is why synchronized keg running is important at Cobalt, to prevent timer issues.
 
 The explosion timer is also something that you have to keep in mind when telling other commanders that you are ready.
-If you give the call right after your safety burn, and Amber goes immediately, then by the time that they have done their mechanic, you will run into all the explosion timers when you attempt to get your burn phase.
+If you give the call right after your safety burn, and Amber goes immediately, then by the time that they have done their mechanic, you will run into all the explosion timers when you attempt to get your final burn phase.
 
 
 \subsection{The Burn Phase}
@@ -531,10 +543,10 @@ The burn phase is the same on every wurm head.
 There is not too much you can command about this during the event, as a lot of it has to be done before the event starts (making sure that people bring the right skills, making sure that people have melee weapons equipped, \textellipsis).
 
 When the burn phase starts, you should move inside of the wurm and stand on the double damage spot.
-This gives people a point of reference to stand.
+This gives people a point of reference to stand and stack on.
 If you see people standing around, attacking the wurm at range, make sure to tell them to move in - even if they use a ranged weapon, their damage will still be increased by the sharing of boons and other profession specific enhancements.
 
-You can use the chat to give commands and remind people about their skills, calls like \enquote{banners down} or \enquote{fire fields \& blast them}.
+You can use the chat to give commands and remind people about their skills, making calls like \enquote{banners down} or \enquote{fire fields \& blast them}.
 Additionally, you can call for \emph{Time Warps} and other \enquote{long cooldowns} when you see that people have enough might, or a few seconds after the burn phase has started.
 
 If you are doing a safety burn, keep in mind to tell people early enough to stop their damage, especially if you have a lot of condition damage in your squad, as those will continue to damage the wurm.
@@ -564,7 +576,7 @@ You want to stack between the wurm and the closest wall.
 
 Additionally, you should learn the wurm animations so that you can call out dodges.
 This is a bit harder in say-chat wurms than on TeamSpeak, because the delay is a lot bigger.
-The wurm will also not do the same attack twice in a row, which is why you can call for dodges prematurely if you see the wurm doing a wiggle.
+The wurm will also not do the same attack twice in a row, which is why you can call for dodges prematurely if you see the that wurm is doing a wiggle.
 
 \begin{triviabox}
   When \emph{Signet of Humility} still did 1000 breakbar damage, you could usually break the wurm's defiance bar with just a few Chronomancers.
@@ -596,7 +608,7 @@ Depending on the blocker, you might also need to handle some unexpected eggs and
 This can make a run a bit more chaotic, especially on Amber, where husks can disrupt the zerg while stacking up.
 
 Depending on the amount of people that you have with you, or the amount of new people, you might have issues getting burn phases on e.g. Cobalt due to bad keg running.
-A commander should coordinate the squad and make sure that they don't descend into chaos with all the explosion timers!
+A commander should coordinate the squad and make sure that the run don't descend into chaos with all the explosion timers!
 
 Additionally, not all people might listen due to various reasons.
 They might not know better, they might not understand English that well, they might not be in your squad, they might just try and get an achievement, or in the worst case, they might be intentionally trolling.
@@ -607,9 +619,9 @@ A good commander is someone who can make the right decisions even in tough and u
 
 All of those however are not things that you can just read about or list in a document.
 They are things that come with experience, and as such, you can learn them by commanding and getting feedback from other commanders.
-This is why at TTT we have feedback from other commanders and the trainee passport, so that commanders can learn from the experiences of other commanders and they can talk and discuss about different decisions.
+This is why at TTT we have feedback from other commanders and the trainee passport, so that we can learn from the experiences of each other and we can talk and discuss about different decisions.
 
-\textbf{Always keep in mind that smooth seas don't make good sailors.}
+\textbf{Always keep in mind that smooth seas don't make good sailors}, so try to see those runs as a learning experience and a rewarding challenge rather than as a negative thing.
 
 
 \section{Dealing With Failures}
-- 
cgit v1.2.3

