|
|
| (85 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| | + | '''UniWiki pages I'm currently contributing to (links are to working drafts):<br />''' |
| | | | |
| − | == Mining Doctrine: Wormhole Mining ==
| |
| | | | |
| − | Mining vessels are vulnerable to combat ships, and so AMC miners sometimes hesitate to mine in lower-security space. To be sure, mining barges and exhumers are slow to warp, have less capacitor than other ships, have little room for weapons, and spend most of their time at asteroid and ice belts that potential aggressors can directly warp to. But this doesn't mean that it's unsafe to mine! Unistas '''can''' mine productively under threat, especially in an boosted Shared-Can op. The purpose of this page is to provide a fleet doctrine that provides maximum safety to AMC miners mining in wormhole ore anomalies and [https://community.eveonline.com/news/dev-blogs/thera-and-the-shattered-wormholes/ shattered-wormhole ice belts].
| + | '''UniWiki pages I've recently completed work on, but would appreciate your input on:<br />''' |
| | + | [[Intro to Eve W-Space|Syllabus: Intro to EVE W-Space]]<br /> |
| | + | [[Logistics Guide]]<br /> |
| | + | [[EWAR Guide]]<br /> |
| | + | [[Template:ShipArticle]] |
| | | | |
| − | The doctrine boils down to a few simple rules:
| + | '''Unfinished pages I'm no longer working on:<br />''' |
| − | | + | [[User:Antei thantonne/Shared-Can Mining in Wormhole Space|Shared-Can Mining in Wormhole Space]] |
| − | ===Unistas should mine in Procurers.===
| |
| − | | |
| − | {| class="wikitable" align="center"
| |
| − | ! width="120px" |
| |
| − | ! width="90px" | [[Procurer]]
| |
| − | ! width="90px" | [[Retriever]]
| |
| − | ! width="90px" | [[Covetor]]
| |
| − | ! width="90px" | [[Skiff]]
| |
| − | ! width="90px" | [[Mackinaw]]
| |
| − | ! width="90px" | [[Hulk]]
| |
| − | |-
| |
| − | ! Relative Ore Mining Efficiency*
| |
| − | | 76.4%
| |
| − | | 83.3%
| |
| − | | 100%
| |
| − | | 84.1%
| |
| − | | 91.6%
| |
| − | | 115.0%
| |
| − | |-
| |
| − | ! Relative Ice Mining Efficiency*
| |
| − | | '''84.9%'''
| |
| − | | 83.3%
| |
| − | | 100%
| |
| − | | '''93.4%'''
| |
| − | | 91.6%
| |
| − | | 115.0%
| |
| − | |-
| |
| − | ! Effective Hit Points**
| |
| − | | 60,000
| |
| − | | 14,000
| |
| − | | 11,000
| |
| − | | 67,000
| |
| − | | 30,000
| |
| − | | 23,000
| |
| − | |-
| |
| − | ! Price (isk)***
| |
| − | | 20,000,000
| |
| − | | 27,500,000
| |
| − | | 32,000,000
| |
| − | | 180,000,000
| |
| − | | 200,000,000
| |
| − | | 230,000,000
| |
| − | |-
| |
| − | ! Base Time to Align (s)
| |
| − | | 13.86
| |
| − | | 18.26
| |
| − | | 19.13
| |
| − | | 13.86
| |
| − | | 18.27
| |
| − | | 19.13
| |
| − | |}
| |
| − | | |
| − | ∗ Relative to the Covetor (100%) assuming max skills and optimal fittings for mining. Your results may vary. <br />
| |
| − | ∗∗ EFT calculation, using Tech I modules and intermediate fitting skills as of Kronos patch. Again, your results may vary. <br />
| |
| − | ∗∗∗ Jita/Amarr best price (as of 17 Feb 2015). <br />
| |
| − | <br />
| |
| − | | |
| − | As the table above shows, the Procurer has better tank and time-to-warp than other barges, at a lower hull replacement cost. The Procurer's role bonus for the Ice Harvester is different from its bonus to the Strip Miner, and that actually results in it being a slightly better ice miner than an ore miner. But the overall effect is similar--by mining in a Procurer, you are sacrificing 25-40% of the yield that you would get from a Covetor or Exhumer. Nevertheless, for null-sec ores and ice that are worth over double the value of high-sec ore, WH mining can still be more profitable than high-sec mining.
| |
| − | | |
| − | Procurers can fit a Damage Control unit in a low slot, and shield hardeners in mids, and still have enough room for other mid-slot modules and an Ice Harvesting Upgrade or Mining Laser Upgrade to help with mining. For example:
| |
| − | | |
| − | {{ShipFitting
| |
| − | | ship=Procurer
| |
| − | | shipTypeID=17480
| |
| − | | fitName=Shattered WH Ice Miner
| |
| − | | fitID=WH-Ice-Miner
| |
| − | | low1name=Damage Control I
| |
| − | | low1typeID=2046
| |
| − | | low2name=Ice Harvester Upgrade I
| |
| − | | low2typeID=22576
| |
| − | | mid1name=Medium Shield Extender I
| |
| − | | mid1typeID=3829
| |
| − | | mid2name=Adaptive Invulnerability Field I
| |
| − | | mid2typeID=578
| |
| − | | mid3name=Stasis Webifier I
| |
| − | | mid3typeID=526
| |
| − | | mid4name=Warp Disruptor I
| |
| − | | mid4typeID=3242
| |
| − | | high1name=Ice Harvester I
| |
| − | | high1typeID=16278
| |
| − | | rig1name=Medium Ice Harvester Accelerator I
| |
| − | | rig1typeID=32819
| |
| − | | rig2name=Medium Core Defense Field Extender I
| |
| − | | rig2typeID=31790
| |
| − | | rig3name=open
| |
| − | | rig3typeID=open
| |
| − | | drone1name=Warrior I x5
| |
| − | | drone1typeID=2486
| |
| − | | drone2name=Hornet EC-300 x5
| |
| − | | drone2typeID=23707
| |
| − | | 1name=Mobile Depot
| |
| − | | 1typeID=33474
| |
| − | | charge1name=open
| |
| − | | charge2name=open
| |
| − | | charge3name=open
| |
| − | | charge4name=open
| |
| − | | charge5name=open
| |
| − | | drone3name=open
| |
| − | | drone4name=open
| |
| − | | drone5name=open
| |
| − | | skills=
| |
| − | | showSKILLS=N
| |
| − | | notes=I have fit this with T1, meta 0 modules and drones; upgrade to meta 3/4 or T2 wherever possible, except for the rigs.</li>
| |
| − | <li>EC-300 drones are included to break the target lock on the opponents' initial tackler. If you don't have the skills to fly ECM drones, replace these with salvage and/or light combat drones.</li>
| |
| − | | showNOTES=Y
| |
| − | | difficulty=0
| |
| − | | warsop=A
| |
| − | | warsopReason=
| |
| − | | version=PHOEBE 1.0
| |
| − | | showTOC=Y
| |
| − | | shipDNA=17480:2046;1:22576;1:3829;1:578;1:526;1:3242;1:16278;1:34268;1:32819;1:31790;1:2486;5:23707;5::
| |
| − | | fleetup=
| |
| − | }}
| |
| − | {{ShipFitting
| |
| − | | ship=Procurer
| |
| − | | shipTypeID=17480
| |
| − | | fitName=WH Ore Miner
| |
| − | | fitID=WH-Ore-Miner
| |
| − | | low1name=Damage Control I
| |
| − | | low1typeID=2046
| |
| − | | low2name=Mining Laser Upgrade I
| |
| − | | low2typeID=22542
| |
| − | | mid1name=Medium Shield Extender I
| |
| − | | mid1typeID=3829
| |
| − | | mid2name=Adaptive Invulnerability Field I
| |
| − | | mid2typeID=578
| |
| − | | mid3name=Stasis Webifier I
| |
| − | | mid3typeID=526
| |
| − | | mid4name=Warp Disruptor I
| |
| − | | mid4typeID=3242
| |
| − | | high1name=Strip Miner I
| |
| − | | high1typeID=17482
| |
| − | | rig1name=Medium Core Defense Field Extender I
| |
| − | | rig1typeID=31790
| |
| − | | rig2name=Medium Anti-EM Screen Reinforcer I
| |
| − | | rig2typeID=31718
| |
| − | | drone1name=Warrior I x5
| |
| − | | drone1typeID=2486
| |
| − | | drone2name=Hornet EC-300 x5
| |
| − | | drone2typeID=23707
| |
| − | | rig3name=open
| |
| − | | charge1name=open
| |
| − | | charge2name=open
| |
| − | | charge3name=open
| |
| − | | charge4name=open
| |
| − | | charge5name=open
| |
| − | | drone3name=open
| |
| − | | drone4name=open
| |
| − | | drone5name=open
| |
| − | | skills=
| |
| − | | showSKILLS=N
| |
| − | | notes=Again, upgrade to meta 3/4 or T2 wherever possible, except for the rigs, and please don't fit meta 1-4 Mining Laser Upgrades (too expensive!). Upgrading to Modulated Strip Miner II will require Arkonor or Bistot Processing III to mine null-sec ore; if you don't have one of those skills, stick with the Strip Miner I.</li>
| |
| − | | showNOTES=Y
| |
| − | | difficulty=0
| |
| − | | warsop=A
| |
| − | | warsopReason=
| |
| − | | version=PHOEBE 1.0
| |
| − | | showTOC=Y
| |
| − | | shipDNA=17480:2046;1:22542;1:526;1:3242;1:578;1:3829;1:17482;1:31790;1:31718;1:2486;5:23707;5::
| |
| − | | fleetup=
| |
| − | }}
| |
| − | Some additional notes:
| |
| − | * If the wormhole exit closes, you could end up trapped in the hole. As a result, you will want to carry a Mobile Depot, a Core Probe Launcher I, and 8 Core Scanner Probe I's in your cargo hold, so that you can re-fit in space to scan for a new exit.
| |
| − | * I have left one of the rig slots empty, but this slot should be filled, '''inside the wormhole''', with a Medium Higgs Anchor I rig. The Higgs rig increases the agility of the Procurer, while reducing the ship's velocity. As explained below, this is actually a win-win in terms of mining aligned. However, it does roughly double the ship's mass, which will impact the stability of the entrance wormhole. As a result, I usually recommend that miners use their Mobile Depot to fit the rig after passing through the wormhole, and then to destroy the rig in the fitting window (no Depot required) before they leave.
| |
| − | * This fit has offensive modules (warp disruptor, or "point", and web) in mid slots, for a couple of reasons. The Procurer receives substantial bonuses to drone damage, and that makes the Procurer an effective attacker against frigate and destroyer opponents, as long as you can hold them in place. The fleet booster will be fit with a shield boosting module that will enhance shield resistances; additional resistance mods would be subject to stacking penalties. The FC may ask some miners to replace their points with warp scramblers ("scrams") for tactical flexibility. One or two miners might also fit a Survey Scanner in a mid slot, but having too many of these in the fleet is a waste of offensive potential.
| |
| − | <br /> | |
| − | | |
| − | ===Miners should mine in motion, aligned to pre-made warp-out bookmarks.===
| |
| − | | |
| − | If you mine from a stand-still, as you would in high sec, you will be vulnerable to being scrammed and webbed by aggressors before you can warp away. On the other hand, if your ship is aligned towards a warp-out point, and moving at least 75% of its maximum speed, you can warp out immediately at the first sign of trouble. This means that constructing alignment [[bookmarks]] is an important part of wormhole mining. For ops that Antei FC's, he will supply you with a container of bookmarks at the beginning of the op, including bookmarks for the wormhole entry and exit, and some that are specific to the ice belt or ore anomaly. The bookmarks have a particular naming format, modeled after [http://www.agony-unleashed.com/wiki/index.php?title=Bookmarks Agony Unleashed's format], that looks like this:
| |
| − | | |
| − | | |
| − | [[File:Asteroids.gif]] | |
| − | | |
| − | Examples:
| |
| − | | |
| − | '''.Sie WH->C1 ABC'''<br/>
| |
| − | ''Wormhole, passing from Sierra to a C1 wormhole. In the Probe Scanner window, the signature would have an ID tag that starts with the three-letter code "ABC". A period at the beginning of the bookmark indicates a wormhole that heads away from campus; an asterisk indicates a wormhole that points back to campus.''
| |
| − | | |
| − | '''C1 Ice1'''<br/>
| |
| − | ''Warp-in point in an ice belt. If there is more than one warp-in point, they will be numbered.''
| |
| − | | |
| − | '''C1 Align1'''<br/>
| |
| − | ''Off-grid alignment/warp-out point, >1000 km away from the warp-in point. Miners aligned to this point can warp out immediately.''
| |
| − | | |
| − | '''C1 TAC WHexit @500k'''<br/>
| |
| − | ''Off-axis tactical bookmark, 500 km from the exit wormhole. Miners can warp to this tactical bookmark to check whether the wormhole has been bubbled by an enemy, or to otherwise check the wormhole with D-Scan.''
| |
| − | | |
| − | '''SCOUT P5 @2AU''' ''or''<br/>
| |
| − | '''DEEP SAFE P5 @18AU'''<br/>
| |
| − | ''Un-aligned safe spot. Closest celestial is planet V, 2 (or 18) AU away. Deep safes are always greater than 14.3 AU (maximum D-scan range) away from any celestial.''<br/>
| |
| − | | |
| − | | |
| − | Miners will warp to their assigned warp-in point, and then always "Align To" one of the two opposing warp-out points at at least 75% max velocity. In case of danger, just warp out! In this scheme, miners are only vulnerable while they are reversing direction, switching between the "Align1" and "Align2" alignment bookmark because they have reached the edge of their mining range.
| |
| − | | |
| − | Miners will jet-can ore, just as they do in a high-sec shared-can op, but cans will be immediately tractored by a central Mobile Tractor Unit, where they can be easily scooped by the fleet hauler. Cans are vulnerable to attack in WH space, so they need to be scooped quickly. As a result, don't worry about naming your cans.
| |
| − | | |
| − | ===Mining boosts should be provided by an ordinary battlecruiser.===
| |
| − | | |
| − | Although Orcas are great for boosting AMC mining fleets in high-sec, they are too large to fit into many wormholes without collapsing the hole, and they are too expensive to lose in the risky environment of W-space. Instead, mining boosts can be supplied by an ordinary battecruiser fitted with boosting Link Modules. For example, Antei's alt Paul flies primarily Amarr, and so he boosts with a Prophecy:
| |
| − | | |
| − | {{ShipFitting
| |
| − | | ship=Prophecy
| |
| − | | shipTypeID=16233
| |
| − | | fitName=Paul's WH Booster
| |
| − | | fitID=Paul's-WH-Booster
| |
| − | | low1name=Damage Control II
| |
| − | | low1typeID=2048
| |
| − | | low2name=1600mm Reinforced Rolled Tungsten Plates I
| |
| − | | low2typeID=11325
| |
| − | | low3name=Drone Damage Amplifier II
| |
| − | | low3typeID=4405
| |
| − | | low4name=Energized Adaptive Nano Membrane II
| |
| − | | low4typeID=11269
| |
| − | | low5name=Energized Adaptive Nano Membrane II
| |
| − | | low5typeID=11269
| |
| − | | low6name=Co-Processor II
| |
| − | | low6typeID=3888
| |
| − | | low7name=Co-Processor II
| |
| − | | low7typeID=3888
| |
| − | | mid1name=Experimental 10MN Afterburner I
| |
| − | | mid1typeID=6005
| |
| − | | mid2name=Cap Recharger II
| |
| − | | mid2typeID=2032
| |
| − | | mid3name=Command Processor I
| |
| − | | mid3typeID=11014
| |
| − | | mid4name=Command Processor I
| |
| − | | mid4typeID=11014
| |
| − | | high1name=Mining Foreman Link - Laser Optimization II
| |
| − | | high1typeID=4276
| |
| − | | high2name=Mining Foreman Link - Mining Laser Field Enhancement II | |
| − | | high2typeID=4278
| |
| − | | high3name=Siege Warfare Link - Shield Harmonizing II
| |
| − | | high3typeID=4284
| |
| − | | high4name=Medium 'Vehemence' Shockwave Charge
| |
| − | | high4typeID=9734
| |
| − | | high5name=Core Probe Launcher I, Core Scanner Probe I
| |
| − | | high5typeID=17938
| |
| − | | charge1name=Core Scanner Probe I x1
| |
| − | | charge1typeID=30013
| |
| − | | rig1name=Medium Processor Overclocking Unit I
| |
| − | | rig1typeID=4395
| |
| − | | rig2name=Medium Processor Overclocking Unit I
| |
| − | | rig2typeID=4395
| |
| − | | rig3name=Medium Capacitor Control Circuit I
| |
| − | | rig3typeID=31372
| |
| − | | drone1name=Warrior I x5
| |
| − | | drone1typeID=2486
| |
| − | | drone2name=Hornet EC-300 x5
| |
| − | | drone2typeID=23707
| |
| − | | charge2name=open
| |
| − | | charge3name=open
| |
| − | | charge4name=open
| |
| − | | charge5name=open
| |
| − | | drone3name=open
| |
| − | | drone4name=open
| |
| − | | drone5name=open
| |
| − | | skills=
| |
| − | | showSKILLS=N
| |
| − | | notes=
| |
| − | | showNOTES=N
| |
| − | | difficulty=0
| |
| − | | warsop=A
| |
| − | | warsopReason=
| |
| − | | version=PHOEBE 1.0
| |
| − | | showTOC=Y
| |
| − | | shipDNA=16233:2048;1:11325;1:4405;1:11269;2:3888;2:6005;1:2032;1:11014;2:4276;1:4278;1:4284;1:9734;1:17938;1:30013;1:4395;2:31372;1:2486;5:23707;5::
| |
| − | | fleetup=
| |
| − | }}
| |
| − | | |
| − | I've fit this with the two mining links, a shield resistance link, tanking modules, drones (partly just because the Prophecy is bonused for them), and a smartbomb to counter interdictor bubbles (which can be destroyed by smartbombs). But I'm definitely open to suggestions that don't require any more CPU for different things I might do with this.
| |
| − | | |
| − | Even though the booster is fitted for mining and shield ("siege") support, the boosting pilot will also provide agility and other defensive boosts to fleeted miners according to skill in [[Skills:Leadership#Skirmish_Warfare|Skirmish Warfare]], [[Skills:Leadership#Armored_Warfare|Armored Warfare]] and [[Skills:Leadership#Siege_Warfare|Siege Warfare]].
| |
| − | | |
| − | In our WH mining ops, I have been sitting the booster at the wormhole exiting into high-sec. That way, at the first sign of trouble, the booster pilot can immediately leave the wormhole. Battlecruisers are slow, and so they make for an inviting target. But I might try posting the booster at a safe spot instead.
| |
| − | | |
| − | ===Hauler support should be provided by Miasmos pilots.===
| |
| − | | |
| − | Hauling in wormhole ops can't be provided by a freighter, like we use in high-sec shared-cans; a freighter would just make too inviting a target for wormhole residents. So we use the Miasmos instead:
| |
| − | | |
| − | {{ShipFitting
| |
| − | | ship=Miasmos
| |
| − | | shipTypeID=656
| |
| − | | fitName=WH Cloak-MWD Hauler
| |
| − | | fitID=WH-Cloak-MWD-Hauler
| |
| − | | low1name=Type-D Restrained Nanofiber Structure
| |
| − | | low1typeID=5599
| |
| − | | low2name=Mark I Compact Power Diagnostic System
| |
| − | | low2typeID=8225
| |
| − | | low3name='Stoic' Core Equalizer I
| |
| − | | low3typeID=16301
| |
| − | | low4name='Stoic' Core Equalizer I
| |
| − | | low4typeID=16301
| |
| − | | mid1name=Upgraded EM Ward Amplifier I
| |
| − | | mid1typeID=9580
| |
| − | | mid2name=Upgraded Thermic Dissipation Amplifier I
| |
| − | | mid2typeID=9568
| |
| − | | mid3name=Limited Adaptive Invulnerability Field I
| |
| − | | mid3typeID=9632
| |
| − | | mid4name=50MN Cold-Gas Enduring Microwarpdrive
| |
| − | | mid4typeID=5975
| |
| − | | high1name=Core Probe Launcher I
| |
| − | | high1typeID=17938
| |
| − | | charge1name=Core Scanner Probe I x8
| |
| − | | charge1typeID=30013
| |
| − | | high2name=Improved Cloaking Device II
| |
| − | | high2typeID=11577
| |
| − | | rig1name=Medium Ancillary Current Router I
| |
| − | | rig1typeID=31360
| |
| − | | rig2name=Medium Low Friction Nozzle Joints I
| |
| − | | rig2typeID=31155
| |
| − | | rig3name=Medium Low Friction Nozzle Joints I
| |
| − | | rig3typeID=31155
| |
| − | | charge2name=open
| |
| − | | charge3name=open
| |
| − | | charge4name=open
| |
| − | | charge5name=open
| |
| − | | drone1name=open
| |
| − | | drone2name=open
| |
| − | | drone3name=open
| |
| − | | drone4name=open
| |
| − | | drone5name=open
| |
| − | | skills=
| |
| − | | showSKILLS=N
| |
| − | | notes=The Miasmos has very low HP, and will spend time in space picking up cans. As a result, out of all the ships involved in wormhole mining, the Miasmos is probably most vulnerable. I have fit the ship very cheaply, with the expectation that it might get shot down while harvesting cans. I recommend against using Tech II modules in the Miasmos.
| |
| − | | showNOTES=N
| |
| − | | difficulty=0
| |
| − | | warsop=A
| |
| − | | warsopReason=
| |
| − | | version=PHOEBE 1.0
| |
| − | | showTOC=Y
| |
| − | | shipDNA=656:5599;1:8225;1:16301;2:9580;1:9568;1:9632;1:5975;1:17938;1:30013;1:11577;1:31360;1:31155;2::
| |
| − | | fleetup=
| |
| − | }}
| |
| − | | |
| − | There are a number of ways to fit the Miasmos. In this fit, I've followed three guiding principles:
| |
| − | *The Miasmos should be quick to pilot if aggressed. Shield-tanked ships often have active shield mods in mid- and high-slots. but if you are engaged at a wormhole, you will have a lot to think about very quickly, and activating defensive modules might not be your first priority. So, I've chosen passive shield modules here. (They also conserve capacitor, but you may be dead before you run out of cap anyway.)
| |
| − | *The fit should minimize signature radius as much as possible. Shield-tanked Miasmos fits often include a Medium Shield Extender, but this comes with a sig radius penalty that will make you easier to lock. So I've avoided a shield extender here.
| |
| − | *The Miasmos should be able to cloak at a WH safe spot, and do the [[Cloak_Trick|MWD-cloak trick]] in a pinch.
| |
| − | | |
| − | It is our intent to use the [[AMC Buyback Spreadsheet]] to process reimbursement for ice mining ops.
| |
| − | | |
| − | ===Miners should control only one character, and be prepared to do opponent research on the fly.===
| |
| − | Pilots in low- and null-sec and in wormhole space need to learn a lot more about other pilots flying in their system than high-sec miners typically do. For example, when we see an unfamiliar character in Local, we nearly always:
| |
| − | | |
| − | *Right-click on their name, "Show info", and check their security status, employment history (which gives their character's age) and bio;
| |
| − | *Search for their name on a public killboard like [http://zkillboard.com zKillboard] or [http://eve-kill.net EVE-Kill], to see whether they have a history of aggression against PvE pilots, to try to determine what kinds of ships they fly, and to see whether they are associated with any other pilots in system; and
| |
| − | *Use D-Scan to try and determine what they're flying now.
| |
| − | | |
| − | Even though your Overview is set to tag pilots with negative security status, it is '''not''' safe to assume that pilots with positive security status won't aggress you. Low-sec pirates often repair their security status regularly for exactly this reason—to give you the false impression that they are friendly.
| |
| − | | |
| − | ''A good introductory assignment: Search a public killboard for the low-sec system that the FC has assigned for the op. What sort of ships have been killed there recently, and by whom? How were the ships fitted? The killboard won't give fits for the victors' ships—but can you find the victors' fits among their past losses?''
| |
| | | | |
| | + | <!-- |
| | ==Keeping combat ships in Sierra.== | | ==Keeping combat ships in Sierra.== |
| | There are a variety of reasons why we might engage in combat. If one of our mining vessels is pointed or scrammed by a war target, we might act to save it. I recommend AMC members have a few different ships at their disposal: | | There are a variety of reasons why we might engage in combat. If one of our mining vessels is pointed or scrammed by a war target, we might act to save it. I recommend AMC members have a few different ships at their disposal: |
| Line 549: |
Line 202: |
| | # You can start codebreaking when you are within 5 km, but you must be within 2.5 km to open the can. You might end up Stopping your Ship *while* you are hacking! | | # You can start codebreaking when you are within 5 km, but you must be within 2.5 km to open the can. You might end up Stopping your Ship *while* you are hacking! |
| | # Go to the next one. If there is anyone else in system, I try to keep my Overview set to the PvP tab, and check DScan periodically. | | # Go to the next one. If there is anyone else in system, I try to keep my Overview set to the PvP tab, and check DScan periodically. |
| − | | + | --> |
| − | = '''Mining Overview''' =
| |
| − | {{Mining Links}}
| |
| − | <BR>
| |
