These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Player Features and Ideas Discussion

 
  • Topic is locked indefinitely.
 

[Proteus - January] Recon ships

First post First post First post
Author
Dark Drifter
Sons of Seyllin
Pirate Lords of War
#2081 - 2014-12-30 17:06:16 UTC
what id the D-scan imunity was a 'skill related bonus.

say 2.8AU reduction to D-scan Visability per RECON level

this leaves tyou with a .3au window of opertunity to see your
agressor/impending death on D scan if they have recon ships to 5
Aureus Ahishatsu
Deadspace Knights
#2082 - 2014-12-30 17:52:12 UTC  |  Edited by: Aureus Ahishatsu
CCP Rise wrote:

  • Align Recons around ship developer trends established in other classes (Roden Lachesis should not use missiles for example)



  • I know this isn't the most discussed topic but this seems like a rather harsh inconvenience for the Caldari/ Minmatar. The Gallente/ Amarr don't need to worry about really cross training anything. However now Minmatar recon pilots will be REQUIRED to train missiles to fly the cloaked ship. While the Lore concept works for the command ship, it seems rather hampering for the recons. Particularly since a lot of scouts are alts who are not training. All those alts will now be required to train missiles if they even want to have any defense on the rapier. I would personally recommend taking one of two approaches to fix the problem.

    A) Make Caldari/ Minmatar ships like the Fleet Scythe in that they all have dual weapon bonuses
    B) Go the same route you already went with Command ships by making both viable. Ex. all recons can equip cloak, at the expense of a high slot.

    edit: by going the second route you would also be able to eliminate the silly d-scan invisibility as both ships can warp/sit cloaked at that point
    Aureus Ahishatsu
    Deadspace Knights
    #2083 - 2014-12-30 18:14:25 UTC
    Niskin wrote:
    Aureus Ahishatsu wrote:

    I don't understand what you are talking about here. Most of the people who have raised concerns have had very definitive points they were making about situations that are very real (wh's, fw). Meanwhile the only argument being made against it is 'mm tears" and 'nom nom nom gonna love killing bears now' neither of which contributes anything. The Faction Warfare concern is very legitimate in that it doesn't even favor those who are playing the game for faction warfare. In fact it benefits those who simply wish to be a nuisance to those participating in faction warfare.


    Yeah, that's what we did in here, ignored all the posts about real situations. I mean I certainly didn't explain how T3 cruisers were still more likely to get a kill on you. Nor did I include some tips to avoid recon ganks in that same post. Later on I didn't help a guy out who didn't understand his defensive options properly. Then I certainly didn't recap the first 52 pages and address the concerns about FacWar plexes. Nor did I present a comparison of being ganked in a wormhole by a combat recon versus a T3 cruiser.

    That's just me, and I'm not the only one arguing in good faith in this thread. There have been some good situations brought up, and all have counters, but not everybody is happy with having to use counters where they didn't have to before. I can understand that, but this is EVE, things will change and sometimes they will get harder.


    Sorry for the long response but holidays and all....
    Niskin you listed helping an individual with a single instance as a counter. That's just an individual not knowing one aspect of gameplay (combat probes while scanning), not countering an entire play style (fleet recon viability). Second all of you're arguments are about how much more dangerous the T3's are. Ok? so what? this article isn't even about the T3's other than one line mentioning how they are making the recons closer to them. A fitted recon isn't even half the cost of a T3 with subsystems. Not to mention for wealthy PVP'ers they will happily throw d-scan immune recons at people over t3's simply for the skill loss avoidance. Your entire argument base is that it's ok to make the recons deadlier because other things are worse. To put it bluntly I'll quote my friend who read your article. it's like you are saying "don't worry about the piranhas in the water, because there are alligators nearby."
    Niskin
    The Dead Parrot Shoppe Inc.
    The Chicken Coop
    #2084 - 2014-12-30 18:48:04 UTC
    Aureus Ahishatsu wrote:
    Sorry for the long response but holidays and all....
    Niskin you listed helping an individual with a single instance as a counter. That's just an individual not knowing one aspect of gameplay (combat probes while scanning), not countering an entire play style (fleet recon viability).


    The guy thought he couldn't hack a can and scan with combat probes at the same time. I pointed out that he could, and now he'll be safer for it. My point is that not everybody arguing in this thread knows how every mechanic works, including myself. If I see a place where somebody would benefit from knowledge then I give it to them, just the same as I read others posts to gather info I didn't have.

    Aureus Ahishatsu wrote:
    Second all of you're arguments are about how much more dangerous the T3's are. Ok? so what? this article isn't even about the T3's other than one line mentioning how they are making the recons closer to them. A fitted recon isn't even half the cost of a T3 with subsystems. Not to mention for wealthy PVP'ers they will happily throw d-scan immune recons at people over t3's simply for the skill loss avoidance. Your entire argument base is that it's ok to make the recons deadlier because other things are worse. To put it bluntly I'll quote my friend who read your article. it's like you are saying "don't worry about the piranhas in the water, because there are alligators nearby."


    T3's exist now and with similar fits they cost 2-3x as much as Recons. You don't have to faction fit a T3 to pull off a cloaky gank. They are also quite prevalent, there are people flying T3's for PvP in every area of the game. People keep saying that "this makes blah blah blah more dangerous" and I'm pointing out that it doesn't. It gives those who would attack you some additional options, but they already have some good options as it is.

    It would be more accurate to say that I am saying "Be careful, there are both piranhas and alligators in this water." But more realistically the number of assailants is going to stay about the same, you just don't know if they will show up in a piranha suit or an alligator suit... and really, does it matter? You're gonna get eaten either way if you aren't careful.

    It's Dark In Here - The Lonely Wormhole Blog

    Remember kiddies: the best ship in Eve is Friendship.

    -MooMooDachshundCow

    Mario Putzo
    #2085 - 2014-12-30 18:50:39 UTC  |  Edited by: Mario Putzo
    baltec1 wrote:
    Its interesting to see so many getting worked up over the Dscan trick when its effectively the same as any ship with a cov ops cloak, the only difference is the rook can be probed down.


    Probably because it is a needless change, and a needless addition to the game. If its no different why not just slap a cov ops cloak on the combat recons?

    When you have to start rescinding changes before they even go live than its probably not worth the adjustment.

    Increasing resist profiles on Combat Recons was a good idea, it would let them be more apt in performing their intended function...combat. Now that this is not going to happen the DSCAN change seems rather redundant, to the point it seems like CCP is just shoehorning a change for change sake.

    Like I said earlier, the change is ****, it offers nothing new to the game, and doesn't actually solve the issue with Combat Recons being utter **** in combat situations. Like I said above. The best fix is to split the recon roles instead of having the mashup we currently have. Combat Recons should be functional in a Combat Role, Force Recons should be more suited for a support role (force multiplier).

    Anything other than defining the ships into 2 distinct role ideologies is just a placebo.

    Like you said, its no different than having a Cov Ops cloak...so why do we need to add it to the game at all...especially at the cost of something a ship line desperately needs.
    Stitch Kaneland
    The Tuskers
    The Tuskers Co.
    #2086 - 2014-12-30 19:39:28 UTC
    Force recons lose ability to cloak, but gain dscan immunity, combat recons get HAC resists and bigger EHP pool. I mean whats the point of one being able to cloak and the other having a semi-cloak, but neither are good in a fleet role.

    Id be happy to jump a gate in null with the lone sabre with falcon alt, and actually see the risk averse ******* before trying to engage. may not show up on dscan, but at least i know a falcon is there on gate when i jump in.

    Just a thought.
    Rowells
    Blackwater USA Inc.
    Pandemic Horde
    #2087 - 2014-12-30 21:19:04 UTC
    since we rolled back on some of the other changes, can we consider the probe fitting bonus for combat recons?
    Catherine Laartii
    Doomheim
    #2088 - 2014-12-30 22:09:00 UTC
    Barrogh Habalu wrote:
    Spugg Galdon wrote:
    Looking forward to setting up some traps in low sec with combat recons.

    3 of you in local. Put 3 cheap mining barges in the belt/ice field.

    Get into your CR's and sit and wait for them to warp to what looks like a mining fleet.

    Get two buddies with you so the number of ships on dscan equals amount of people in local.


    Or better yet, if oyu live out there just ditch the ships in the belt and get into the CR's. You'd be amazed at how many people take that bait since it's EXACTLY what it looks like to them.
    Jenshae Chiroptera
    #2089 - 2014-12-30 22:51:36 UTC
    Jaysen Larrisen wrote:
    East Windstar wrote:
    Jenshae Chiroptera wrote:


    Nope.

    Check local. - See 10.
    D-scan - see 5.
    Assume 5 are Recons.
    Avoid fight.


    You won't see 5 on D-scan, they will not be on D-scan at all.

    Looks like you have never used the D-scan.


    I think Jenshae was saying that if you see 10 people in local and only 5 ships on scan just assume the delta equals recon ships to be safe.

    Yup.
    CALAMYTY DIVA wrote:
    What about WH?


    Just blobs invading temporarily. I won't try live in them again. Did a year before frigate holes.

    CCP - Building ant hills and magnifying glasses for fat kids

    Not even once

    EVE is becoming shallow and puerile; it will satisfy neither the veteran nor the "WoW" type crowd in the transition.

    Orange Faeces
    Farbissina Industrial and Procurement
    #2090 - 2014-12-31 03:00:03 UTC  |  Edited by: Orange Faeces
    Mario Putzo wrote:
    baltec1 wrote:
    Its interesting to see so many getting worked up over the Dscan trick when its effectively the same as any ship with a cov ops cloak, the only difference is the rook can be probed down.

    ...
    Increasing resist profiles on Combat Recons was a good idea, it would let them be more apt in performing their intended function...combat. Now that this is not going to happen the DSCAN change seems rather redundant, to the point it seems like CCP is just shoehorning a change for change sake.

    Like I said earlier, the change is ****, it offers nothing new to the game, and doesn't actually solve the issue with Combat Recons being utter **** in combat situations. Like I said above. The best fix is to split the recon roles instead of having the mashup we currently have. Combat Recons should be functional in a Combat Role, Force Recons should be more suited for a support role (force multiplier).

    Anything other than defining the ships into 2 distinct role ideologies is just a placebo.

    Like you said, its no different than having a Cov Ops cloak...so why do we need to add it to the game at all...especially at the cost of something a ship line desperately needs.

    Saying the d-scan immunity doesn't offer something new to the game is just false. It is introducing a "cloak" that:

    • you can't go AFK without the risk of getting popped. (Eliminating deep-safes was another change that helped in this direction.)
    • you can't use for tower warp-ins or on-grid intel.
    • you can't use for fleet warp-ins because you'll get popped
    • you can't use for cov-ops cyno activities (because the force recon is balanced for this with lower DPS).
    • does make some ganks easier, but after five years of continuous nerfs to this play-style I think we're in safe territory.
    • you don't have to remember to turn it on. BFD. (edit) Granted, CCP does have to figure out how ot balance this for people logging with aggression.


    As for the fleet viability, I thought about this a bit more. In CCP Rise's statement, he didn't say that he would go back to the existing resist profile. He may make the resist profile such that addition of hardeners would make it viable for fleet at the expense of some EWAR functionality; Or, he can tune it so that it would be viable in a typical null-sec fleet but only with the addition of a slightly higher mix of logistics. It may still be viable for fleet action. We just don't know until he comes back from vacation. Its not an either-or.

    So, I say, keep your pants on until the changes are clarified. I'm hopeful that a creative change like the d-scan immunity can be balanced with other play styles.


    O. Faeces
    Mario Putzo
    #2091 - 2014-12-31 03:29:04 UTC  |  Edited by: Mario Putzo
    Orange Faeces wrote:
    Mario Putzo wrote:
    baltec1 wrote:
    Its interesting to see so many getting worked up over the Dscan trick when its effectively the same as any ship with a cov ops cloak, the only difference is the rook can be probed down.

    ...
    Increasing resist profiles on Combat Recons was a good idea, it would let them be more apt in performing their intended function...combat. Now that this is not going to happen the DSCAN change seems rather redundant, to the point it seems like CCP is just shoehorning a change for change sake.

    Like I said earlier, the change is ****, it offers nothing new to the game, and doesn't actually solve the issue with Combat Recons being utter **** in combat situations. Like I said above. The best fix is to split the recon roles instead of having the mashup we currently have. Combat Recons should be functional in a Combat Role, Force Recons should be more suited for a support role (force multiplier).

    Anything other than defining the ships into 2 distinct role ideologies is just a placebo.

    Like you said, its no different than having a Cov Ops cloak...so why do we need to add it to the game at all...especially at the cost of something a ship line desperately needs.

    Saying the d-scan immunity doesn't offer something new to the game is just false. It is introducing a "cloak" that:

    • you can't go AFK without the risk of getting popped. (Eliminating deep-safes was another change that helped in this direction.)
    • you can't use for tower warp-ins or on-grid intel.
    • you can't use for fleet warp-ins because you'll get popped
    • you can't use for cov-ops cyno activities (because the force recon is balanced for this with lower DPS).
    • does make some ganks easier, but after five years of continuous nerfs to this play-style I think we're in safe territory.


    As for the fleet viability, I thought about this a bit more. In CCP Rise's statement, he didn't say that he would go back to the existing resist profile. He may make the resist profile such that addition of hardeners would make it viable for fleet at the expense of some EWAR functionality; Or, he can tune it so that it would be viable in a typical null-sec fleet but only with the addition of a slightly higher mix of logistics. It may still be viable for fleet action. We just don't know until he comes back from vacation. Its not an either-or.

    So, I say, keep your pants on until the changes are clarified. I'm hopeful that a creative change like the d-scan immunity can be balanced with other play styles.


    O. Faeces


    Doesn't stop people fitting a cloak to their ship like they did before and going afk, decloak to warp don't show on dscan...
    Why not just give it cov ops cloak? Its the same damn thing.

    Couldn't use it for reliable warp ins or on grid intel before.
    No Change.

    Couldn't use it for fleet warp ins before.
    No Change.

    Couldn't use it for cov op cyno activity.
    No Change

    Does make some ganks easier.
    So do T3's by a great deal more

    Which can
    Fit a cov ops cloak
    Provide Warp Ins and Intel
    Provide Fleet Warp ins
    Use Cov Op Cynos/Blops


    So do Force Recons
    So do SOE Cruisers/Frigs.

    So you get the ability to not show up on dscan while you are uncloaked. Whoopy ****.

    Its a placebo change that isn't going to change anything. 5 second target delay from warping to a grid, or 5 second target delay uncloaking. It is literally the exact same functionality as it used to have. How about instead of sucking up this crap heap of a tweak you actually make an argument to make these ships truly useful.

    If a cloaky T3 or Stratios can pack 500+DPS and 70K+EHP...why the hell shouldn't a Combat Recon?

    Ask yourself.

    Does this change solve an issue that is causing this particular ship class to be underused.
    Does not showing up on DSCAN solve the issues with Combat Recons being underused.

    If that answer is no, then the change isn't worth it, ESPECIALLY, when the exact same mechanic already exists in game that solves this apparent issue. If Combat Recons are not being used because people know they are there, change their permissions on using Covert Cloaks. Boom mail me my check.
    Orange Faeces
    Farbissina Industrial and Procurement
    #2092 - 2014-12-31 03:38:27 UTC  |  Edited by: Orange Faeces
    Mario Putzo wrote:

    Doesn't stop people fitting a cloak to their ship like they did before and going afk, decloak to warp don't show on dscan...
    Why not just give it cov ops cloak? Its the same damn thing.

    Couldn't use it for reliable warp ins or on grid intel before.
    No Change.

    Couldn't use it for fleet warp ins before.
    No Change.

    Couldn't use it for cov op cyno activity.
    No Change

    Does make some ganks easier.
    So do T3's by a great deal more

    Which can
    Fit a cov ops cloak
    Provide Warp Ins and Intel
    Provide Fleet Warp ins
    Use Cov Op Cynos/Blops


    So do Force Recons
    So do SOE Cruisers/Frigs.

    So you get the ability to not show up on dscan while you are uncloaked. Whoopy ****.

    Its a placebo change that isn't going to change anything. 5 second target delay from warping to a grid, or 5 second target delay uncloaking. It is literally the exact same functionality as it used to have. How about instead of sucking up this crap heap of a tweak you actually make an argument to make these ships truly useful.

    If a cloaky T3 or Stratios can pack 500+DPS and 70K+EHP...why the hell shouldn't a Combat Recon?

    Ask yourself.

    Does this change solve an issue that is causing this particular ship class to be underused.
    Does not showing up on DSCAN solve the issues with Combat Recons being underused.

    If that answer is no, then the change isn't worth it, ESPECIALLY, when the exact same mechanic already exists in game that solves this apparent issue. If Combat Recons are not being used because people know they are there, change their permissions on using Covert Cloaks. Boom mail me my check.


    Its always most fun when people miss their own point! Now you are arguing that there is no change in the combat recon for many of the features of this limited 'cloak' but you still don't want it. This is because you're original point was that you want the T2 resists INSTEAD.

    My last paragraph, which you conveniently ignored in your response, explains why it is not necessarily an either-or decision between T2 resists and d-scan immunity. The resists can be adjusted to make them fleet capable. Its not that hard to imagine how that would work. If Rise wants to make combat recons Cov-Ops capable instead of d-scan immune, thats fine by me, but it does miss an opportunity to adjust the cloak mechanics in a way that discourages AFK cloaking by making pilots trade off DPS or cargo space for cloaks and/or depots.

    And to answer your question about whether combat recons will be more used with the d-scan immunity, my answer is yes it will. This limited 'cloak' capabiliity will have an effect on their use, and its nonsense to argue that it wont. There are many other changes in his list that help with this and there are lots of other issues to discuss, but the answer is yes.


    O. Faeces
    Mario Putzo
    #2093 - 2014-12-31 03:58:29 UTC
    Orange Faeces wrote:

    Its always most fun when people miss their own point! Now you are arguing that there is no change in the combat recon for many of the features of this limited 'cloak' but you still don't want it. This is because, you're original point was that you want the T2 resists INSTEAD.

    My last paragraph, which you conveniently ignored in your response, explains why it is not necessarily an either-or decision between T2 resists and d-scan immunity. The resists can be adjusted to make them fleet capable. Its not that hard to imagine how that would work. If Rise wants to make combat recons Cov-Ops capable instead of d-scan immune, thats fine by me, but it does miss an opportunity to adjust the cloak mechanics in a way that prevents AFK cloaking.

    And to answer your question about whether combat recons will be more used with the d-scan immunity, my answer is yes it will. This limited 'cloak' capabiliity will have an effect on their use, and its nonsense to argue that it wont. There are many other changes in his list that help with this and there are lots of other issues to discuss, but the answer is yes.

    O. Faeces


    You are right my original point was I want T2 resists on my Combat Recon so it is Combat Viable for its price point. Did you know that a Blackbird can perform the exact same functionality as a Rook for a fraction of the cost. The same applies to all of the T1 Cruiser EWAR ships vs their comparable "Combat Recons". There is a huge gap in cost effective utility. On the other side for only a couple hundred more mil you can get a T3 that absolutely ***** all over anything a Combat Recon does.

    Showing up on DSCAN is the least of this ship class' worries. T2 Resists would absolutely bump its cost effectiveness to the point I might say, **** ill bring this Rook instead of my Blackbird, because it might not get volleyed off field the moment I land on grid.

    I didn't acknowledge your last paragraph because it offers little to the discussion. CCP Rise can do anything he wants, and he usually does. He can set resists to anywhere he wants and he will, but that isn't the only issue with Recons.

    Why do I have 2 ships that perform essentially the same functionality. Is my paltry DPS from a Rook what you want (Kinetic Only no less!) If you want me to put down DPS why not let me use a Caracal, I get the better Damage and a similar tank for a fraction of the cost, its not like I can fit a Rook with Gank and Tank. And ECM. You can't have it all... If Rise is serious about tweaking this class, he absolutely needs to split the class.

    If you want to DPS as a Recon you bring a Combat Recon. Get rid of the Ewar bonuses and make it combat focused. Hell slap on a 4% Resist/level bonus over one of the EWAR bonuses to give it some added resist love.

    If you want to EWAR bring a Force Recon. Get rid of combat bonuses and add scanning bonuses, you know for recon ****.

    Also please stop saying limited cloak. If someone wants to AFK cloak in your system, they will just fit a ******* cloaking device to their ship. The DSCAN change is a placebo that is in no way going to impact the utility of Combat Recons. As long as I get more bang for my buck whelping Blackbirds and Caracals, or flying a T3, there is absolutely no reason at all to ever fly a Combat Recon.

    Combat Recons need to be vastly improved in terms of their ability to engage in Combat. Not hide from it better.
    Orange Faeces
    Farbissina Industrial and Procurement
    #2094 - 2014-12-31 04:41:39 UTC  |  Edited by: Orange Faeces
    Mario Putzo wrote:

    You are right my original point was I want T2 resists on my Combat Recon so it is Combat Viable for its price point. Did you know that a Blackbird can perform the exact same functionality as a Rook for a fraction of the cost. The same applies to all of the T1 Cruiser EWAR ships vs their comparable "Combat Recons". There is a huge gap in cost effective utility. On the other side for only a couple hundred more mil you can get a T3 that absolutely ***** all over anything a Combat Recon does.


    I took a moment to run the numbers for the null-sec HAC loadouts that were popular in my days in 0.0 (recent history on another toon). Using 3 mid-slots the HAC achieved 11k - 27k EHP (depending on damage type). We usually achieved very robust fleet tank with about 7-8 logistics for the group. Now, to tank up a combat recon with the resists as they were, we needed to plug a resist hole, so to achieve comparable tank numbers (13k - 27k EHP) on the combat recon we needed 4 mids. So these recons were as durable as the HACs and fit in with the same ratio of logistics to combat ships. This left 3 mids left for EWAR or tackle. Not a great tradeoff but reasonable for the cost, especially if the recons were huginn or lachesis which give the fleet robust tackle bonuses.

    Now, if I try the same thing with a celestis or a blackbird, and use 4 mids for tank, I can't get more than 8k - 14k EHP, which will need a higher number of logis in fleet and more likely that they can be popped before logistics get on them. It just wont work. Furthermore, this means only 1-2 mids remain for EWAR. This is not viable for HAC+Logi fleet disciplines. So, I'm not sure what you mean by, "Did you know that a Blackbird can perform the exact same functionality as a Rook for a fraction of the cost." It is a statement, that in light of your interest in fleet viability of combat recons, is plainly false in my experience. Is there another cruiser fleet discpline that you had in mind when you made this statement? If not, I'm just not sure how to respond to your claims.

    Mario Putzo wrote:
    ...
    Also please stop saying limited cloak. If someone wants to AFK cloak in your system, they will just fit a ******* cloaking device to their ship. The DSCAN change is a placebo that is in no way going to impact the utility of Combat Recons. As long as I get more bang for my buck whelping Blackbirds and Caracals, or flying a T3, there is absolutely no reason at all to ever fly a Combat Recon.

    Combat Recons need to be vastly improved in terms of their ability to engage in Combat. Not hide from it better.


    Given my explanation above, I certainly think there is a cost advantage to the combat recon over the T3 in the fleet context, regardless of recent market trends. You are right that they can still fit a cloak module. If the d-scan invulnerability experiment goes well, I wouldn't be surprised if there were ... additional changes to all cloaks in the future. Think about it...


    O. Faeces

    edit -- I should mention that the fleet arrangement is much less beneficial for Force Recons, as they stand. The resist profile results in fewer than 3 remaining mids (in all cases), usually only 1 remains, to make the tank viable. So, there's little overlap in that sense -- the force recon's role as cloaky scout/cyno/cov-ops/etc is not an issue. Adding a form of sneakiness to the Combat recon is a viable way to get it used in other settings.
    Jaysen Larrisen
    Caldari Provisions
    Caldari State
    #2095 - 2014-12-31 05:08:56 UTC
    Orange Faeces wrote:

    ....

    My last paragraph, which you conveniently ignored in your response, explains why it is not necessarily an either-or decision between T2 resists and d-scan immunity. The resists can be adjusted to make them fleet capable. Its not that hard to imagine how that would work. If Rise wants to make combat recons Cov-Ops capable instead of d-scan immune, thats fine by me, but it does miss an opportunity to adjust the cloak mechanics in a way that discourages AFK cloaking by making pilots trade off DPS or cargo space for cloaks and/or depots.

    And to answer your question about whether combat recons will be more used with the d-scan immunity, my answer is yes it will. This limited 'cloak' capabiliity will have an effect on their use, and its nonsense to argue that it wont. There are many other changes in his list that help with this and there are lots of other issues to discuss, but the answer is yes.


    O. Faeces


    Orange,

    You make solid points and so does Mario frankly.

    The the root problem is what are we doing to separate the Blackbird, Rook, and Falcon with this change?

    From a purely EWAR perspective...not really anything. So then I start looking at what is the point of the 3 different ships? The Blackbird is pretty straight forward - it's a purely an EWAR platform and can engage with a huge range advantage. The Falcon and Rook share the exact same EWAR bonus both have paper thin hp now. The T1 hull and Force Recon are both in solid position...the outlier is the Combat Recon.

    Trying to apply the d-scan immunity either in-lieu of or at the expense of legitimate eHP to the a dedicated EWAR platform that needs fleet survivability, particularly given that it will likely be a primary target in any group fight. Let me be clear, I'm not saying the d-scan immunity won't be useful and generate some - some - creative play but it's nowhere near worth the cost based on comparable alternatives.

    The full T2 resists would go a long way into helping justify the cost. If the EWAR bonus was adjusted to something utilizing increments of both the intensity of the Falcon and range of the Blackbird that would be a way to make the ship unique and useful.

    "Endless money forms the sinews of War" - Cicero

    Biomassed - Dust & EVE Podcast

    Twitter - @JaysynLarrissen

    Jaysen Larrisen
    Caldari Provisions
    Caldari State
    #2096 - 2014-12-31 05:34:34 UTC
    Orange Faeces wrote:
    Mario Putzo wrote:

    You are right my original point was I want T2 resists on my Combat Recon so it is Combat Viable for its price point. Did you know that a Blackbird can perform the exact same functionality as a Rook for a fraction of the cost. The same applies to all of the T1 Cruiser EWAR ships vs their comparable "Combat Recons". There is a huge gap in cost effective utility. On the other side for only a couple hundred more mil you can get a T3 that absolutely ***** all over anything a Combat Recon does.


    I took a moment to run the numbers for the null-sec HAC loadouts that were popular in my days in 0.0 (recent history on another toon). Using 3 mid-slots the HAC achieved 11k - 27k EHP (depending on damage type). We usually achieved very robust fleet tank with about 7-8 logistics for the group. Now, to tank up a combat recon with the resists as they were, we needed to plug a resist hole, so to achieve comparable tank numbers (13k - 27k EHP) on the combat recon we needed 4 mids. So these recons were as durable as the HACs and fit in with the same ratio of logistics to combat ships. This left 3 mids left for EWAR or tackle. Not a great tradeoff but reasonable for the cost, especially if the recons were huginn or lachesis which give the fleet robust tackle bonuses.

    Now, if I try the same thing with a celestis or a blackbird, and use 4 mids for tank, I can't get more than 8k - 14k EHP, which will need a higher number of logis in fleet and more likely that they can be popped before logistics get on them. It just wont work. Furthermore, this means only 1-2 mids remain for EWAR. This is not viable for HAC+Logi fleet disciplines. So, I'm not sure what you mean by, "Did you know that a Blackbird can perform the exact same functionality as a Rook for a fraction of the cost." It is a statement, that in light of your interest in fleet viability of combat recons, is plainly false in my experience. Is there another cruiser fleet discpline that you had in mind when you made this statement? If not, I'm just not sure how to respond to your claims.

    Mario Putzo wrote:
    ...
    Also please stop saying limited cloak. If someone wants to AFK cloak in your system, they will just fit a ******* cloaking device to their ship. The DSCAN change is a placebo that is in no way going to impact the utility of Combat Recons. As long as I get more bang for my buck whelping Blackbirds and Caracals, or flying a T3, there is absolutely no reason at all to ever fly a Combat Recon.

    Combat Recons need to be vastly improved in terms of their ability to engage in Combat. Not hide from it better.


    Given my explanation above, I certainly think there is a cost advantage to the combat recon over the T3 in the fleet context, regardless of recent market trends. You are right that they can still fit a cloak module. If the d-scan invulnerability experiment goes well, I wouldn't be surprised if there were ... additional changes to all cloaks in the future. Think about it...


    O. Faeces

    edit -- I should mention that the fleet arrangement is much less beneficial for Force Recons, as they stand. The resist profile results in fewer than 3 remaining mids (in all cases), usually only 1 remains, to make the tank viable. So, there's little overlap in that sense -- the force recon's role as cloaky scout/cyno/cov-ops/etc is not an issue. Adding a form of sneakiness to the Combat recon is a viable way to get it used in other settings.


    Ok, I've got to ask...if we are talking about actually fleet operations - the d-scan immunity seems to me will be even of lesser value. Once you get even a small fleet up the EWAR capability is in far greater demand than any theoretical "recon" function it could preform...there are simply better ships for that but nothing better for EWAR.

    Honestly...really seems like the combat recon aren't anything to do with "recon" they are much more of a Electronic Attack Cruiser. To that end, they should probably be treated as such.

    In reference to your point earlier about HP differences between the Blackbird and Rook..you are correct there is a difference. My numbers weren't quite as dramatic as yours but your set up makes sense. That said, a decently skilled Blackbird pilot can jam a lot of targets from a very long range...much longer than the Rook. So can a Blackbird do at least as good of a job disrupting a fleet as a Rook, yes, it can. Not always by any stretch but that certainly doesn't mean it's not at least nearly as effective.

    I won't go into the T3 bit since CCP Rise did make it pretty clear there is a future pass on T3's and the sound of it is that they will be noticeably toned down across several facets.

    "Endless money forms the sinews of War" - Cicero

    Biomassed - Dust & EVE Podcast

    Twitter - @JaysynLarrissen

    Orange Faeces
    Farbissina Industrial and Procurement
    #2097 - 2014-12-31 06:15:49 UTC  |  Edited by: Orange Faeces
    Jaysen Larrisen wrote:
    Ok, I've got to ask...if we are talking about actually fleet operations - the d-scan immunity seems to me will be even of lesser value. Once you get even a small fleet up the EWAR capability is in far greater demand than any theoretical "recon" function it could preform...there are simply better ships for that but nothing better for EWAR.

    Honestly...really seems like the combat recon aren't anything to do with "recon" they are much more of a Electronic Attack Cruiser. To that end, they should probably be treated as such.

    In reference to your point earlier about HP differences between the Blackbird and Rook..you are correct there is a difference. My numbers weren't quite as dramatic as yours but your set up makes sense. That said, a decently skilled Blackbird pilot can jam a lot of targets from a very long range...much longer than the Rook. So can a Blackbird do at least as good of a job disrupting a fleet as a Rook, yes, it can. Not always by any stretch but that certainly doesn't mean it's not at least nearly as effective.

    I won't go into the T3 bit since CCP Rise did make it pretty clear there is a future pass on T3's and the sound of it is that they will be noticeably toned down across several facets.


    Jaysen,

    Well, there could be some wrinkles in how the d-scan immunity affects HAC fleet behavior. As it stands today, the mix of Huginns vs. Lachesis that an opposing FC sees on scan can affect where they put position logistics anchor. If they see damping heavy group with few webs and no TP bonuses, they'll want to keep their logistics anchor close to the HACs. D-scan immunity means more unknowns going into a HAC fight. With the d-scan immunity change, FCs will have to count local, subtract the on-scan HACs/Logis and then consider the possibilities for the number of possible remaining combat recons. But I'm willing to concede that this is a minor effect for the d-scan immunity on fleet fights. (edit - note that this is a very simplistic example. there are many people who know a LOT more than I do about fleet tactics.)

    On the other hand, you make a reasonable point about blackbird vs. rook, ie range bonus vs. no bonus. This is a much more specific point about ECM-range balance that isn't a direct tie to the discussion of d-scan immunity. I can understand, however, why you would want the rook to have a superior tank given that it has to stay close to achieve the ECM effect, of course. All I can say on that is that with a 4-midslot tank on the rook, you have similar tank capability as the other combat recons, so staying with the HACs is viable, even if ECM is rarely the right choice for those types of fleet fights.

    And that seems to be more to the point -- its not that you can't tank up the rook and still have 3 mids free, but since there is no tackle benefit to these mids, why bring a rook to a fleet fight when a blackbird can stay relatively safe at range and jam things. That is the point that you two are making.

    You and Mario Putzo aren't complaining that people wont bring combat recons to fleet fights because they can and do (as I've shown). You are complaining that people wont bring Rooks to fleet fights! Now that I have understood why you two are so emo, I again feel confident in saying that this is not relevant to the d-scan immunity discussion. What you are concerned with is the Rook/Blackbird tradeoffs -- not the combat recons in general. All I can say on that is, the problem you are concerned with is how to balance ECM bonuses across the Blackbird hull cruisers and that is a discussion for a very different thread indeed. Its not that it isn't important, it just shouldn't derail the benefits the other combat recons are getting.


    O. Faeces
    Jaysen Larrisen
    Caldari Provisions
    Caldari State
    #2098 - 2014-12-31 07:20:56 UTC  |  Edited by: Jaysen Larrisen
    Orange Faeces wrote:


    Jaysen,

    Well, there could be some wrinkles in how the d-scan immunity affects HAC fleet behavior. As it stands today, the mix of Huginns vs. Lachesis that an opposing FC sees on scan can affect where they put position logistics anchor. If they see damping heavy group with few webs and no TP bonuses, they'll want to keep their logistics anchor close to the HACs. D-scan immunity means more unknowns going into a HAC fight. With the d-scan immunity change, FCs will have to count local, subtract the on-scan HACs/Logis and then consider the possibilities for the number of possible remaining combat recons. But I'm willing to concede that this is a minor effect for the d-scan immunity on fleet fights. (edit - note that this is a very simplistic example. there are many people who know a LOT more than I do about fleet tactics.)

    On the other hand, you make a reasonable point about blackbird vs. rook, ie range bonus vs. no bonus. This is a much more specific point about ECM-range balance that isn't a direct tie to the discussion of d-scan immunity. I can understand, however, why you would want the rook to have a superior tank given that it has to stay close to achieve the ECM effect, of course. All I can say on that is that with a 4-midslot tank on the rook, you have similar tank capability as the other combat recons, so staying with the HACs is viable, even if ECM is rarely the right choice for those types of fleet fights.

    And that seems to be more to the point -- its not that you can't tank up the rook and still have 3 mids free, but since there is no tackle benefit to these mids, why bring a rook to a fleet fight when a blackbird can stay relatively safe at range and jam things. That is the point that you two are making.

    You and Mario Putzo aren't complaining that people wont bring combat recons to fleet fights because they can and do (as I've shown). You are complaining that people wont bring Rooks to fleet fights! Now that I have understood why you two are so emo, I again feel confident in saying that this is not relevant to the d-scan immunity discussion. What you are concerned with is the Rook/Blackbird tradeoffs -- not the combat recons in general. All I can say on that is, the problem you are concerned with is how to balance ECM bonuses across the Blackbird hull cruisers and that is a discussion for a very different thread indeed. Its not that it isn't important, it just shouldn't derail the benefits the other combat recons are getting.

    O. Faeces


    There are some that would rather d-scan immunity not come into the game at all...again, I am not one of them. I think its a novel mechanic; I just don't value it perhaps to the degree that you do

    I totally disagree that discussions about the Rook/Falcon aren't relevant to the Recon ship discussion...all Recon ships are getting reworked, including Rooks and Falcons. Several role / hull perks are changing and that makes it specifically the purview of the discussion points that at least I have been trying to engage you in. This thread is not specifically focused on the d-scan immunity component of the Recon ship update and I'm addressing things from the perspective of the ships themselves and not just that sole component. If you think that's "emo"...lol...you have a very different definition of that than i do.

    The 4 racial recon ships all use different flavors of non-lethal effects to augment the fight such as neuts, damps, painters, and ECM. That is being addressed (in the form of bonuses and such) along with DPS, eHP, general hull changes, etc in this update, correct? I'm pretty sure that it is so what I'm discussing is specific to the Caldari hulls in this manner.

    As i've noted i'm totally fine with the d-scan immunity being in play. Rise indicating that he felt the d-scan immunity in conjunction with T2 resists would be too powerful and most of what i've seen since his announcement is advocating that folks would rather have the resists in lieu of the D-scan immunity based on what they feel are relative value of each capability.

    You did make an earlier point that it is very possible that Rise & Co will increase the resists from current levels to something below the HAC level. I don't speak for anyone else on this but my perception of his comments (which i went back and looked at again) is that they didn't want the ships too powerful in small gang fights. I happen to disagree that they will be anymore OP in small fleets than any number of ships out there.

    As for your comments on Recons as part of larger HAC-centric fleets...sure i'll buy that. That is also one specific type of fleet comp and not the complete picture of things. You are correct that ECM / ECCM is a topic in and of itself, no argument there, and I'm not fencing with folks on that in here either. I'm specifically addressing ships and the greater Recon role in the ship stable of the game.

    "Endless money forms the sinews of War" - Cicero

    Biomassed - Dust & EVE Podcast

    Twitter - @JaysynLarrissen

    Mario Putzo
    #2099 - 2014-12-31 07:29:16 UTC  |  Edited by: Mario Putzo
    Orange Faeces wrote:


    I took a moment to run the numbers for the null-sec HAC loadouts that were popular in my days in 0.0 (recent history on another toon). Using 3 mid-slots the HAC achieved 11k - 27k EHP (depending on damage type). We usually achieved very robust fleet tank with about 7-8 logistics for the group. Now, to tank up a combat recon with the resists as they were, we needed to plug a resist hole, so to achieve comparable tank numbers (13k - 27k EHP) on the combat recon we needed 4 mids. So these recons were as durable as the HACs and fit in with the same ratio of logistics to combat ships. This left 3 mids left for EWAR or tackle. Not a great tradeoff but reasonable for the cost, especially if the recons were huginn or lachesis which give the fleet robust tackle bonuses.

    Now, if I try the same thing with a celestis or a blackbird, and use 4 mids for tank, I can't get more than 8k - 14k EHP, which will need a higher number of logis in fleet and more likely that they can be popped before logistics get on them. It just wont work. Furthermore, this means only 1-2 mids remain for EWAR. This is not viable for HAC+Logi fleet disciplines. So, I'm not sure what you mean by, "Did you know that a Blackbird can perform the exact same functionality as a Rook for a fraction of the cost." It is a statement, that in light of your interest in fleet viability of combat recons, is plainly false in my experience. Is there another cruiser fleet discpline that you had in mind when you made this statement? If not, I'm just not sure how to respond to your claims.



    Thanks for proving my point. Nice support ship odd you didn't once mention DPS, about the only stat the Rook significantly blows away the blackbird. While you were salvaging your 27K EHP Rook for 3 ECM module, My Blackbird is sitting at ~28K EHP with 4ECM modules a prop mod and a Point. I have only 40 DPS though, your fit should be around 270-340 depending on if you went for BCUs or not. Of course we don't know because you were to focused on telling us about the ECM on there. I put a Cloak, Probe Launcher and 2 Nuets on mine.

    Since im not sure what role your Rook is in your 40 man gang (are you EWAR? Tackle? DPS? Im just not sure). My Blackbird is dual purpose. It can be a Hunterseeker, and it can function as a support ewar ship. While enjoying Armor fleets, it isn't shy sitting at 70K Applying up to 5 Jams in a shield fleet either.

    Do you see my point yet?

    Your argument is that the Rook a COMBAT Recon ship is better at applying ECM than a Blackbird when shield fit. because it can use more ECM, heck you didn't even mention is 57% advantage over the BB either in likelihood to jam more often.

    I would almost say sorry for the bait post about the blackbird, but it really did emphasize my point, that people view Combat Recons as Force multipliers and not Combat ships. Perhaps CCPs focus should would be better spent on differentiating Combat Recons from Force Recons? I mean if the metric is based on how much more EWAR? they can provide then T1 cruiser, isn't that an issue since each racial Force Recon is better in every aspect in applying EWAR?

    Again I will say that CCP is offering up a placebo change instead of an actual role defying change that is needed. DSCAN change is nothing more than something to make a next to worthless (the tackle ships aside) group of ships seem useful. When all it offers is a gimmick cloak...that has already raised one huge concern in FW and its not even on the test server.

    It is a bad adjustment that entirely misses the issue with the ship class. Combat Recons are not suitable for combat roles in their current state, because they have no defined role. Are they a Combat ship? or an Ewar ship? Should I bring a HAC or a Force Recon instead?

    Or a BB as the case may be.

    The Gimmick change would be neat...if the ships were at all useful for anything that Cov Cloaky ships don't do better.
    Orange Faeces
    Farbissina Industrial and Procurement
    #2100 - 2014-12-31 08:47:54 UTC  |  Edited by: Orange Faeces
    Mario Putzo wrote:
    Thanks for proving my point. Nice support ship odd you didn't once mention DPS, about the only stat the Rook significantly blows away the blackbird. While you were salvaging your 27K EHP Rook for 3 ECM module, My Blackbird is sitting at ~28K EHP with 4ECM modules a prop mod and a Point. I have only 40 DPS though, your fit should be around 270-340 depending on if you went for BCUs or not. Of course we don't know because you were to focused on telling us about the ECM on there. I put a Cloak, Probe Launcher and 2 Nuets on mine.

    Since im not sure what role your Rook is in your 40 man gang (are you EWAR? Tackle? DPS? Im just not sure). My Blackbird is dual purpose. It can be a Hunterseeker, and it can function as a support ewar ship. While enjoying Armor fleets, it isn't shy sitting at 70K Applying up to 5 Jams in a shield fleet either.

    Do you see my point yet?


    First of all, recons in a HAC fleet are focused on adding tackle and EWAR capability while having a tank that is consistent with the fleet. Same thing would go for a BS fleet. If they have any DPS at all it is a tertiary factor. Your inclusion of spaghetti tackle and neuts is... quaint but not the best use of a pod pilot. If you had proper skills/wallet your FC would have demanded something much more focused from you.

    Second, the EHP numbers I stated were only for the shields (since thats all that matters for logi compatibility). The total EHP of the HACs I was describing is no less than 35k EHP, and up to 45k for the higher resisted damage types. Your 28k EHP BB is actually only 23k (and thats not even the worst pattern!!) when looking at the armor (again, for logi compatibility). Your fit is not viable for fleet as it will be alpha'd off the field before logi reps can do anything about it. The range benefit is unlikely to be of much advantage against fleet-HACs or fleet-BS since they can easily apply damage at that range. On the otherhand, a Rook could be viable in a shield-fleet from a tank perspective. Notice that Rise doubled down on making the Rook unsuitable for armor tanking in the proposed changes.

    Finally, your point was that T2 resists are a preferable buff to d-scan immunity, but my post showed something very clearly -- that HAC/logi fleets are already viable with combat recons. So I don't see your point. Indeed, you have failed to make any argument that doesn't crumble for lack of understanding of the game. You proved that there are certain cases where scrub targets find it harder to deal with your 70km BB than a rook sitting at 30km. WTF does that have to do with d-scan immunity as an innovative new mechanic.

    Your continued issue with the Rook/Blackbird balance is further evidence that your concern really has NOTHING to do with d-scan immunity. It's really about the relative positions of the rook and blackbird specifically, as well as how ECM works (or doesn't work) in large scale engagements. While the rook bonuses may indeed need work, you continue to miss that d-scan immunity has nothing fundamental to do with the caldari EWar issues. Caldari Ewar issues are only 1/4th of the recon story, and ECM is the root cause for that, not the tank on your Rook.

    I urge you to cross train the other races so that you will have to tools you need to solve the different challenges you face in game. Focusing only on one race pigeon-holes you. Your narrow view of how the rook/blackbird performance affects the whole recon picture is evidence of very limited experience in the game. Maybe it is an area that needs to be addressed but not at the expense of the overall balance changes needed for recons.


    O. Faeces