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] Reduction in Fighter and Fighter Bomber scan resolution

First post First post First post
Author
Previous Topic Next Topic
Jenn aSide
Soul Machines
The Initiative.
#41 - 2015-01-05 22:15:06 UTC
Rawketsled wrote:
+1 for drone session change timers.


+2 for this

But alas the CCP way is to use a Jackhammer on something requiring a scalpel ....
Bienator II
madmen of the skies
#42 - 2015-01-05 22:16:10 UTC
Sugar Kyle wrote:
Bienator II wrote:
sounds reasonable. any changes planed to address skynet carriers?



To quote Fozzie:

Quote:
I know that some people who are hoping for a major nerf to assigned fighters will be unhappy that this change will only have a small-moderate effect on that activity. We have been keeping a close eye on the way fighters are used ever since our recent rounds of drone rebalancing and we aren't ruling out any potential future changes at this time. However we are not going to rush into any larger changes to fighter mechanics.


It is a topic that I have and several other members of the CSM have brought up with CCP as a problem. No solutions for you yet, sad to say.

i must be blind i completely overread the last paragraph. thanks for pointing it out for me :P

how to fix eve: 1) remove ECM 2) rename dampeners to ECM 3) add new anti-drone ewar for caldari 4) give offgrid boosters ongrid combat value
Lord Takani
Eve's Retirement Society
#43 - 2015-01-05 22:17:56 UTC  |  Edited by: Lord Takani
Remove the assignment of fighters. Problem of inties with fighter support solved(Not the primary issue but still a good update IMO). On to the stated issue. Re-launch fighter delay. Easy to implement, as with re-entering wormholes.
Tykonderoga
Imperial Academy
Amarr Empire
#44 - 2015-01-05 22:18:51 UTC
baltec1 wrote:
Brace yourselves, NC DOT superwaggon arriving.



Brace yourself, you use drones too, friend. And your bears do too.
baltec1
Bat Country
Pandemic Horde
#45 - 2015-01-05 22:20:07 UTC
Lord Takani wrote:
Remove the assignment of fighters. Problem of inties with fighter support solved.


This isnt the problem they are fixing.
killerkeano
Doomheim
#46 - 2015-01-05 22:20:36 UTC
're-launch delay'

there 'exploit' (if that is even in existence) fixed.
Yarda Black
The Black Redemption
#47 - 2015-01-05 22:21:05 UTC
So prevent relaunch within 20 seconds of scooping/returning drones. Right now I cant reconnect with drones more than once a minute for example. Use that system to prevent an "unfair dps" increase. Since that is a more general way to influence drones, any future tactic involving drones other than fighers or fighterbombers is solved pro-actively too.
Haidere
Republic Military School
Minmatar Republic
#48 - 2015-01-05 22:21:11 UTC
The scan res nerf is a bandaid, a lazy fix to a rare problem, there are better, smarter ways to fix the problem.

I see two solutions, both require a bit more work and will fix all possible exploits with this issue:

1: Make the cycle time not reset when you withdraw drones

Or

2: Add relaunch delay for any drones/fighters


CCP don't be lazy, actually FIX the issue instead of trying to slap a bandaid on it.
baltec1
Bat Country
Pandemic Horde
#49 - 2015-01-05 22:21:25 UTC
Tykonderoga wrote:
baltec1 wrote:
Brace yourselves, NC DOT superwaggon arriving.



Brace yourself, you use drones too, friend. And your bears do too.


We dont care. Death to all supers.
Firefox4312 Yatolila
Blackwater USA Inc.
Pandemic Horde
#50 - 2015-01-05 22:23:37 UTC
As the "exploit" has already been explained on how it works, I don't need to explain it here.

So, if scooping and redeploying is an exploit, why even have that mechanic in the game? The exploit just comes from the laziness of CCP's coding. If they decided to just make the ROF a global timer per drone. So if you pulled and redeployed that timer never got reset, then this exploit would never have existed nor would be an issue today.

The bottom line is that, CCP would rather just nerf something to fix an issue, rather than look at the coding and be like "Oh, we screwed up, and this exploit is our fault for bad coding, we should probably fix this." But instead of doing that, they'd rather go "Oh, we screwed up, but let's not admit it, and just change scan res so that we kinda fixed the exploit without actually fixing our terrible coding."


Just make each fighter and fighter bomber's ROF work on a global timer than doesn't reset when you scoop and deploy and everything is fixed. There's no legitimate reason to nerf the scan res of Fighters and FBs unless CCP would rather just make supercarriers used less and less than they already are.
Kaarous Aldurald
Black Hydra Consortium.
#51 - 2015-01-05 22:24:43 UTC
Yet another exploit tied to the drone system. Is it about time to start yelling "Death to Drones!" as much as we yell "Death to all Supers!", perhaps?

"Verily, I have often laughed at the weaklings who thought themselves good because they had no claws."

One of ours, ten of theirs.

Best Meltdown Ever.
TrouserDeagle
Beyond Divinity Inc
Shadow Cartel
#52 - 2015-01-05 22:25:00 UTC
0/10, doesn't go far enough as usual
Kaarous Aldurald
Black Hydra Consortium.
#53 - 2015-01-05 22:26:09 UTC
Yarda Black wrote:
So prevent relaunch within 20 seconds of scooping/returning drones.


They're trying to lower server load caused by drones, not increase it. The system would have to track each individual drone's lowered timer.

"Verily, I have often laughed at the weaklings who thought themselves good because they had no claws."

One of ours, ten of theirs.

Best Meltdown Ever.
Frostys Virpio
State War Academy
Caldari State
#54 - 2015-01-05 22:27:35 UTC
Kaarous Aldurald wrote:
Yet another exploit tied to the drone system. Is it about time to start yelling "Death to Drones!" as much as we yell "Death to all Supers!", perhaps?


Death to all supers didn;t work all that well so while I might support the idea, I doubt it will have any real success...
Lord Takani
Eve's Retirement Society
#55 - 2015-01-05 22:27:48 UTC
baltec1 wrote:
Tykonderoga wrote:
baltec1 wrote:
Brace yourselves, NC DOT superwaggon arriving.



Brace yourself, you use drones too, friend. And your bears do too.


We dont care. Death to all supers.


I don't get why you guys dont want to improve the game. So there are issues, and instead of complaining on your in-game enemy posting that it might be better to go back to the drawing board, your bashing complete nonsense totally not related to the subject and totally not constructive.

I hope this is not the level of CSM, as if it does then EVE will not get better and CCP should just ditch the entire CSM concept, as they will be destroying there company value.
killerkeano
Doomheim
#56 - 2015-01-05 22:27:57 UTC
baltec1 wrote:
Tykonderoga wrote:
baltec1 wrote:
Brace yourselves, NC DOT superwaggon arriving.



Brace yourself, you use drones too, friend. And your bears do too.


We dont care. Death to all supers.



you get boring really quickly. Its not even witty, accurate or constructive. Go spam troll EVEnews24 or that other one, or even better, go talk to a RL human

No wonder even your corp mates don't like you
Tykonderoga
Imperial Academy
Amarr Empire
#57 - 2015-01-05 22:28:32 UTC
baltec1 wrote:
Tykonderoga wrote:
baltec1 wrote:
Brace yourselves, NC DOT superwaggon arriving.



Brace yourself, you use drones too, friend. And your bears do too.


We dont care. Death to all supers.



Then self destruct all your supers and titans and prove to me you are not a hypocrite.
Frostys Virpio
State War Academy
Caldari State
#58 - 2015-01-05 22:28:43 UTC
Kaarous Aldurald wrote:
Yarda Black wrote:
So prevent relaunch within 20 seconds of scooping/returning drones.


They're trying to lower server load caused by drones, not increase it. The system would have to track each individual drone's lowered timer.



Timer on the pilot, can't launch any drone for 20 seconds after launching some others. But that is also server load technically...
Primary This Rifter
Mutual Fund of the Something
#59 - 2015-01-05 22:29:05 UTC
"Ishtars are fine, but fighters definitely need a scan res nerf."
Panther X
Destructive Influence
Northern Coalition.
#60 - 2015-01-05 22:30:56 UTC
Firefox4312 Yatolila wrote:
As the "exploit" has already been explained on how it works, I don't need to explain it here.

So, if scooping and redeploying is an exploit, why even have that mechanic in the game? The exploit just comes from the laziness of CCP's coding. If they decided to just make the ROF a global timer per drone. So if you pulled and redeployed that timer never got reset, then this exploit would never have existed nor would be an issue today.

The bottom line is that, CCP would rather just nerf something to fix an issue, rather than look at the coding and be like "Oh, we screwed up, and this exploit is our fault for bad coding, we should probably fix this." But instead of doing that, they'd rather go "Oh, we screwed up, but let's not admit it, and just change scan res so that we kinda fixed the exploit without actually fixing our terrible coding."


Just make each fighter and fighter bomber's ROF work on a global timer than doesn't reset when you scoop and deploy and everything is fixed. There's no legitimate reason to nerf the scan res of Fighters and FBs unless CCP would rather just make supercarriers used less and less than they already are.



I think that's what they want really.

@CCP_Fozzie c'mon Fozzie, just admit it.

Why the hard on for nerfing supers so much lately? The session timer for supers is a much more reasonable fix for this issue than absolutely killing scan res. Fix it, don't slap a bandaid on it and call it a day.

While the Chicken Little crew is wailing about "oooh fighter assist is killing our lowsec roams into null" really there are much more important issues to address.

My Titan smells of rich Corinthian Leather...