Archive:Logistic Guide: Difference between revisions

Line 123:

The logi channel can be used for the following information:

* Who is the logi anchor (if different than the rest of the fleet's anchor).

* Who should be on the ~~watchlist~~.

* Who should be on the watch list.

* Provide warp-ins for logi pilots that have just joined fleet, or missed warps, etc.

* Who you should anchor on (and orbit range).

Line 171:

You should sort the Blue Logi overview by name. The cap chain for Guardians and Basilisks is normally 2 down, meaning you should look for the two pilots that are below your name in the overview list when it is sorted alphabetically, and activate one cap transfer module on each. You must skip over Scimitars and Oneiros, you should never give cap to these ships in normal circumstances.

If you are in a guardian or basilisk, you should be cap stable with two cap transfers if you have logi 4, and one cap transfer of you have logi 5. The cap chain is set up 2 down even if those who receive cap have logi 5. This insures redundancy in combat situations where the cap chain is often broken when ships are destroyed. You should keep an eye on your ~~watchlist~~ and overview and be ready to change cap transfer targets if necessary.

If you are in a guardian or basilisk, you should be cap stable with two cap transfers if you have logi 4, and one cap transfer of you have logi 5. The cap chain is set up 2 down even if those who receive cap have logi 5. This insures redundancy in combat situations where the cap chain is often broken when ships are destroyed. You should keep an eye on your watch list and overview and be ready to change cap transfer targets if necessary.

You should NOT rely on the logi channel list for the cap chain ordering. The logi channel will include non-cap transferring logi, sometimes the FC or other commanders, pilots that have had their ships destroyed, pilots that are off grid, pilots that are in another system, etc.

@@ Line 123: / Line 123: @@
 The logi channel can be used for the following information:
 * Who is the logi anchor (if different than the rest of the fleet's anchor).
-* Who should be on the watchlist.
+* Who should be on the watch list.
 * Provide warp-ins for logi pilots that have just joined fleet, or missed warps, etc.
 * Who you should anchor on (and orbit range).
@@ Line 171: / Line 171: @@
 You should sort the Blue Logi overview by name. The cap chain for Guardians and Basilisks is normally 2 down, meaning you should look for the two pilots that are below your name in the overview list when it is sorted alphabetically, and activate one cap transfer module on each. You must skip over Scimitars and Oneiros, you should never give cap to these ships in normal circumstances.
-If you are in a guardian or basilisk, you should be cap stable with two cap transfers if you have logi 4, and one cap transfer of you have logi 5. The cap chain is set up 2 down even if those who receive cap have logi 5. This insures redundancy in combat situations where the cap chain is often broken when ships are destroyed. You should keep an eye on your watchlist and overview and be ready to change cap transfer targets if necessary.
+If you are in a guardian or basilisk, you should be cap stable with two cap transfers if you have logi 4, and one cap transfer of you have logi 5. The cap chain is set up 2 down even if those who receive cap have logi 5. This insures redundancy in combat situations where the cap chain is often broken when ships are destroyed. You should keep an eye on your watch list and overview and be ready to change cap transfer targets if necessary.
 You should NOT rely on the logi channel list for the cap chain ordering. The logi channel will include non-cap transferring logi, sometimes the FC or other commanders, pilots that have had their ships destroyed, pilots that are off grid, pilots that are in another system, etc.