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
Kagura Nikon
Native Freshfood
Minmatar Republic
#681 - 2014-12-19 08:53:47 UTC
hellokittyonline wrote:
I'm wondering why people see the need to compare the combat v force recons on the same platform, they serve different roles. Might as well just remove one of them and just have 1 recon cruiser per race. Also I feel the need to repeat that the DSCAN immunity is going to be ******* broken



Will only be meaningful on WH and maybe FW sites. Every other activity already relies in local 10 times more than in DSCAN.



Unfortunately the sensors mechanics in this game are too simplistic. The directional scanner should never be absolute. It should always have a chance of detecting something, and each ship would be a different chance, based on their signature againdt he scanning sensor strenght. Then would be easier and more balanced to just give a BONUS to the combat recons on that.

This also would create a good reason to keep a fleet small, because less hips woudl mean less likely to be detected. But we are stuck with a primitive and oversimplistic mechanic.

"If brute force does not solve your problem....  then you are  surely not using enough!"

Zappity
New Eden Tank Testing Services
#682 - 2014-12-19 08:57:57 UTC
Adam C wrote:
for trolly ideas i would of preferred combat recons dont appear in local but on dscan. is that even possible :D

Oh yes, PLEASE do that but for the Force Recons! No local would make them perfect solo and scout ships.

Zappity's Adventures for a taste of lowsec and nullsec.

VonBeerpuszken
Doomheim
#683 - 2014-12-19 09:06:06 UTC
Great change, but it would be better for Pilgrim:

Recon Ships Bonuses:
25% bonus to Energy Vampire and Energy Neutralizer transfer range
20% bonus to Energy Vampire and Energy Neutralizer transfer amoun
Fu Qjoo
Pangalactic Frontline Supply Agency
#684 - 2014-12-19 09:09:50 UTC
CCP Rise wrote:

Role Bonus:
Cannot be detected by directional scanners


This is the best idea you ever had - which is an achievement by its own.
A combat recon or 2 in every FW medium complex will contribute a lot to the new player experience,
hellokittyonline
Hellokitty's Online Adventure
#685 - 2014-12-19 09:12:01 UTC
Kagura Nikon wrote:
hellokittyonline wrote:
I'm wondering why people see the need to compare the combat v force recons on the same platform, they serve different roles. Might as well just remove one of them and just have 1 recon cruiser per race. Also I feel the need to repeat that the DSCAN immunity is going to be ******* broken



Will only be meaningful on WH and maybe FW sites. Every other activity already relies in local 10 times more than in DSCAN.



Unfortunately the sensors mechanics in this game are too simplistic. The directional scanner should never be absolute. It should always have a chance of detecting something, and each ship would be a different chance, based on their signature againdt he scanning sensor strenght. Then would be easier and more balanced to just give a BONUS to the combat recons on that.

This also would create a good reason to keep a fleet small, because less hips woudl mean less likely to be detected. But we are stuck with a primitive and oversimplistic mechanic.


Why shouldn't it be absolute? Because you wanna roleplay startrek? I dont care. It's already bubble space and this isn't a simulator, it'd be nice to see changes based on the overall balance of the GAME not just on a ship by ship basis and honestly you cant even compare ships across classes as the whole point is they serve different roles.

And if dscan is too absolute then change dscan, but do not make it absolute for everything EXCEPT that one shipclass that all the coolbros will be inevitably using. Really I'm just looking for changes that reinforce or encourage good fights in low sec so I don't have perspective on anything else. With that being said, this is going to **** on good fights for solo pvpers in low sec (example: look a slasher at the medium.. land at medium, oh a curse im dead).
HoruSeth
Republic University
Minmatar Republic
#686 - 2014-12-19 09:13:04 UTC  |  Edited by: HoruSeth
Kagura Nikon wrote:
Will only be meaningful on WH and maybe FW sites. Every other activity already relies in local 10 times more than in DSCAN.


No, it will not. It won't change WH a lot as they have no local, so whenever you press scan in DS you see nothing, but there can be a fleet of CovOps T3 out there already. Nothing will Change really. And most WHrs already have Scouts on their wormholes, you see recons early enough. And using Recons as Scout, who can not cloak is probably a bad idea due to jump mass range issue.
Only difference: You just have to add 1x Combat Probes Scanning when you start until you have whole control. That's it. stupid, simple technique.

But this will heavily influence FW and lowsec PvP and PvE, especially solo, small gang work. Totally agree on that Point. And from my current Point of view that influence is too much!

Buff the Recons? Yes!

Make CR DS-immune? Don't do it.
It will unbalance things in bad way as there is literelly not much how you can counter that in lowsec. This has been described by others already in this topic!

PS: CCP, why do you nerf Pilgrim again? Eliminate the neut strength bonus is not worth the extra range! Keep the strength bonus and only increase the range a little bit (maybe just 10%). With regard to Neuting role the Pilgrim was fine as it is! No improvement is done by giving it more range, but limiting the Neuting Power. Roll

On my gravestone will be written: "Died because he used sarcasm in the wrong moment"

Zappity
New Eden Tank Testing Services
#687 - 2014-12-19 09:15:27 UTC
I don't understand all the complaints about the d-scan thing. How is this different in principle to the covert ops cloak? It 'breaks' just as many things as d-scan immunity does. But then I've always thought that there should be a specific probe to detect (if not necessarily resolve) cloaked ships.

Zappity's Adventures for a taste of lowsec and nullsec.

hellokittyonline
Hellokitty's Online Adventure
#688 - 2014-12-19 09:18:33 UTC  |  Edited by: hellokittyonline
Zappity wrote:
I don't understand all the complaints about the d-scan thing. How is this different in principle to the covert ops cloak? It 'breaks' just as many things as d-scan immunity does. But then I've always thought that there should be a specific probe to detect (if not necessarily resolve) cloaked ships.

because if someone is cloaked in a medium with their t1 frig bait, they have a locking delay to wait out while you leave, furthermore you cant cloak within 30km of the plex so they have to burn in (if only slightly it still matters ALLOT) to get a point on you.
HoruSeth
Republic University
Minmatar Republic
#689 - 2014-12-19 09:21:41 UTC  |  Edited by: HoruSeth
Zappity wrote:
I don't understand all the complaints about the d-scan thing. How is this different in principle to the covert ops cloak? It 'breaks' just as many things as d-scan immunity does. But then I've always thought that there should be a specific probe to detect (if not necessarily resolve) cloaked ships.


E.g. because CovertOps have targeting delay (except Bomber, which are very fragile). And CovertOps Show up on DS at least for 1-3 seconds after Jump or can not Operation within 0m range to objects, etc, etc. This can make huge difference.

If I would be a low-sec-plexer and see People in local, but can not assign ships on DS to them I would assume now they have CovertOps, which gives me some space to react. If they later sit in Combat Recons behind the first gate or at the first gate of my combat plex I have literally no Chance, except with a second alt, scouting for me (Combat probes and warping in) before I am going in and Scouting the entrance when I am doing my Job.

This feature again heavily disturbs parts of solo/smallgang gameplay in Eve.

On my gravestone will be written: "Died because he used sarcasm in the wrong moment"

Suzuma
Makiriemi Industries
#690 - 2014-12-19 09:22:12 UTC
Lelob wrote:
Kagura Nikon wrote:
Lelob wrote:
Well this is just dissapointing. A curse is STILL worthless. The only good tank a curse could hope to get was from shields, and you are now removing shields and adding to hull wtf. Having a crappy tank, mediocre dps and kinda meh bonuses makes this crap. TD's cannot be reliably fit unless you armour tank, which is beyond ******** on a 4 lowslot tank. Removing shield mods for td's makes a curse worthless for fleet engagements because they always get primaried and will just get instapopped with the crappy tank. Neuts are not nearly as useful as something like ecm, first because they have a HARD range of 37.8km and second because medium neuts off a curse don't really neut enogh to be a threat unless they are neuting you over an extended time period, which never happens because they always get primaried because they have terrible tanks. Assuming t2 resists will resemble the zealot, then this is just bs, because amarr t2 has terribad shield em/therm resists.

The drone bonus is far less useful then you might think though because anyone with 1/2 a brain against just a curse will immediately kill your drones and laugh as you fail to kill them. Because you only really can have 2 flights of mediums (you need small drones to kill off frigs) this is a big deal. More to the point, this is in no way better then an ishtar. An ishtar has a better tank with the mwd sig reduction, can fit 3 medium neuts and run 2 of them fairly long, is still probably fastter and does wayyyy more dps. If you want to try a solo curse you are better 99% of the time with just buying an ishtar. If you are wanting to do fleet things, you are better off in flying a rook, which can actually have a shield tank and jam things (as opposed to td's), or a huggin/lach which can do range control far, far, far better then a curse ever could.

tldr: Curse still sucks at solo and gang engagements.




WHAAAT? The curse worthless? It can defeat basically any turreted subcapital ship in this game.

I am not sure if serious or trolling. Comapring a RECON witht he ishtar.. the most OP of the HACs (that are already supposed to be more pwoerful in direct combat)


Assuming this is solo/very small gang, where the td is really only capable of being fitted onto a curse due to the tank loss, anyone with a brain would just bumrush the curse, scram it and own face or disengage.

I'll give some examples of other common turret ships that might be fielded:

Vagabond: Can tank the curse for an extremely long time, while killing drones. That assumes he screwed up and didn't try to scram the curse, seens how it's now the big meta to have a asb scram vaga.

Deimos: Either he's rail fit and tries to snipe you and when he fails because of td he runs away OR he's blaster fit, which gurantees a scram and blamo he scrams the curse, nukes him with his sick dps and keeps his own stuff on with a nos. The curse might be able to win this if he makes the deimos chase after him like a dummie and neut him out, but that also assumes buffer fit without a cap booster. One of the big metas nowadays is a cap booster with a medium ancil armor repper. So if he gets neuted and nos'd he, simply cap boosts away to freedom or kills the curse. Either way the deimos wins.

Nomen? They all have cap boosters nowadays and so he probably disengages. He's fast enough that no curse can catch him.

Vigilant: New meta is rails, when the vigi get's td'd he disengages. He has vastly better speed/agility then a curse so he would have to be beyond stupid to get neuted out by a curse.

Cynabal: charge curse, own him with autocannons at short range, ezy pzy. If you have a long point instead of scram you run away

SFI: Cap boosted so he either runs away or gets a scram and laughs into the sun

THAT SAID, most solo pvpers now are in either ishtars or cerbs, both of which **** out curses for breakfast. Most ratters are also in either ishtars or gilas or carriers too, so again nbd.

If you fitted td's on a curse in a gang situation, you're already dead because either:

1. You tried fitting a 4 slot armour tank and got instapopped.
2. You tried fitting a td to a shield tank and got instapopped.


nice essay

deimos has no utility high btw

CEO

Makiriemi Industries

Karl Hobb
Imperial Margarine
#691 - 2014-12-19 09:22:15 UTC
Zappity wrote:
I don't understand all the complaints about the d-scan thing. How is this different in principle to the covert ops cloak? It 'breaks' just as many things as d-scan immunity does. But then I've always thought that there should be a specific probe to detect (if not necessarily resolve) cloaked ships.

My biggest misgiving about it is that Force Recons have to use a module whereas Combats get it for free. Granted, there is the whole combat probe disadvantage to the d-scan immunity over a Cov Ops Cloak, but I don't feel that's a good balancing point considering the benefits.

A professional astro-bastard was not available so they sent me.

Barrogh Habalu
Imperial Shipment
Amarr Empire
#692 - 2014-12-19 09:23:29 UTC  |  Edited by: Barrogh Habalu
Pilgrim:
Somehow I feel torn. On one hand, neut range is a big deal, and cloaky platform makes no exception. On the other hand, it won't be able to punch above its weight anymore (terms and conditions apply). The problem with the ship was that its usage was very niche though, so I don't know if that's really a big loss.
Curse seems to be all around better choice now that it trades cloaking ability for semi-cloak and all around better performance.
The only thing I see going for Pilgrim now is that you can have it decently armor tanked to go with armor logi gang while being capable to make use of bonused TD. Something tells me that some players would happily trade cloak for Curse neut bonuses though What?

D-scan immunity and WHs:
Well, if I were to ninja PvE in a wormhole, I'd be more concerned about cloaky Proteus or Loki, ones that were around like forever.
Granted, more people would do cloaky ganks now that force/combat recons are sturdier/sneakier since they are cheaper than T3s. Oh well. Probably not that much of a difference now that I think about it.

I think that as far as ganking concerned, in practice combat recons changes will impact k-space more, depending on what regions we are talking about.

I think this should be tried. Reserving the idea of making them visible at short ranges (under 1 AU) may be good, unless they are specifically designed to be flown offensively and pounce-tackling flat-footed pilots.

Nishachara wrote:
You can lower its visibility, for example not saying *insert combat recon of your choice* here in the column..but just ship or something.

Yeah, having to guess between 4 types of EWAR cruisers will surely lower their visibility...

Cyno synergy:
How do you feel about slightly buffing time reduction, maybe at least to -62,5%; -85% ? I always felt there's so little reason to use recons to actually cyno due to risks and costs. It doesn't do much in return for that tbh. Nice for those who don't have spare character for dedicated CovOps ofc, but I'd rather see more reason to go this route over just lacking whelp toon (I use the term loosely here) P

hellokittyonline wrote:
Also if you want ships to fall in line with t3s just make isk actually matter, the only reason t3s are op is because scrubs can get a pimped out one for 15 bucks or a few hours of incursions. T3s becoming overused is a perfect example of how isk faucets like incursions affect the meta. If its too easy to get e-rich (or too cheap to get e-rich with real life money) anything with even the slightest advantage will be abused no matter the cost because the risk has been made negligible due to inflation.

And how exactly inflation and ISK faucets affect availability of long-present things that are built with materials?
Please.

baltec1 wrote:
Love these threads, we have one guy moan about how the curse is now overpowered instantly followed by someone else flailing around decrying the the curse is near useless.

With most of such posters pointing out different ways to fit and use those ships. So, working as intended, I guess?

Herzog Wolfhammer wrote:
Recons immune to D-Scan.

This might have worked back when one had to actually scan down every site. Back when you can "stealth" with ECCMs in the mids and force them to put the combat probes in closer.

Now it's suicide.

Why even leave highsec?

What was changed though? Anoms were always warpable, sites still have to be scanned down, ECCM "stealthing" could always be sidestepped by using core probes unless we're talking about missions (where ECCM works). I feel I'm missing something. Maybe you mean grav sigs -> ore anoms change...

Also, about Curse tank, is it indeed so bad if you really need to fit armor and TDs, considering that we are getting full T2 resistance profile? I think we're looking at 55k+ ehp fairly easily - I mean, shield tanked one we have today is less tanky than that IIRC. But it's nice to have an option.
Viceran Phaedra
Instar Heavy Industries
#693 - 2014-12-19 09:27:59 UTC
I like the D-scan immunity idea; we should at least try implementing it for awhile and see where it goes. You can always remove it if it doesn't work out. Otherwise, solid changes. Well done, Rise!

Please make sure the missile bonus covers RLM launchers for the Rook as well!

Chief Executive Officer

Instar Heavy Industries

hellokittyonline
Hellokitty's Online Adventure
#694 - 2014-12-19 09:29:46 UTC  |  Edited by: hellokittyonline
Barrogh Habalu wrote:

hellokittyonline wrote:
Also if you want ships to fall in line with t3s just make isk actually matter, the only reason t3s are op is because scrubs can get a pimped out one for 15 bucks or a few hours of incursions. T3s becoming overused is a perfect example of how isk faucets like incursions affect the meta. If its too easy to get e-rich (or too cheap to get e-rich with real life money) anything with even the slightest advantage will be abused no matter the cost because the risk has been made negligible due to inflation.

And how exactly inflation and ISK faucets affect availability of long-present things that are built with materials?
Please.

You clearly have the IQ of a squirrel because I said nothing about the availability and was obviously talking about the frequency of use. Notice I said "T3s becoming overused" and not "T3s becoming more available".

But to answer your question, when a pimped t3 suddenly costs $15 instead of $30 you better believe you're going to see more of them.
Big Lynx
#695 - 2014-12-19 09:31:26 UTC
@hellokitty

face bookmarked
Fu Qjoo
Pangalactic Frontline Supply Agency
#696 - 2014-12-19 09:32:06 UTC
Zappity wrote:
I don't understand all the complaints about the d-scan thing. How is this different in principle to the covert ops cloak? It 'breaks' just as many things as d-scan immunity does. But then I've always thought that there should be a specific probe to detect (if not necessarily resolve) cloaked ships.


Much <3, but you know how plexing mechanisms work in FW, right?
Nami Kumamato
Perkone
Caldari State
#697 - 2014-12-19 09:34:06 UTC
Stacy Lone wrote:
CCP Rise wrote:
Combat Recons will now be permanently undetectable by directional scanners

Have you considered the implications this will have for wspace?

I mean it might work for 0.0 where you can see that *something* is there through local, but in wspace, this will be absolutely OP and hilarious. No local, not even DScan anymore, how are you supposed to even get any intel?

The only way to detect such a ship is by having either eyes on all wholes (requires multitude of characters) and thus seeing it enter or by constant combat probing, which can be seen by the enemy.

I fear that this will make this ship far out of line in wspace, where intel is already harder to get than in 0.0.


CCP - increasing the levels of paranoia and jump-scares daily! :D
Well gues now I'll get 200 more bps when tiptoeing through wormholes What?

Fornicate The Constabulary !

Onslaughtor
Phoenix Naval Operations
Phoenix Naval Systems
#698 - 2014-12-19 09:34:28 UTC
A few things.

Rook needs another low. either for another powergrid mod or more armor tank. take a high slot and move it to a low. Also I feel that the rook needs a ecm range bonus to remain competitive. a 20% strength and 10% range bonus would fit really nicely if you dont want it to be to powerful.


Pilgrim was actually really good with the amount bonus, but range is also needed, so maybe a 10% amount and 30% range?. The real issue with the ship, (and the curse) is that tracking disruption only work on 3 of eve's weapon systems. So I would look into actually having them affect missiles and drones in some way. This would go a long way to making all TD bonused ships be better and actually useful. Would likely have to nerf TD a bit and buff the specialist ships like you did ecm and damps tho, but I think we would all be ok with this.

Finally the big pink flame engulfed elephant in the room. This D-scan immunity thing..... Its a really bad idea as presented.
The main problem I find with it is how it basically destroys all trust in d-scan as a intel inference tool, with no real way to counter it. Combat probes while they do work require either a gimpfit or a specialist ship to fit them. Also there is no choices in the matter, no draw backs in it. The only other thing we have that is dscan immune is the sensor inhibitor, which is so costly and has so many draw backs that its a very useful but also extremely niche tool. In your proposed state implementing it would be bad for the over all health of the game and would add unenjoyable complexity to the system.
Gemma Wildfire
Urhi Inc
#699 - 2014-12-19 09:36:59 UTC
I don't like the dscan change at all. There is already a mechanism for not appearing on dscan, cloaking. If you do anything then please remove the post cloak targeting delay for recons instead.
Zappity
New Eden Tank Testing Services
#700 - 2014-12-19 09:37:25 UTC
:shrug: Don't sit at zero on the beacon. You will see them as soon as they land on grid.

Perfect intel is bad, just like perfect stealth is bad.

Zappity's Adventures for a taste of lowsec and nullsec.