More actions
| Line 287: | Line 287: | ||
''' Organize for cap-chain logistics | '''Organize for cap-chain logistics''' | ||
[[File:LogiChat.jpg|frame|Cap-chain logistics groups are often organized in a chat channel. The current member list is used to figure out who transfers cap to who. In the case of a 1-up, 1-down configuration (very common), John Smallberries both gives and receives cap with the channel members above and below him on the list.]] | [[File:LogiChat.jpg|frame|Cap-chain logistics groups are often organized in a chat channel. The current member list is used to figure out who transfers cap to who. In the case of a 1-up, 1-down configuration (very common), John Smallberries both gives and receives cap with the channel members above and below him on the list.]] | ||
As explained before, cap-chain ships have the advantage of abundant capacitor and they seldom have to worry about having to cycle modules on and off. But cap-chain logistics pilots do have an extra layer of complexity to deal with: maintaining the capacitor chain. There are a few ways to do this, but the most common method is to organize cap-transfer partners in a dedicated logistics chat channel set up by the logi commander. Once you are in this channel, the names above and below yours in the Member List are your transfer partners (assuming a 1-up, 1-down transfer scheme—your FC could choose a different one). Members at the very top and very bottom of the member list are also partnered. The advantage of using a chat channel is that members can drop out of the channel when they are destroyed or otherwise incapacitated, and the remaining, neighboring pilots can adjust by obtaining a new cap-transfer partner from the member list. | As explained before, cap-chain ships have the advantage of abundant capacitor and they seldom have to worry about having to cycle modules on and off. But cap-chain logistics pilots do have an extra layer of complexity to deal with: maintaining the capacitor chain. There are a few ways to do this, but the most common method is to organize cap-transfer partners in a dedicated logistics chat channel set up by the logi commander. Once you are in this channel, the names above and below yours in the Member List are your transfer partners (assuming a 1-up, 1-down transfer scheme—your FC could choose a different one). Members at the very top and very bottom of the member list are also partnered. The advantage of using a chat channel is that members can drop out of the channel when they are destroyed or otherwise incapacitated, and the remaining, neighboring pilots can adjust by obtaining a new cap-transfer partner from the member list. | ||
==Logistics and Crimewatch== | |||
Assuming their safeties are set to the appropriate level, logistics pilots inherit the timers of the pilots they repair, and may receive new ones. If the repaired ship is engaged in combat, the logistics pilot will almost certainly receive PvP, Weapons, and Limited Engagement timers. In addition, if repair occurs in low- or high-security space, and the logistics pilot is not legally allowed to engage all of the repaired ship's combat targets--either due to war or limited engagement--the logistics pilot will become criminal and will be killed by CONCORD, even if neither of the engaged pilots are. As a result, logistics pilots occasionally have to think about how repair affects other, non-aligned pilots in system. Your logistics ship may end up attackable by parties in system that you did not expect including [[Concordokken|CONCORD]]. | |||
it is not recommended to never set logistics piltos safeties to red. | |||
The consequences of repairing a ship with a specific timer: | |||
* Non-Capsuleer Log-Off Timer - Logistic pilot inherits the timer. | |||
* Capsuleer Log-Off Timer - Logistic pilot inherits the timer. | |||
* Weapons Timer - Logistic pilot inherits the timer. | |||
* Suspect Timer - Logistic pilot inherits the timer. Green safeties will prevent activating remote assistance modules. | |||
* Criminal Timer - Logistic pilot inherits the timer and is killed by CONCORD. Green and yellow safeties will prevent activating remote assistance modules. | |||
* Limited Engagement Timer - The consequences depend on relationship between logistics pilot, repaired pilot and the target of the repaired pilot. | |||
** If the logistic pilot and repaired pilot are in same corporation and the engagement timer is with a war target then nothing will happen (other timers will be inherited normally). | |||
** Otherwise if this occurs in high or low security space the logistics pilot receives criminal timer and is killed by CONCORD. Green and yellow safeties will prevent activating remote assistance modules. | |||
[[Category:Fleets]] | [[Category:Fleets]] | ||