More actions
mNo edit summary |
|||
| Line 112: | Line 112: | ||
[https://drive.google.com/file/d/19uWP4oSyw5o-sBlL5BeYG9__yripk8jh/view?usp=sharing And here] you can find abundances for all the P0 materials in every planet in the NSC in percents | [https://drive.google.com/file/d/19uWP4oSyw5o-sBlL5BeYG9__yripk8jh/view?usp=sharing And here] you can find abundances for all the P0 materials in every planet in the NSC in percents | ||
There are additional considerations and guidelines pilots should heed when conducting PI in dangerous space. | There are additional considerations and guidelines pilots should heed when conducting PI in dangerous space. | ||
* | ==Maintaining a PI Operation== | ||
* | |||
===General Tips=== | |||
* Join, monitor, and contribute to local intel channels. | |||
* Use [[Directional_scanning|D-scan]]. Even though local chat displays other players in Nullsec, this is still good practice, and it might give some intel on the types of ships entering a system. | |||
* Link [[Killmail|killmails]] in local intel to provide threat intel to other players and support the correct response to the threat. | |||
* Maximizing profit or productivity is a quick way for a player new to PI to burn out and disregard it altogether. Start smaller or simpler, and let interest or need drive an expanded operation. | |||
===On Alts=== | |||
* If a particular activity requires a capsuleer to be in space, then it can probably be conducted while [[Tethering|tethered]] at a friendly [[Upwell_structures|Citadel]]. | |||
* If a friendly Citadel is unavailable for tethering, then the next safest option is to be cloaked in space. | |||
* If conducting PI on an alt character then endeavor for the alt to have positive standings to locals. For NSC members, this means applying for the alt to be on the NSC Pocket Blues list. | |||
===Keeping an Epithal Alive=== | |||
* Shield hardeners are not passive modules. Turn them on, and overheat them if under fire. An Epithal cannot survive for long, but the extra time permits additional threat assessment and potential assistance. | |||
* Before venturing to POCOs to pick up a week's worth of advanced product, confirm via intel channels whether or not there has been any recent activity in the area. | |||
* For station > poco > station, this won't be a problem, but chunky epithal can bump the poco if you make more than one stop and the poco is in the alignment path as warp speed is attained | * For station > poco > station, this won't be a problem, but chunky epithal can bump the poco if you make more than one stop and the poco is in the alignment path as warp speed is attained | ||
* Make sure to actually turn on shield hardeners | * Make sure to actually turn on shield hardeners | ||
| Line 129: | Line 147: | ||
* If operating on a alt, be sure to have the alt join the local standing fleet asap, or apply for the alt to be 'blue' - else you will spook the locals every time they log in | * If operating on a alt, be sure to have the alt join the local standing fleet asap, or apply for the alt to be 'blue' - else you will spook the locals every time they log in | ||
* Expect that sometimes, planned windows for PI activity will be thwarted by local threats. Plan ahead for this by exporting materials early to free space in on-planet storage, building additional storage if possible, or opting for simpler setups that require less time in space. Do not try to squeeze in a POCO run if a roaming gang is afoot. | * Expect that sometimes, planned windows for PI activity will be thwarted by local threats. Plan ahead for this by exporting materials early to free space in on-planet storage, building additional storage if possible, or opting for simpler setups that require less time in space. Do not try to squeeze in a POCO run if a roaming gang is afoot. | ||
* This should go without saying, but | * This should go without saying, but | ||
* Some groups will log out or appear out of a wormhole; be warned | * Some groups will log out or appear out of a wormhole; be warned | ||
* Comms, intel channels, recent kills | * Comms, intel channels, recent kills | ||