(06-18-2013, 01:31 PM)Anaximander Wrote: To be clear, I don't mind botsharing between caps or between snubs exclusively; but it's freaking annoying when you duel someone in a fighter and he has two dreadnoughts feed him. You'll never stand a chance at winning unless you have means to instakill him; it rather becomes a matter of how many b/b you can drain before you go out. It's boring.

If Caps just got that much more armor (e.g. turtle's 2000 bots + 2000 bats = 800,000 added hull or something scaled properly to the Cap armor multiplier), couldn't it solve it?

(06-18-2013, 01:34 PM)Hasteric Wrote: This. Why exactly would this add so much workload for the devs? I don't see any "unforseen consequences" (those tend to be hard to see, though) of upping armor and doing away with B/B for caps. Unlike snubs, they don't tend to get insta'd.

(06-19-2013, 05:30 AM)Knjaz Wrote:

(06-18-2013, 01:31 PM)Anaximander Wrote: To be clear, I don't mind botsharing between caps or between snubs exclusively; but it's freaking annoying when you duel someone in a fighter and he has two dreadnoughts feed him. You'll never stand a chance at winning unless you have means to instakill him; it rather becomes a matter of how many b/b you can drain before you go out. It's boring.

If Caps just got that much more armor (e.g. turtle's 2000 bots + 2000 bats = 800,000 added hull or something scaled properly to the Cap armor multiplier), couldn't it solve it?

I was taking about battleships full of nanobots. It takes that much time for the first focused battleship to die.
Such approach would solve fighter balance problems, though. But would make Docking Bays so much more powerful.

I do remember a fight, that happened relatively recently, when during few minutes of combat our focused RMBS chewed through nanobots of the whole fleet, including repair ship ones. Something around 10000 bots in total (his own 2000, my 2000, Repship's 4000, and 2-3 cruisers - and I dont remember if we had another battleship on the field, than it's 11-12k ), or more - and was half-dead at the end. That required some good cooperation, though. (edit: actually, I think we did have a carrier, and I'm not sure if it was one or two. So it was over 12k nanos in a medium-scale fleet fight, during few mins)

You just won't fix that by turning bots into armor, since first focused fighter can easily survive for minutes (you know I dont fly them, but I think it's accurate estimate?), for the first focused battleship - it's seconds.
So please, do not remove bots from caps, they're kinda essential for fleet warfare.

(06-18-2013, 01:34 PM)Hasteric Wrote: This. Why exactly would this add so much workload for the devs? I don't see any "unforseen consequences" (those tend to be hard to see, though) of upping armor and doing away with B/B for caps. Unlike snubs, they don't tend to get insta'd.

It's quite the other way around. Go participate in cap combat with 5-6 battleships on both sides. You'll see how long the first one lives.

With 6 full cerb LiDreads, first focused Cau8 Full Bots RMBS goes down in 8.2 seconds, if you dont count in shield and batteries (but include those 2.000 nanobots). Just do the math. Shields will add another 2 seconds, I suppose. I've used estimate of 15 seconds for large scale combat because, well, not always you meet a full-cerb fleet, and usually people aren't cooperating that well, so it takes several seconds for them to locate and focus at single target.

LiDreads, medium battleships, would be capable to keep that rate of DPS for ~18 seconds. After that it goes to DpE*regen.

(06-18-2013, 01:34 PM)Hasteric Wrote:

(06-18-2013, 01:31 PM)Anaximander Wrote: If Caps just got that much more armor (e.g. turtle's 2000 bots + 2000 bats = 800,000 added hull or something scaled properly to the Cap armor multiplier), couldn't it solve it?

This. Why exactly would this add so much workload for the devs? I don't see any "unforseen consequences" (those tend to be hard to see, though) of upping armor and doing away with B/B for caps. Unlike snubs, they don't tend to get insta'd.