After my last post about C5 wormhole escalations, I have a new triage pilot in our C5. My previous partner has a very demanding first life commitment, and while playing, is just after simple pew pew after 70 hour per first life working week
So off to singularity (the testing server) with my new partner. In part to see how he will work out, and in part to see how I will handle the webbing loki component.
We know that we want at least federation navy stasis webifiers, for the increased range. The problem is, how to get them. I don't know of an eve-central service for the test servers. I possibly could point a crest based scraper at one but .. end up finding 6 of them by flying around. Most major trade hubs were sold out. My nullsec region had a few left, with only 3 days remaining. And one of the highsec regions (Sinq Laison I think), had 1. My partner had 2 from some source, so between us we could fit out 2 lokis.
So, the good news is that you can find faction gear on singularity markets for a time at least. The bad news? Those player orders sell out and expire. The best news? Part way through writing this post, singularity was re-mirrored. Be prepared, buy some parts and put them aside for testing. I recommend that you buy what you need rather than buy everything out there. (http://wiki.eveonline.com/wiki/Test_server_rules "Do not make mass market purchases or create oversized stacks of items. ..." ) Also do not expect your items to be available in Jita. Someone else has probably bought them out already. Hunt the secondary markets or source systems.
Finally, if you are more organised, on tranquility (live) have a couple of ships fit with items you might want later. Then on Singularity (test) there is a /copyships command that clones (almost) all your ships from the last mirror and places them into one of the nullsec combat systems. From there you can /moveme to your relevant type of space (trade hubs, different wormholes etc)
After much stuffing around getting fits, off to Singuality's /moveme C5 and then the neighbouring static, where I promptly lose the Moros to sleepers. Sleepless guardians orbit at 35k and scram and web to 40k. Which means my baby boosted Loki, is outwebbed with only 35k . (I can web one or 2 but they are continuously leaving range) Even more annoying is the bear's mistake of not overheating for the additional range. My partner warps in his better skilled loki and webs for me, and I grab a second Moros (we were not entirely disorganised), and all of a sudden the sleepers die a quick death.
The following weekend I have Minmatar Electronics 5 on my Loki pilot and it goes well, no stress, sleepers falling one after the other.
How to get that magic 40k (without overheating)?
Module : Federation Navy Stasis Webifier has a base range of 14km.
Module Loki Electronics - Immobility Drivers with Minimatar electronics system Level 5 increases webbing range to 35k. This is not enough to reliably web the sleepers.
Booster : Unbonused battlecruiser with Skirmish warfare link - Interdiction Maneuvers 1, with Skirmish Warfare Link Specialist 4. This reaches the magic 40k with some room to spare, and now I out-range the sleepers webs and orbit.
Tech 2 links and boosting ships with bonuses (command or strategic cruiser) would be wonderful for another 6k range but ... instead do what you can with what you have (while training for better).
Monday, 23 November 2015
Wednesday, 28 October 2015
Capital Escalations are dead. Long live Capital Escalations.
This post is made from 100% tin foil hats, and has a large dose of speculation.
I have been looking at C5 capital escalations, using Jack Miton's 'Like a Baws' guide. https://forums.eveonline.com/default.aspx?g=posts&t=144954
Jack also has a Carrier + Battleship guide at https://forums.eveonline.com/default.aspx?g=posts&m=1808468#post1808468
I have run some sites on singularity with a corp member on the other side of the world, and really need to get organised to run them on live. Sometimes real life gets in the way, and I am currently the junior partner (skillwise) in the C5 sites.
To run the sites, as I understand it:
If you fail, you will lose your fleet. If your triage Archon disconnects, say good by to billions of ISK. Sleepers remote repair each other, so high applied DPS matters. The tricky point I found in the above method was the second escalation. We want to get the number of sleepers down before the logi runs out of capacitor.
Assuming you want to keep the site alive, salvage this site while the DPS squad does the next site, then 5 pilots in a DPS squad, 3 ignored alts (Boosters and ECM), and a salvager. Lets call it initially 10K DPS for dread #1, ramping up to 23K DPS by the time second dread and carrier land. Including concurrent salvaging, this is moderately comfortable for 3 players with alts.
With the new capitals, there are some changes.
Firstly, it wont be a triage Archon landing, but one of the new Force Auxiliary capitals. As a guess, it will be the Amarr one for increased armor resists.
The next question is what will be the preferred DPS platform vs battleships? I have read that CCP want dreads to be the 'in your face' DPS ship, doing 2-3 times what a battleship does. Different bloggers are suggesting 2k or maybe 3k DPS vs battleships. In comparison, I am reading about (but do not yet fly) 1.5k DPS Vindicators.
However, another ratting carrier pilot I know claims 3k DPS with 13 fighters (and he doesn't have full skills yet). So one of the following will happen. Carriers will remain the preferred anti battleship platform, or dreads will do more than 3k, or carriers will be nerfed.
The siege armor dread won't be able to use an anti-cap gun, but will need to use a battleship gun. Guesses suggest DPS in the 2-3k range, but ... will carriers do more?
Assuming that there will still be capital escalations, and that a force auxiliary escalates the site (neither a forgone conclusion), and that once I get 10K DPS on field with only 2 capitals, I can then smash the site out no problems, I still see something for the new capital escalation site running.
As a rough idea:
I have chosen armor, it is what I am most familiar. Given the setup and not automatically triggering escalations, then maybe shield might also be OK.
I have some experience with what I am talking about, but not enough. There will be holes in the above speculation. Feel free to poke holes in it.
For lesser skilled pilots trying boosting, I sometimes use Gnoboosts. Put whatever useful links that your well skilled booster does not have. It is replacement tanked, and I would much rather lose it than the rest of the fleet.
[Gnosis, Gnobooster]
Co-Processor II
Co-Processor II
Co-Processor II
Co-Processor II
Co-Processor II
Co-Processor II
Command Processor I
Command Processor I
Command Processor I
Command Processor I
Command Processor I
Medium F-S9 Regolith Compact Shield Extender
Skirmish Warfare Link - Evasive Maneuvers I
Information Warfare Link - Sensor Integrity I
Armored Warfare Link - Rapid Repair I
Skirmish Warfare Link - Rapid Deployment I
Armored Warfare Link - Passive Defense I
Armored Warfare Link - Damage Control I
Medium Processor Overclocking Unit I
Medium Processor Overclocking Unit I
Medium Capacitor Control Circuit I
I have been looking at C5 capital escalations, using Jack Miton's 'Like a Baws' guide. https://forums.eveonline.com/default.aspx?g=posts&t=144954
Jack also has a Carrier + Battleship guide at https://forums.eveonline.com/default.aspx?g=posts&m=1808468#post1808468
I have run some sites on singularity with a corp member on the other side of the world, and really need to get organised to run them on live. Sometimes real life gets in the way, and I am currently the junior partner (skillwise) in the C5 sites.
To run the sites, as I understand it:
- Roll open wormholes.
- Set up your booster ships (x2)
- Triage Archon warps in (escalation 1)
- Webbing, target painting Loki warps in, calls targets.
- Siege armor dread warps in (escalation 2), blaps sleeper battleships for roughly 10K DPS, using anti structure guns (hence the need for webbing and target painting). Things get hairy.
- Once most battleships are down, warp in armor dread #2 (escalation 3) (and maybe a second webbing loki). Blap stuff easily.
- Warp in Carrier #2 (escalation 4). Rush to kill something before the dreads do.
- Maybe a ECM boat to keep a trigger alive but harmless. This allows a full site respawn (or so I have read - not confirmed yet).
- Salvage and loot with Noctis and Mobile Tractor Unit, while the DPS wing goes to the next site.
If you fail, you will lose your fleet. If your triage Archon disconnects, say good by to billions of ISK. Sleepers remote repair each other, so high applied DPS matters. The tricky point I found in the above method was the second escalation. We want to get the number of sleepers down before the logi runs out of capacitor.
Assuming you want to keep the site alive, salvage this site while the DPS squad does the next site, then 5 pilots in a DPS squad, 3 ignored alts (Boosters and ECM), and a salvager. Lets call it initially 10K DPS for dread #1, ramping up to 23K DPS by the time second dread and carrier land. Including concurrent salvaging, this is moderately comfortable for 3 players with alts.
With the new capitals, there are some changes.
Firstly, it wont be a triage Archon landing, but one of the new Force Auxiliary capitals. As a guess, it will be the Amarr one for increased armor resists.
The next question is what will be the preferred DPS platform vs battleships? I have read that CCP want dreads to be the 'in your face' DPS ship, doing 2-3 times what a battleship does. Different bloggers are suggesting 2k or maybe 3k DPS vs battleships. In comparison, I am reading about (but do not yet fly) 1.5k DPS Vindicators.
However, another ratting carrier pilot I know claims 3k DPS with 13 fighters (and he doesn't have full skills yet). So one of the following will happen. Carriers will remain the preferred anti battleship platform, or dreads will do more than 3k, or carriers will be nerfed.
The siege armor dread won't be able to use an anti-cap gun, but will need to use a battleship gun. Guesses suggest DPS in the 2-3k range, but ... will carriers do more?
Assuming that there will still be capital escalations, and that a force auxiliary escalates the site (neither a forgone conclusion), and that once I get 10K DPS on field with only 2 capitals, I can then smash the site out no problems, I still see something for the new capital escalation site running.
As a rough idea:
- Roll open wormholes (no change).
- Set up boosters (plural, no change).
- Triage Force Auxillery warps in (little change). Will this escalate?
- Probably the webbing Loki (webbing range still helps)
- 3 Bling battleships to clear most of the first escalation.
- Highest DPS vs battleship of armor carrier (probably Thanatos) or Dread
- Capitals to complete escalations in turn. (possibly by BS pilots swapping to capitals)
- Maybe an ECM to keep the site alive (assuming this still works - I heard that CCP wanted to stop this)
- Salvage and loot with a Noctis and MTU.
I have chosen armor, it is what I am most familiar. Given the setup and not automatically triggering escalations, then maybe shield might also be OK.
I have some experience with what I am talking about, but not enough. There will be holes in the above speculation. Feel free to poke holes in it.
For lesser skilled pilots trying boosting, I sometimes use Gnoboosts. Put whatever useful links that your well skilled booster does not have. It is replacement tanked, and I would much rather lose it than the rest of the fleet.
[Gnosis, Gnobooster]
Co-Processor II
Co-Processor II
Co-Processor II
Co-Processor II
Co-Processor II
Co-Processor II
Command Processor I
Command Processor I
Command Processor I
Command Processor I
Command Processor I
Medium F-S9 Regolith Compact Shield Extender
Skirmish Warfare Link - Evasive Maneuvers I
Information Warfare Link - Sensor Integrity I
Armored Warfare Link - Rapid Repair I
Skirmish Warfare Link - Rapid Deployment I
Armored Warfare Link - Passive Defense I
Armored Warfare Link - Damage Control I
Medium Processor Overclocking Unit I
Medium Processor Overclocking Unit I
Medium Capacitor Control Circuit I
Saturday, 24 October 2015
Citadel and Capital announcements during Eve-Vegas
Some notes from the Eve-Vegas announcements regarding Citadels, Capitals and Supercaps.
There will be dev blogs coming soon.
Citadels
For this document: 'Confirmed' means that I have read it elsewhere before.
All prices are subject to market movements. Based on today's input prices, hulls costs will be :
- Medium Citadel - cost 600M
- Large Citadel - 7B
- Extra Large Citadel - 70B
Rigs will be how you balance between defense and industry.
- Medium Citadel Rigs between 7 and 70m
- Large Citadel Rigs between 90 and 1.1B
- Extra Large Citadel Rigs between 1B and 23B.
Confirmed: You can have an alliance based wormhole market hub.
Confirmed: Citadels will be vulnerable per week 3 hours/6 hours/21 hours per week for the 3 sizes.
Confirmed : Citadels can be blown up by doing DPS, but there is a DPS cap so that they will still take at least 30 minutes on field. (Other places have said that there will be reinforcement timers.)
Confirmed: A destroyed wormhole Citadel has a standard loot fairy.
Confirmed: You will be able to recover the majority of stuff in known space POS, with the exception of components to build the Citadels, and whatever is currently being built.
We will be getting an improved UI for controlling Citadels. (Thank Bob). All anchored structures on overview. UI to say if you have docking rights, access to services. We will be able to share corporation/alliance lists etc. (My take is that blue lists will be easier to maintain).
You will be able to charge the public a fee for docking, but discounts for friends.
You will be able to have player owned tradehubs with lower taxes.
Capital Notes
Dreads are to be the 'in your face' weapons platform.Carriers are to project damage across the battlefield , with a revamped 'fighter squadron' mechanism. Fighters for different roles: Structures, or subcaps or other fighter. No shields/armor/hull per se, more a 'group of small ships that get exploded'. Carriers lose their remote rep role.
New Force Auxiliary capitals to take on the remote repair/triage role.
Damage capitals can be fit to hit subcaps or other capitals/damage structures.
Capital fittings in Meta, Tech2, and faction variations, with new skills to match.
Capitals will all have fleet/ship/refitting services. You will no longer be able to refit mid fight (weapons timer based).
Supercaps will be able to break up large opposing fleets in various new (and some probably over/under powered) ways. I dont fly supercaps so ... less notes from me.
Other notes
A new minigame rewards ISK and sisters loyalty points for 'crowdsourcing' first world protein sequencing.
Sources
https://www.youtube.com/watch?v=w8K9b7CEWOE&feature=youtu.behttps://www.youtube.com/watch?v=bNGQ_Rjhr6g
Thanks to Trinket's Friend for blogging the first link I found.
P.S. http://pastebin.com/A7zvp7Z3 is another set of notes
Tuesday, 13 October 2015
Multiple account launcher in Beta
For those who have not yet seen it, there is a multiple account launcher in beta at https://forums.eveonline.com/default.aspx?g=posts&t=449738&_ga=1.174225634.1175545162.1444213707
Whether you are an alt-a-lot for various forms of industry, or merely someone who loves to set logoff traps on a bazillion pilots, I find this launcher a wonderful improvement.
If you want to play with singularity (the test server), that is also a bonus, and available as a pull down optoin.
There are some caveats, and it is worth reading the known issues/ frequent requests faq on the post.
You will need to re setup your client settings though apparently for those that come later there are plans for an export/import option. As with all plans, a google search for soon (tm) might be illuminating, though I am quietly optimistic.
I also don't entirely understand how to drive the different 'settings' per account, but seem to be working fine.
For anyone with 2 or more accounts, or if you want to play with singularity, I recommend the new launcher.
Whether you are an alt-a-lot for various forms of industry, or merely someone who loves to set logoff traps on a bazillion pilots, I find this launcher a wonderful improvement.
If you want to play with singularity (the test server), that is also a bonus, and available as a pull down optoin.
There are some caveats, and it is worth reading the known issues/ frequent requests faq on the post.
You will need to re setup your client settings though apparently for those that come later there are plans for an export/import option. As with all plans, a google search for soon (tm) might be illuminating, though I am quietly optimistic.
I also don't entirely understand how to drive the different 'settings' per account, but seem to be working fine.
For anyone with 2 or more accounts, or if you want to play with singularity, I recommend the new launcher.
Wednesday, 23 September 2015
Fozzie Sov troll mechanics are a good thing.
Oasa now held by 6 different alliances, with systems changing hands every few days. Cobalt Edge with 5 alliances, and 12 systems changing hands. These are regions I pay attention to.
I know far less about providence, but even Goons recent war there showed the strength of the new system. They burned abandoned systems, and mostly failed in systems where the locals fought. (As a message to the propagandists, a similar burn exercise as before would have been even harder for Providence to re-eject the goons.)
Landlord coalitions are crying over being run ragged with what they perceive as pointless fights, attempting to hold vast but empty regions. Some of them no longer have passive income from renters. Previous renters are adjusting to the new mechanics and forming fleets (some successful, others very much otherwise).
These are very good things. Small groups are taking ownership of their own space, and can bounce back far more easily. Of course in any war game, the bigger, better organsied and funded war machine can roll over the smaller group, but with the new sov, smaller groups have the ability to retake land, or tie up those the larger groups.
I remind those that hark back to the 'good old days': https://www.google.com/search?q=cfc+win+eve
Before new sov, we were asking if the CFC had won eve. The result of a large battle was that new accords were re-written to prevent repeats of these events.
For better or worse, because of the troll mechanics of fozzie sov, and the much maligned troll interceptor; smaller groups are standing up to the previous landlords.
I heartily endorse a small group taking land 'out there', but I still get nervous when it happens too close to home. I want home to be defensible, but I see no reason that buffer space should be held easily. Land is being taken. http://evemaps.dotlan.net/outposts/freeports shows that there are still only 12 systems in freeport. Someone obviously cares enough to hold stations despite all the trolling.
With the latest citadel incarnation, CCP have said that you will again need to apply DPS to the new citadels to capture them http://community.eveonline.com/news/dev-blogs/citadels-sieges-and-you-v2/ "Entosis links are not going to work on new structures". Dreadnoughts were a class of ship designed with structure fights in mind, and that role now officially has a place in new structure fights.
Without an autodefense mechanism, and a cap on total EHP to citadel structures, they will be susceptible to trolling attempts, but not as easily as with entosis links. As a defender, I am not too worried about this as there will be several timers to defend, and customs offices have shown that that while trolling occurs, it is not the end of the world. For me, the bigger loss is no longer treating all unknown Citadels (outside of highsec) as dangerous. And yes our POS have shot as many friendly friendly alts as they have killed hostiles. I like this mechanic, even if I did wish it respected standings granted to individual players as well as standings granted to corporations. I am also fully expecting to be bitten by these statements at some stage in the future.
One thing that is going away with citadels appears to be system wide vulnerability timers. ... "players not belonging to the corporation owning the structure need to be on grid to see [timers]"
At risk of talking about 'when I was young ...' (despite my pilots being younger than many), I actually like the system wide invite of dishonorable third parties to a possibility of a fight.
We are no longer asking if any one entity has won Eve. I don't want to see a return to massive blue donuts where large organizations dictate who can own what space in null and who can fight. There should be room for a certain amount of trolling.
I currently have 2 'hats' in eve, a nullsec trader hat, and the other as a WH PI bear hat. Today's post is wearing my nullsec trader hat.
This post is a record of me saying that, in my opinion, the balkanization of nullsec is a good thing.
I know far less about providence, but even Goons recent war there showed the strength of the new system. They burned abandoned systems, and mostly failed in systems where the locals fought. (As a message to the propagandists, a similar burn exercise as before would have been even harder for Providence to re-eject the goons.)
Landlord coalitions are crying over being run ragged with what they perceive as pointless fights, attempting to hold vast but empty regions. Some of them no longer have passive income from renters. Previous renters are adjusting to the new mechanics and forming fleets (some successful, others very much otherwise).
These are very good things. Small groups are taking ownership of their own space, and can bounce back far more easily. Of course in any war game, the bigger, better organsied and funded war machine can roll over the smaller group, but with the new sov, smaller groups have the ability to retake land, or tie up those the larger groups.
I remind those that hark back to the 'good old days': https://www.google.com/search?q=cfc+win+eve
Before new sov, we were asking if the CFC had won eve. The result of a large battle was that new accords were re-written to prevent repeats of these events.
For better or worse, because of the troll mechanics of fozzie sov, and the much maligned troll interceptor; smaller groups are standing up to the previous landlords.
I heartily endorse a small group taking land 'out there', but I still get nervous when it happens too close to home. I want home to be defensible, but I see no reason that buffer space should be held easily. Land is being taken. http://evemaps.dotlan.net/outposts/freeports shows that there are still only 12 systems in freeport. Someone obviously cares enough to hold stations despite all the trolling.
With the latest citadel incarnation, CCP have said that you will again need to apply DPS to the new citadels to capture them http://community.eveonline.com/news/dev-blogs/citadels-sieges-and-you-v2/ "Entosis links are not going to work on new structures". Dreadnoughts were a class of ship designed with structure fights in mind, and that role now officially has a place in new structure fights.
Without an autodefense mechanism, and a cap on total EHP to citadel structures, they will be susceptible to trolling attempts, but not as easily as with entosis links. As a defender, I am not too worried about this as there will be several timers to defend, and customs offices have shown that that while trolling occurs, it is not the end of the world. For me, the bigger loss is no longer treating all unknown Citadels (outside of highsec) as dangerous. And yes our POS have shot as many friendly friendly alts as they have killed hostiles. I like this mechanic, even if I did wish it respected standings granted to individual players as well as standings granted to corporations. I am also fully expecting to be bitten by these statements at some stage in the future.
One thing that is going away with citadels appears to be system wide vulnerability timers. ... "players not belonging to the corporation owning the structure need to be on grid to see [timers]"
At risk of talking about 'when I was young ...' (despite my pilots being younger than many), I actually like the system wide invite of dishonorable third parties to a possibility of a fight.
We are no longer asking if any one entity has won Eve. I don't want to see a return to massive blue donuts where large organizations dictate who can own what space in null and who can fight. There should be room for a certain amount of trolling.
I currently have 2 'hats' in eve, a nullsec trader hat, and the other as a WH PI bear hat. Today's post is wearing my nullsec trader hat.
This post is a record of me saying that, in my opinion, the balkanization of nullsec is a good thing.
Tuesday, 15 September 2015
Wormhole RR dominix
Several players have been asking me about my RR Dominix fit. I like paired (or more) remote repairing drone boats.
If in doubt, practice first on Singularity ( http://foo-eve.blogspot.com.au/2014/06/eve-beta-client-windows-edition.html )
The following fit's philosophy will apply varying Gallente droneboats, but the Domnix is the one I know best.
[Dominix, DroneMaster]
1600mm Steel Plates II
Armor Explosive Hardener II
Drone Damage Amplifier II
Drone Damage Amplifier II
Energized Adaptive Nano Membrane II
Energized Adaptive Nano Membrane II
Damage Control II
Phased Weapon Navigation Array Generation Extron
Omnidirectional Tracking Link II
Large Micro Jump Drive
Sensor Booster II
Cap Recharger II
Large Remote Capacitor Transmitter II
Large Remote Capacitor Transmitter II
Drone Link Augmentor II
Drone Link Augmentor II
Large Remote Armor Repairer II
Large Remote Armor Repairer II
Large Egress Port Maximizer I
Large Egress Port Maximizer I
Large Sentry Damage Augmentor I
Vespa EC-600 x5
Garde II x4
Hornet EC-300 x5
Bouncer II x5
Salvage Drone I x5
Hobgoblin II x10
Optimal Range Script x2
Tracking Speed Script x2
Targeting Range Script x1
Scan Resolution Script x1
[Dominix, DroneSlave]
1600mm Steel Plates II
Armor Explosive Hardener II
Drone Damage Amplifier II
Drone Damage Amplifier II
Energized Adaptive Nano Membrane II
Energized Adaptive Nano Membrane II
Damage Control II
Omnidirectional Tracking Link I
Omnidirectional Tracking Link II
Large Micro Jump Drive
Sensor Booster II
Cap Recharger II
Large Remote Capacitor Transmitter II
Large Remote Capacitor Transmitter II
Drone Link Augmentor II
Drone Link Augmentor II
Large Remote Armor Repairer II
Large Remote Armor Repairer II
Large Egress Port Maximizer I
Large Egress Port Maximizer I
Large Sentry Damage Augmentor I
Hobgoblin II x10
Vespa EC-600 x5
Hornet EC-300 x5
Garde II x4
Bouncer II x5
Salvage Drone I x5
Optimal Range Script x2
Tracking Speed Script x2
Targeting Range Script x1
Scan Resolution Script x1
Have a 2% cpu implant for this one. The MJD is the GTFO option. Or swap out the MJD for something useful, possibly another sensor booster (or target painter on the master). If you do so you can upgrade the tracking link.
By all means fit meta 4 instead of tech 2, but don't bother with these ships unless you have capacitor emissions 4.
Match the cap emission modules. If one of a pair (or trio) is using meta 4, then all in that set use meta 4.
Flying notes:
Capacitor Emission Systems 4 is mandatory, 5 is strongly recommend.
Warp both Dominix to site, at range.
Launch drones, move, something to to break local invulnerability.
Target each other and apply both capacitor transmitters and one armor repairer. Apply second armor repairer as necessary.
Slave assigns drones to master.
Master uses target painter to 'shoot' slaves drones, applies own drones normally.
Master is responsible for main DPS.
Slave can as necessary swap out sentries for light drones to clean up frigates, then swap back to sentries (or heavies)
The primary difference between master and slave is the target painter.
MASTER SHOULD DO NOT APPLY TARGET PAINTER TO PAIRED SHIP. IT WILL HURT. So says bitter experience. If it does happen, then make very sure to reapply drones to new targets as soon as possible by reapplying target painter to something else. Generally this occurs because your fleet member needs extra reps and is already in armor. Then their armor dips into structure. If you have a non-drone boat not participating in remote exchanges, it would be better to assign all drones to that boat.
While you should not get out of range of your pair, you should not be stationary either. Orbit something - your paired fleet member, a sentry drone, or maybe even a jet-canned <anything>.
This setup works well for multiboxing. It scales well too.
For the remote capacitor exchanges, in a larger squad, you can apply the remote capacitor to 1 up 1 down. This will help even out any neuting. Alternatively, minimise the damage caused by insufficient skills by organising ships in pairs or trios (so any difficulty with cap exchange is minimised to a few ships.)
Sleepers are damage agnostic, so match your drones to range. When the hostile resists are known, consider that when selecting drones.
The reason for the cap exchange rigs instead of remote armor rep rigs is that you are cap exchanging 100% of the time, but only repairing as needed.
We ran 4 of these in our C4 when we had it, and only ever had problems when I was 'helping' friends ... by applying the target painter on them. Doing so causes excitement on voice coms.
If you have sufficient points already on field, this also makes a reasonable defensive fleet.
I am not an inspired Pyfa warrior, but this fleet worked for us. Old pilots that want to provide alternative fits (or links to such fits) are welcome to do so.
If in doubt, practice first on Singularity ( http://foo-eve.blogspot.com.au/2014/06/eve-beta-client-windows-edition.html )
The following fit's philosophy will apply varying Gallente droneboats, but the Domnix is the one I know best.
[Dominix, DroneMaster]
1600mm Steel Plates II
Armor Explosive Hardener II
Drone Damage Amplifier II
Drone Damage Amplifier II
Energized Adaptive Nano Membrane II
Energized Adaptive Nano Membrane II
Damage Control II
Phased Weapon Navigation Array Generation Extron
Omnidirectional Tracking Link II
Large Micro Jump Drive
Sensor Booster II
Cap Recharger II
Large Remote Capacitor Transmitter II
Large Remote Capacitor Transmitter II
Drone Link Augmentor II
Drone Link Augmentor II
Large Remote Armor Repairer II
Large Remote Armor Repairer II
Large Egress Port Maximizer I
Large Egress Port Maximizer I
Large Sentry Damage Augmentor I
Vespa EC-600 x5
Garde II x4
Hornet EC-300 x5
Bouncer II x5
Salvage Drone I x5
Hobgoblin II x10
Optimal Range Script x2
Tracking Speed Script x2
Targeting Range Script x1
Scan Resolution Script x1
[Dominix, DroneSlave]
1600mm Steel Plates II
Armor Explosive Hardener II
Drone Damage Amplifier II
Drone Damage Amplifier II
Energized Adaptive Nano Membrane II
Energized Adaptive Nano Membrane II
Damage Control II
Omnidirectional Tracking Link I
Omnidirectional Tracking Link II
Large Micro Jump Drive
Sensor Booster II
Cap Recharger II
Large Remote Capacitor Transmitter II
Large Remote Capacitor Transmitter II
Drone Link Augmentor II
Drone Link Augmentor II
Large Remote Armor Repairer II
Large Remote Armor Repairer II
Large Egress Port Maximizer I
Large Egress Port Maximizer I
Large Sentry Damage Augmentor I
Hobgoblin II x10
Vespa EC-600 x5
Hornet EC-300 x5
Garde II x4
Bouncer II x5
Salvage Drone I x5
Optimal Range Script x2
Tracking Speed Script x2
Targeting Range Script x1
Scan Resolution Script x1
Have a 2% cpu implant for this one. The MJD is the GTFO option. Or swap out the MJD for something useful, possibly another sensor booster (or target painter on the master). If you do so you can upgrade the tracking link.
By all means fit meta 4 instead of tech 2, but don't bother with these ships unless you have capacitor emissions 4.
Match the cap emission modules. If one of a pair (or trio) is using meta 4, then all in that set use meta 4.
Flying notes:
Capacitor Emission Systems 4 is mandatory, 5 is strongly recommend.
Warp both Dominix to site, at range.
Launch drones, move, something to to break local invulnerability.
Target each other and apply both capacitor transmitters and one armor repairer. Apply second armor repairer as necessary.
Slave assigns drones to master.
Master uses target painter to 'shoot' slaves drones, applies own drones normally.
Master is responsible for main DPS.
Slave can as necessary swap out sentries for light drones to clean up frigates, then swap back to sentries (or heavies)
The primary difference between master and slave is the target painter.
MASTER SHOULD DO NOT APPLY TARGET PAINTER TO PAIRED SHIP. IT WILL HURT. So says bitter experience. If it does happen, then make very sure to reapply drones to new targets as soon as possible by reapplying target painter to something else. Generally this occurs because your fleet member needs extra reps and is already in armor. Then their armor dips into structure. If you have a non-drone boat not participating in remote exchanges, it would be better to assign all drones to that boat.
While you should not get out of range of your pair, you should not be stationary either. Orbit something - your paired fleet member, a sentry drone, or maybe even a jet-canned <anything>.
This setup works well for multiboxing. It scales well too.
For the remote capacitor exchanges, in a larger squad, you can apply the remote capacitor to 1 up 1 down. This will help even out any neuting. Alternatively, minimise the damage caused by insufficient skills by organising ships in pairs or trios (so any difficulty with cap exchange is minimised to a few ships.)
Sleepers are damage agnostic, so match your drones to range. When the hostile resists are known, consider that when selecting drones.
The reason for the cap exchange rigs instead of remote armor rep rigs is that you are cap exchanging 100% of the time, but only repairing as needed.
We ran 4 of these in our C4 when we had it, and only ever had problems when I was 'helping' friends ... by applying the target painter on them. Doing so causes excitement on voice coms.
If you have sufficient points already on field, this also makes a reasonable defensive fleet.
I am not an inspired Pyfa warrior, but this fleet worked for us. Old pilots that want to provide alternative fits (or links to such fits) are welcome to do so.
Saturday, 5 September 2015
Shared Blog Collections
Shared blog collections now at
I have been using the free services of feedly since the demise of google reader, and I love that it does not matter what device I am reading EVE news on, but that I get to see every article once and only once.
What I did find a nuisance was that I could not easily share my collection. I have tried with my own efforts and have supported the efforts of others (see the consolidated Eve blogrolls list on the right hand side of my blog), but none of this has been as easy as just adding a new blog to Feedly.
Well, now Feedly have a service that I forked out cash for. Feedly Shared Collections
The good news is that these are easily shared, so that if any other blogger puts up a shared collection, I can copy their collections into my feedly and vice versa. If any 'curator' disappears (as happened with an earlier eve blog bundle), then it will be easy for someone else to pick up the pieces.
- http://feedly.com/FooEveCollection : My master sharing list
- http://feedly.com/FooEveCollection/Eve%20Online : player blogs
- http://feedly.com/FooMusings/Eve%20Online%20Official : Official Eve feeds
- http://feedly.com/FooEveCollection/EveNewsSites : Eve news sites
I have been using the free services of feedly since the demise of google reader, and I love that it does not matter what device I am reading EVE news on, but that I get to see every article once and only once.
What I did find a nuisance was that I could not easily share my collection. I have tried with my own efforts and have supported the efforts of others (see the consolidated Eve blogrolls list on the right hand side of my blog), but none of this has been as easy as just adding a new blog to Feedly.
Well, now Feedly have a service that I forked out cash for. Feedly Shared Collections
The good news is that these are easily shared, so that if any other blogger puts up a shared collection, I can copy their collections into my feedly and vice versa. If any 'curator' disappears (as happened with an earlier eve blog bundle), then it will be easy for someone else to pick up the pieces.
Subscribe to:
Posts (Atom)