Bureaucrats, push, push-admin, push-director, push-manager, push-senior, Administrators
340
edits
Xye Zaloris (talk | contribs) (Blockade Runner (BR)) |
Xye Zaloris (talk | contribs) |
||
(7 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
Asset protection - keeping your hauling ships and cargo alive - is the most important cornerstone of being a successful hauler. Due to our extremely wide range of services, ships, and collaterals, Pushers are expected to be experts in all areas of hauler asset protection. If there is any area you are uncertain about, take the time to consult with a more experienced Pusher. | Asset protection - keeping your hauling ships and cargo alive - is the most important cornerstone of being a successful hauler. Due to our extremely wide range of services, ships, and collaterals, Pushers are expected to be experts in all areas of hauler asset protection. If there is any area you are uncertain about, take the time to consult with a more experienced Pusher. | ||
= '''Risk''' = | |||
Risk is part of EVE Online. No matter what you are doing or where you are there is always some risk in Eve, even if it is very minimal. Risk is an unavoidable component of hauling and one reason why clients turn to PushX for their hauling needs. As such, Pushers are expected to be experts at assessing and handling the risks a contract may include. | |||
== Minimizing Risk == | |||
The most effective way to minimize risk while hauling is to follow the best practices of asset protection and be competent in the essential techniques used by each ship type. Pushers are also encouraged to self-assess when they may be too tired - or otherwise impaired - to haul safely. | |||
== Refusing a Contract Due to Risk == | |||
Hauler safety is PushX's top priority and Pushers will NEVER be penalized for refusing to accept or run a contract due to '''significant''' risk. | |||
*Pushers are expected to consult a PushX Senior, Manager, or Director when they believe a contract is too dangerous for them to complete. | |||
*Pushers are expected to have concrete - not anecdotal - evidence that a contract is dangerous. This can include recent kills on [https://zkillboard.com/ zKillboard], [http://evemaps.dotlan.net Dotlan] statistics, live footage, or in-game scouting. | |||
*Significant risk does not include routine, circumventable risks such as a freighter gank fleet in Uedama. | |||
*Inexperience with a particularly dangerous route is a valid risk; however, Pushers are expected to seek to improve and overcome a lack of experience. | |||
*It is always appropriate to ask a more experienced Pusher for advice. | |||
*Approval to skip a contract applies specifically to that contract at that time. This does not automatically apply to future contracts on the same route. | |||
= '''Basic Asset Protection''' = | = '''Basic Asset Protection''' = | ||
Line 9: | Line 24: | ||
{| class="wikitable" style="text-align: left;" | {| class="wikitable" style="text-align: left;" | ||
|- | |- | ||
| Ship Class || Areas of Service || Primary Defenses || Collateral Limits | | '''Ship Class''' || '''Areas of Service''' || '''Primary Defenses''' || '''Collateral Limits''' | ||
|- | |- | ||
| T1 Industrial || Not Used || N/A || N/A | | T1 Industrial || Not Used || N/A || N/A | ||
Line 36: | Line 51: | ||
=== Triglavian Invasion Content === | === Triglavian Invasion Content === | ||
In the aftermath of the Triglavian Invasion, | In the aftermath of the Triglavian Invasion, pilots need to be aware of the Triglavian and EDENCOM threat to ensure safe passage of their personal assets and PushX Freight. | ||
You need positive EDENCOM standing to safely travel through EDENCOM systems and positive Triglavian standing to safely travel through Triglavian systems. | You need positive EDENCOM standing to safely travel through EDENCOM systems and positive Triglavian standing to safely travel through Triglavian systems. | ||
Line 44: | Line 59: | ||
By default - with no standings - your hauler is considered hostile to Triglavians and neutral to EDENCOM. | By default - with no standings - your hauler is considered hostile to Triglavians and neutral to EDENCOM. | ||
==== Achieving Standing ==== | ==== Achieving Standing ==== | ||
Achieving standings of 0.0 or greater will make EDENCOM neutral towards you. | Achieving standings of 0.0 or '''greater''' will make EDENCOM neutral towards you. | ||
Achieving standings '''greater''' than 0.0 will make Triglavians neutral towards you. | Achieving standings '''greater''' than 0.0 will make Triglavians neutral towards you. | ||
This is the mandatory best practice for PushX haulers. | This is the mandatory best practice for PushX haulers. | ||
*Kill credit on an Edencom ship will give Trig standings and lose Edencom standings. | * '''Do NOT''': Kill credit on an Edencom ship will give Trig standings and lose Edencom standings. | ||
*Kill credit on a Triglavian ship will give Edencom standings and lose Trig standings. | * '''Do NOT''': Kill credit on a Triglavian ship will give Edencom standings and lose Trig standings. | ||
*Kill credit on a Rogue Drone, Sleeper, or Drifter will give both positive Edencom and positive Trig standings. | * '''Do''': Kill credit on a Rogue Drone, Sleeper, or Drifter will give both positive Edencom and positive Trig standings. | ||
The most optimal method, to the best of our knowledge at this time, involves getting kill credit on a Rogue Drone or Drifter in Pochven. The following is one way to cheaply accomplish this: | The most optimal method, to the best of our knowledge at this time, involves getting kill credit on a Rogue Drone, Sleeper, or Drifter in Pochven. The following is one way to cheaply accomplish this: | ||
*Swap to a blank clone (no implants) | |||
*The following fit is very cheap and it is fast enough to kite away and warp off. It has three targeting range scrips so you can paint from 100km+ | |||
[Vigil, Pochven Diver] | [Vigil, Pochven Diver] | ||
Line 90: | Line 93: | ||
Targeting Range Script x3 | Targeting Range Script x3 | ||
*Grab a Pochven Filament (Border/Internal ideally) | |||
*Use the filament to go to Pochven | |||
*Warp at 100km to every warpable object (planet/moon/station/gate/beacon/etc) in the system until you find Drifters, Sleepers, or Rogue Drones, ideally that are actively fighting Trigs or Edencomm | |||
*Use D-Scan to help you find Drifters or Rogue Drones. Ensure that these entities are enabled in your overview settings. | |||
*If you cannot find any Drifters, Sleepers, or Rogue Drones, you can try moving to another system. | |||
*Target a Drifter/Sleeper/Rogue Drone or two and target paint them. This will mark you as having contributed to their death if they die within the next - approximately - twenty minutes. | |||
*Warp off to drop aggro | |||
*You can wait at a bookmark in cloak, or watch them from cloak | |||
*Wait for them to die fighting against Trigs or Edencomm - if they weren't in combat they will warp around every five minutes until they encounter a Trig or Edencomm fleet and start fighting | |||
*You should receive standings for kill participation within twenty minutes of the Rogue Drone/Sleeper/Drifter dying | |||
*You can either use an out (Extraction/Glorification) filament, or you can suicide your pod to get out of Pochven | |||
== '''Universal Best Practices''' == | == '''Universal Best Practices''' == | ||
Line 115: | Line 117: | ||
=== Stay Within Value Limits === | === Stay Within Value Limits === | ||
A hauler’s total cargo value should never exceed the PushX collateral limit for that ship class. Excessive freight value raises your gank profile. | A hauler’s total cargo value should never exceed the PushX collateral or value limit for that ship class. Excessive freight value raises your gank profile. | ||
=== Disable Duel Invitations === | === Disable Duel Invitations === | ||
Line 171: | Line 173: | ||
*The Vigil Fleet Issue is generally the best "rookie" webber to use while training to fly a Rapier. | *The Vigil Fleet Issue is generally the best "rookie" webber to use while training to fly a Rapier. | ||
*Your webber is often also your scout. | *Your webber is often also your scout. | ||
*Do NOT web every warp - this massively raises your gank profile. | |||
=== No Assembled Containers or Double Wraps === | === No Assembled Containers or Double Wraps === | ||
Line 477: | Line 480: | ||
*If you use "Warp to 0" instead of "Jump" to initiate warp, and do not hit "Jump" to queue the gate jump command while in warp, you will have an additional few seconds of post-warp invulnerability in which you can jump to your e-cyno. | *If you use "Warp to 0" instead of "Jump" to initiate warp, and do not hit "Jump" to queue the gate jump command while in warp, you will have an additional few seconds of post-warp invulnerability in which you can jump to your e-cyno. | ||
=== Stop, Align, Warp Method === | === Stop, Align, Warp (S.A.W.) Method === | ||
''This is the correct way to warp a JF to a gate from a station in Low Sec. This is also a safer way to warp a JF in High Sec when you think there is a gank risk.'' | ''This is the correct way to warp a JF to a gate from a station in Low Sec. This is also a safer way to warp a JF in High Sec when you think there is a gank risk.'' | ||
*Immediately upon undocking, press Ctrl+Space to start stopping your JF. This will not break the undock invulnerability. ''(This step is not necessary when initiating a warp from gate cloak).'' | *Immediately upon undocking, press Ctrl+Space to start stopping your JF. This will not break the undock invulnerability. ''(This step is not necessary when initiating a warp from gate cloak).'' | ||
Line 485: | Line 488: | ||
*If you are undocking from a station with a small docking radii, inertial stabilizers and expanded cargohold modules will reduce how far your JF travels while slowing down and aligning. | *If you are undocking from a station with a small docking radii, inertial stabilizers and expanded cargohold modules will reduce how far your JF travels while slowing down and aligning. | ||
*Information on station docking radii can be found here: http://go-dl.eve-files.com/media/1105/Stations_undock_range.pdf | *Information on station docking radii can be found here: http://go-dl.eve-files.com/media/1105/Stations_undock_range.pdf | ||
edits