Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Glyken Touchon
Gallente Independent Alchemists
|
Posted - 2010.10.02 11:55:00 -
[1]
I came up with this idea this morning, and thought I'd throw it out there for comments:
Give cynos a mass limit like WHs. it would: - make cap blobs more awkward - allow an alert defensive hotdrop to gimp the attack directly - give Black Ops a boost in usefullness - open possibilities for mass-bonusing rigs/modules/implants/ships
It would probably require tweaks to the mass & agility of caps/supercaps. The beacon should probably remain for the duration, but unusable with an "expired" tag or something.
I'm sure there are problems that I haven't considered. *Ducks for cover*
|
Dammus
Gallente
|
Posted - 2010.10.02 16:07:00 -
[2]
Seems interesting... But how does this benefit Black Ops?
|
Zverofaust
Gallente Locus Industries
|
Posted - 2010.10.02 16:15:00 -
[3]
Then cap blobs would just use multiple cynos, slightly complicating but otherwise not really affecting their numbers. ___________________________________________ The Hero of Kamela The Terror of Tararan The Executioner of Ezzara |
Glyken Touchon
Gallente Independent Alchemists
|
Posted - 2010.10.02 18:43:00 -
[4]
Originally by: Dammus Seems interesting... But how does this benefit Black Ops?
It may make them more popular for hotdrops- choice of 10 black ops or 1 capital.
Originally by: Zverofaust Then cap blobs would just use multiple cynos, slightly complicating but otherwise not really affecting their numbers.
For rapid deployments, it should be quite a hefty penalty. I didn't want to stop cap fleets, just make them more cumbersome and require more effort.
As I said, this was my first inclination. Adjust as necessary...
|
Nika Dekaia
|
Posted - 2010.10.02 20:53:00 -
[5]
Originally by: Glyken Touchon
Originally by: Zverofaust Then cap blobs would just use multiple cynos, slightly complicating but otherwise not really affecting their numbers.
For rapid deployments, it should be quite a hefty penalty. I didn't want to stop cap fleets, just make them more cumbersome and require more effort.
As I said, this was my first inclination. Adjust as necessary...
I'm all for making the positioning of cap fleets (less jumprange / more fuel use) and regular fleets (more warptime) more of an strategic descission than a tactical. Large allinaces would not be able to claim a few systems and still be able to lay waste smaller entities 30 jumps away with relatively small logistical effort.
But as Zverofaust said, only by having them use a few more alts this won't be achieved. Maybe a mix of the two might work out.
|
Roosterton
Internet Spaceship Raiders
|
Posted - 2010.10.02 21:29:00 -
[6]
Edited by: Roosterton on 02/10/2010 21:31:04 Make different sizes of Cynos. "Small" ones would require the least fitting space and fuel, and would activate instantly, but only a single carrier/dreadnaught/JF can jump in before it collapses, meaning it's mainly a tool for bringing in carrier support, killing a target, and getting your fleet out.
"X-Large" cynos on the other hand, Would be capable of jumping in a titan or a few supercarriers, but would have an activation timer of a minute (or a few) before anything can jump in, and use the most fuel and fitting space. This would stop fleets from dropping Supercarriers on unsuspecting gangs resulting in total overkill, since the gang can see an X-large cyno active and GTFO before anything can jump in, but they would still be useful in large fleet fights which go on for long periods of time.
Of course, there can be cyno sizes in between, such as medium, large, etc. -------- Enemy corps raided into disbandment: Three.
Originally by: Tarminic
OH MY GOD WHAT HAVE YOU DONE?! |
Vadania Amastacia
Caldari Exploit Inc.
|
Posted - 2010.10.03 00:10:00 -
[7]
Originally by: Glyken Touchon I came up with this idea this morning, and thought I'd throw it out there for comments:
Give cynos a mass limit like WHs.
This idea is just plain stupid. A cynosural field generator does just that, generates a special point in space for capital ship jump drive to lock onto. Its not a wormhole of any type; its a BEACON.
|
Abdiel Kavash
Caldari Paladin Order Fidelas Constans
|
Posted - 2010.10.03 00:53:00 -
[8]
Disregarding the RP discrepancy above, I think this is an interesting idea. I have always found it silly that one ship can call in several battlefleets at once. This wouldn't delay normal fleet movements (get a couple of throwaway ships instead of one, or bridge more cynoships to the first) or logistics (one or several JFs or carriers could always jump to one cyno), but it would make people think about deploying large fleets. Either send in several ships and alert the enemy of your presence, or you will delay the deployment by using additional cynos on the ships jumping in.
One of the very few caps/supercaps proposals I like. ___________ EVE is dying! Now for real! |
Glyken Touchon
Gallente Independent Alchemists
|
Posted - 2010.10.05 11:24:00 -
[9]
Originally by: Vadania Amastacia
Originally by: Glyken Touchon I came up with this idea this morning, and thought I'd throw it out there for comments:
Give cynos a mass limit like WHs.
This idea is just plain stupid. A cynosural field generator does just that, generates a special point in space for capital ship jump drive to lock onto. Its not a wormhole of any type; its a BEACON.
Call it "feedback from ships landing on the beacon means that the beacon becomes unlockable" or something. Whatever, that's an RP issue rather than a mechanics one.
I admit that this wouldn't be the silver bullet to Capital blobs, but it's one to think about in conjunction with other ideas.
|
Nuts Nougat
Perkone
|
Posted - 2010.10.05 11:38:00 -
[10]
It doesn't matter anyway. Pop cyno, carriers jump, carriers pop cynos, chain reaction ensues, "capblob" is on your ass 5-10 seconds later than it would be otherwise. ---
|
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |