Scouting: Difference between revisions

Line 145:

Most Uni fleets will look for a forward scout and a rear scout, and any number of floating scouts. Forward and floating should be covops ships, rear can be a prototype cloak ship in a pinch, but covops preferred.

Most Uni fleets will look for a forward scout and a rear scout, and any number of floating scouts. Forward and floating should be covops ships, rear can be a prototype cloak ship in a pinch, but covops preferred. You may also see or hear reference to "+1" and "+2" scouts, and sometimes "-1" - these are just another way to refer to forward scouts (staying 1 or 2 jumps ahead of the fleet), or rear scouts (one jump behind).

The forward scout's role is to check each gate before the fleet warps to it. As a forward scout, you want to be able to warp to a gate bookmark, check that the gate is clear and give the go-ahead, then warp to zero on the gate and jump through to check the other side. If you don't have bookmarks, this process gets tougher - you're reduced to either travelling uncloaked (bad), travelling cloaked to the gate (slow), or bouncing off a remote celestial to do a warp to zero when you want to go through the gate. So bookmarks are valuable here.

Rear scouts watch the back of the fleet, to make sure no-one's following. They'll typically stay one jump behind the fleet, and need to watch for neutrals or suspicious behaviour.

Rear scouts watch the back of the fleet, to make sure no-one's following. They'll typically stay one jump behind the fleet, and need to watch for neutrals or suspicious behaviour. This is arguably tougher than forward scout, as you'll need to be watching not only for obvious war targets, but also for neutrals who "happen" to be following or showing up often.

Floating scouts have a slightly freer job - depending on your FC, they'll either be carefully positioned by FC instruction to watch different gates and/or neighbouring systems, or they'll be free to move around and look for WT's. Floating and forward is pretty much interchangable depending on FC decisions.

Reporting war target sightings - do this as calmly as possible, and as clearly as possible. Good reporting would be "command, darius, I have one cerberus on the korsiki gate in osmon, jumping through to you now". Bad reporting would be "hey guys, there's a war target coming at you!". TS discipline in the uni at least is always lead with the channel name (that's "command" in the above example) and your name so the FC knows who's talking where, then provide the ship type and location, optionally war target name and any other details you might have.

A note on TeamSpeak operation - as scout, you are perfectly within your rights to overtalk someone if something urgent comes up - typically you do that by saying "check check" in the command channel, people should then stop and listen.

== Scanning down the opponent: ==

@@ Line 145: / Line 145: @@
-Most Uni fleets will look for a forward scout and a rear scout, and any number of floating scouts. Forward and floating should be covops ships, rear can be a prototype cloak ship in a pinch, but covops preferred.
+Most Uni fleets will look for a forward scout and a rear scout, and any number of floating scouts. Forward and floating should be covops ships, rear can be a prototype cloak ship in a pinch, but covops preferred. You may also see or hear reference to "+1" and "+2" scouts, and sometimes "-1" - these are just another way to refer to forward scouts (staying 1 or 2 jumps ahead of the fleet), or rear scouts (one jump behind).
 The forward scout's role is to check each gate before the fleet warps to it. As a forward scout, you want to be able to warp to a gate bookmark, check that the gate is clear and give the go-ahead, then warp to zero on the gate and jump through to check the other side. If you don't have bookmarks, this process gets tougher - you're reduced to either travelling uncloaked (bad), travelling cloaked to the gate (slow), or bouncing off a remote celestial to do a warp to zero when you want to go through the gate. So bookmarks are valuable here.
-Rear scouts watch the back of the fleet, to make sure no-one's following. They'll typically stay one jump behind the fleet, and need to watch for neutrals or suspicious behaviour.
+Rear scouts watch the back of the fleet, to make sure no-one's following. They'll typically stay one jump behind the fleet, and need to watch for neutrals or suspicious behaviour. This is arguably tougher than forward scout, as you'll need to be watching not only for obvious war targets, but also for neutrals who "happen" to be following or showing up often.
 Floating scouts have a slightly freer job - depending on your FC, they'll either be carefully positioned by FC instruction to watch different gates and/or neighbouring systems, or they'll be free to move around and look for WT's. Floating and forward is pretty much interchangable depending on FC decisions.
 Reporting war target sightings - do this as calmly as possible, and as clearly as possible. Good reporting would be "command, darius, I have one cerberus on the korsiki gate in osmon, jumping through to you now". Bad reporting would be "hey guys, there's a war target coming at you!". TS discipline in the uni at least is always lead with the channel name (that's "command" in the above example) and your name so the FC knows who's talking where, then provide the ship type and location, optionally war target name and any other details you might have.
+A note on TeamSpeak operation - as scout, you are perfectly within your rights to overtalk someone if something urgent comes up - typically you do that by saying "check check" in the command channel, people should then stop and listen.
 == Scanning down the opponent: ==