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.
 

[Retribution 1.1] Black Ops Little Things - now with Covert Cyno update

First post First post
Author
CCP Fozzie
C C P
C C P Alliance
#241 - 2013-01-31 15:19:00 UTC
Syrias Bizniz wrote:
CCP Fozzie wrote:
A couple questions I can quickly answer:

  • No this is not the "done" state for black ops. The covert cyno change is just another little things tweak in the interim.

  • I don't think we have the bandwidth to change slot layouts on blockade runners this patch, but it's something to consider when we rebalance transport ships later.

  • Bombers are getting a 50% CPU reduction, so the end result will be exactly the same.




  • A 50% CPU reduction on Bombers? Is that a typo and you meant '50 CPU reduction' cause a Cov Ops Cloak uses 50 CPU on a Bomber?

    Because if not, people won't be able to use an expanded probe launcher on a Bomber anymore. At least not without slapping a good chunk of coprocs on it.


    Edit:

    And no, end result wouldn't be exactly the same if you just reduce it by 50 cpu. Maybe there are people out there that use coprocs to get the cpu to fit some modules. If you reduce the CPU of the bombers, the inital fittings will all be the same. However, coprocs will then give less CPU than they do now and will maybe make some seriously tight fittings unfittable anymore. To be fair, i don't have such a fitting lying around. But the possibility is there that this change will affect some very specialized bomber fittings.


    I worded that badly, sorry. What it means is that the bombers now get a 50% reduction in the CPU requirements of cloaks.

    Game Designer | Team Five-0

    Twitter: @CCP_Fozzie
    Twitch chat: ccp_fozzie

    Omnathious Deninard
    University of Caille
    Gallente Federation
    #242 - 2013-01-31 15:56:07 UTC
    @ CCP Fozzie, do you have some fun things in mind for the Black Ops ships in mind for there total overhaul? Will we be seeing the overhaul possibly this summer or will T2 ships be started with frigates?

    If you don't follow the rules, neither will I.

    Kerdrak
    Querry Moon
    #243 - 2013-01-31 16:06:45 UTC
    RubyPorto wrote:

    The AFK cloaker is not at risk because he is not doing anything. Just like you're not at risk when sitting AFK in your station.


    No matter how many times you repeat the same words, it's not going to be true.

    As I said before, you can cloak for days in a system waiting for the perfect opportunity. It's the ability to perform a perfect strike risk free what is unbalanced.
    Drosal Inkunen
    Spreadsheeters
    #244 - 2013-01-31 16:53:59 UTC
    Kerdrak wrote:
    RubyPorto wrote:

    The AFK cloaker is not at risk because he is not doing anything. Just like you're not at risk when sitting AFK in your station.


    No matter how many times you repeat the same words, it's not going to be true.

    As I said before, you can cloak for days in a system waiting for the perfect opportunity. It's the ability to perform a perfect strike risk free what is unbalanced.

    To expand on what Kerdrak said, the reason the comparison between afk cloaked and afk docked isn't a good one is that when you undock, you show up on d-scan so they know you are now active. When you become active in the cov ops ship, there is nothing indicating this to players in system.

    I am not talking about a ship without a cov-ops cloak and I don't believe Kerdrak is either since he says there is no risk after waiting for the opportunity..

    Omnathious Deninard
    University of Caille
    Gallente Federation
    #245 - 2013-01-31 16:59:31 UTC
    Ta-Dam
    #246 - 2013-01-31 18:46:50 UTC
    TravelBuoy wrote:
    More blablbla. The local is the perfect intel tool ? ROTFL
    No thats not. LLocal is the counter against the AFK cloaker ? What ? :DDDD
    Newer was, you dont see on local, enemy AFK or not. Remove local ? More give a big red I-Win button for cloakers ? WTF u talking about ? The real answer is, the active player has risk in system, but AFK cloaker is not, because uncatchable.

    God save us, when a big alliances such the Goon or other big entities starting new tactics for kill the full EVE 0.0 economics and go to loading up all 0.0 systems with AFK cloaker alts.
    I would look at it how you would be crying when at least 10 AFK cloaker poisoning every 0.0 system where you live.
    And this is the new trend.
    Inactive players disturbing the active players when they dont play, its a bad game mechanics.

    +1
    RubyPorto
    RubysRhymes
    #247 - 2013-01-31 20:50:50 UTC
    Kerdrak wrote:
    RubyPorto wrote:

    The AFK cloaker is not at risk because he is not doing anything. Just like you're not at risk when sitting AFK in your station.


    No matter how many times you repeat the same words, it's not going to be true.

    As I said before, you can cloak for days in a system waiting for the perfect opportunity. It's the ability to perform a perfect strike risk free what is unbalanced.


    No matter how many times you try to ignore the most important point, it's not going to disappear.

    Name for me a counter to Local's use as a perfect intel tool (providing both the system population and list of who is active)* that doesn't involve AFK cloaking.

    *By the defenders only, no less, because AFK Stationing or POSing is possible for the defenders to hide their true numbers.

    You can cloak for days doing nothing in a system waiting for something that appears to be the perfect opportunity. It's the ability to perform a not-at-all-surprising attack (Local means the defender get's to know it's coming, just not when) with the very real possibility of falling into a trap (because of the whole "in the middle of hostile space" thing).

    "It's easy to speak for the silent majority. They rarely object to what you put into their mouths." -Abrazzar "the risk of having your day ruined by other people is the cornerstone with which EVE was built" -CCP Solomon

    Drosal Inkunen
    Spreadsheeters
    #248 - 2013-01-31 20:53:23 UTC
    RubyPorto wrote:
    Kerdrak wrote:
    RubyPorto wrote:

    The AFK cloaker is not at risk because he is not doing anything. Just like you're not at risk when sitting AFK in your station.


    No matter how many times you repeat the same words, it's not going to be true.

    As I said before, you can cloak for days in a system waiting for the perfect opportunity. It's the ability to perform a perfect strike risk free what is unbalanced.


    No matter how many times you try to ignore the most important point, it's not going to disappear.

    Name for me a counter to Local's use as a perfect intel tool (providing both the system population and list of who is active)* that doesn't involve AFK cloaking.

    *By the defenders only, no less, because AFK Stationing or POSing is possible for the defenders to hide their true numbers.

    You can cloak for days doing nothing in a system waiting for something that appears to be the perfect opportunity. It's the ability to perform a not-at-all-surprising attack (Local means the defender get's to know it's coming, just not when) with the very real possibility of falling into a trap (because of the whole "in the middle of hostile space" thing).

    A cyno/bridge is a way to counter local being a perfect intel tool before the attack.
    Only one person shows up in local, yet that one person represents everything that is going to be jumped in.
    RubyPorto
    RubysRhymes
    #249 - 2013-01-31 21:16:02 UTC  |  Edited by: RubyPorto
    Drosal Inkunen wrote:
    RubyPorto wrote:
    Kerdrak wrote:
    RubyPorto wrote:

    The AFK cloaker is not at risk because he is not doing anything. Just like you're not at risk when sitting AFK in your station.


    No matter how many times you repeat the same words, it's not going to be true.

    As I said before, you can cloak for days in a system waiting for the perfect opportunity. It's the ability to perform a perfect strike risk free what is unbalanced.


    No matter how many times you try to ignore the most important point, it's not going to disappear.

    Name for me a counter to Local's use as a perfect intel tool (providing both the system population and list of who is active)* that doesn't involve AFK cloaking.

    *By the defenders only, no less, because AFK Stationing or POSing is possible for the defenders to hide their true numbers.

    You can cloak for days doing nothing in a system waiting for something that appears to be the perfect opportunity. It's the ability to perform a not-at-all-surprising attack (Local means the defender get's to know it's coming, just not when) with the very real possibility of falling into a trap (because of the whole "in the middle of hostile space" thing).

    A cyno/bridge is a way to counter local being a perfect intel tool before the attack.
    Only one person shows up in local, yet that one person represents everything that is going to be jumped in.


    So you're saying that, if AFK cloaking disappeared, you'd keep ratting if you knew there was a hostile active in your system? Funny, because that's never been my experience when hunting ratters who have half a brain.

    Without AFK Cloaking, Local provides the defenders a complete list of those who are both in system and active.
    Please explain how "a cyno" provides an exception (i.e. counter) to either part of that.

    "It's easy to speak for the silent majority. They rarely object to what you put into their mouths." -Abrazzar "the risk of having your day ruined by other people is the cornerstone with which EVE was built" -CCP Solomon

    Drosal Inkunen
    Spreadsheeters
    #250 - 2013-01-31 21:39:08 UTC
    RubyPorto wrote:
    Drosal Inkunen wrote:

    A cyno/bridge is a way to counter local being a perfect intel tool before the attack.
    Only one person shows up in local, yet that one person represents everything that is going to be jumped in.


    So you're saying that, if AFK cloaking disappeared, you'd keep ratting if you knew there was a hostile active in your system? Funny, because that's never been my experience when hunting ratters who have half a brain.

    Without AFK Cloaking, Local provides the defenders a complete list of those who are both in system and active.
    Please explain how "a cyno" provides an exception (i.e. counter) to either part of that.


    Of course anyone with half a brain is going to dock up when their is a known hostile active in system. That wasn't what you had originally asked though.

    Local does show a complete list of who is in system. It does not give a list of those who are active with or without afk cloaking.
    If I want to be stupid enough to park my ship on a celestial or in a safe spot I can. Just because I'm in local doesn't mean I'm active.

    How I'm saying a cyno counters the "perfect intelligence" of local is that you only see one ship in local, but within a split second that one ship is suddenly many, many more. The people are not presently in the system, but they are effectively wherever the cyno ship is.

    So, if the cyno ship gets to you, the whole fleet gets to you.

    Local said 1 ship, but that ship represented the fleet. Local gave you a false representation of the force able to be used in your system.
    RubyPorto
    RubysRhymes
    #251 - 2013-01-31 22:26:39 UTC
    Drosal Inkunen wrote:
    RubyPorto wrote:
    Drosal Inkunen wrote:

    A cyno/bridge is a way to counter local being a perfect intel tool before the attack.
    Only one person shows up in local, yet that one person represents everything that is going to be jumped in.


    So you're saying that, if AFK cloaking disappeared, you'd keep ratting if you knew there was a hostile active in your system? Funny, because that's never been my experience when hunting ratters who have half a brain.

    Without AFK Cloaking, Local provides the defenders a complete list of those who are both in system and active.
    Please explain how "a cyno" provides an exception (i.e. counter) to either part of that.


    Of course anyone with half a brain is going to dock up when their is a known hostile active in system. That wasn't what you had originally asked though.

    Local does show a complete list of who is in system. It does not give a list of those who are active with or without afk cloaking.
    If I want to be stupid enough to park my ship on a celestial or in a safe spot I can. Just because I'm in local doesn't mean I'm active.

    How I'm saying a cyno counters the "perfect intelligence" of local is that you only see one ship in local, but within a split second that one ship is suddenly many, many more. The people are not presently in the system, but they are effectively wherever the cyno ship is.

    So, if the cyno ship gets to you, the whole fleet gets to you.

    Local said 1 ship, but that ship represented the fleet. Local gave you a false representation of the force able to be used in your system.


    It's exactly what I asked.

    In your example (remember, this is in the hypothetical that AFK cloaking doesn't exist), Local shows 1 ship AND that it's active.

    RubyPorto wrote:
    Name for me a counter to Local's use as a perfect intel tool (providing both the system population and list of who is active)* that doesn't involve AFK cloaking.


    Which means that it still provides the current system population, the fact that there's a hostile in system, AND the fact that that hostile is active. So no, cynos do not counter local's use as a perfect intel tool (providing both the system population and the much more important list of who is active).

    Once again, Name for me a counter to Local's use as a perfect intel tool (providing the current system population, the presence or absence of a hostile element, and the list of who is active) aside from AFK cloaking. Especially the important two pieces of Information that local-without-AFK-Cloaking would provide; the presence or absence of a hostile element and a list of who is active.

    "It's easy to speak for the silent majority. They rarely object to what you put into their mouths." -Abrazzar "the risk of having your day ruined by other people is the cornerstone with which EVE was built" -CCP Solomon

    Evanga
    DoctorOzz
    Domain Research and Mining Inst.
    #252 - 2013-01-31 22:53:53 UTC
    Stop going off topic for the love of god.
    Not all cloakers are afk, not everybody docked up is afk. You are filling int the void and its not being afk.

    The problem is your bots wont be able to make any isk! Cry
    TravelBuoy
    Imperial Academy
    Amarr Empire
    #253 - 2013-02-01 11:26:18 UTC  |  Edited by: TravelBuoy
    RubyPorto wrote:
    more blabla


    Man you talking idiocracy.
    Local is a counter against AFK cloakers ? ROTFL
    The local just show it who is in the system, nothing else and showing for the both side the same informations without advantage.
    You need scanning the whole system to check, you see enemy ship or not, but you cant see who AFK or not.


    You talkin about docking ship ? LOL When someone undocked and changing his "position", instanlty show on scanner and will vulnerable.(or cloaker get visual contact if cloaking at station grid) And dont forget, the station build for so much ISK, to defend pilots in "home" system. But AFK cloaker get the advantage to terrorize them. Oh and wait, what happen when no station in the system ? :D

    What happen when an AFK pilots after 3 days long AFK changing his position ? Nothing, he still unattackable and dont have counter in system just seeing them on local and nothing else. They are unscanable, they are uncatchable etc and cloakers have advantage for where,when starting their attack and, they can choose what situation is the best moment for them, contrary as undocked and vulnerable ships . That's why, cloaker can do same economical damage in active or inactive mode, because he is potential danger for anyone and everytime.
    No matter if the cloaker do his job in active mode,no matter if a cloaked pilot can go out from his PC 1 or 2 hours long, but 24/7 AFK ability without potential danger in "hostile" system is a bad game feature while he can make potential danger availability without play and can disturb the active players without activity.

    It's time to create counters against the cloakers (for at least against the AFK cloakers) not just boosting them with the new boosted features.
    Such a bubble resisted and covert cloaked t3 ships, range boosted BOPS fleets, new cyno module user covert cloaker ships (such a t3, blockade runners)etc.
    Nagarythe Tinurandir
    Einheit X-6
    #254 - 2013-02-01 12:10:17 UTC
    https://forums.eveonline.com/default.aspx?g=posts&t=186549 looky there for a diskussion how to deal with the local-cloaking mess.
    besides that, there a ton of other afk-cloaking threads you can rant in. no need to degrade this topic into one.

    on topic:

    i am actually quite curious how this changes turn out on TQ.
    somehow i dont think there will be an enormous increase in Black Ops Hot Drops. But it will make things much more easier for groups how already enjoy this part of eve.
    Naomi Knight
    Ministry of War
    Amarr Empire
    #255 - 2013-02-02 12:01:56 UTC
    I hope that blackops will be used on the battlefield and not just lame jumpbridgers like atm. 700-800M for a ship is huge cost when they are weaker than the 90m t1 variants with or without jumpbride.
    Strange Shadow
    Hedion University
    Amarr Empire
    #256 - 2013-02-04 08:54:36 UTC  |  Edited by: Strange Shadow
    TL; DR

    1. Eliminate instant local.
    2. Redesign D-Scan into something more usable, something that doesn't require constant clicking on small button. Proximity sensor from "The Alien" movie was excellent idea i think.
    3. Make cloak use capboosters (or nanite paste, or enriched uranium). Anything that makes your FULL cargo bay remain cloaked for 2-3 hours.
    4.?????
    5.PROFIT!

    EDIT: Everything should be done in a single move, eliminating local with current D-Scan will be total disaster for null and low sec pvp (scouts wont find enemy 2 jumps away), and even to highsec too (cant see ppl wardecced you).

    EDIT2: I for one would eliminate cyno mechanic at all, and force capitals/supers to use gates, much like orcas/freighters do now.
    Dirk Morbho
    Native Freshfood
    Minmatar Republic
    #257 - 2013-02-04 15:16:41 UTC
    Strange Shadow wrote:
    TL; DR


    3. Make cloak use capboosters (or nanite paste, or enriched uranium). Anything that makes your FULL cargo bay remain cloaked for 2-3 hours.


    make the cloak generate heat (ala overheating - but 1000x slower) and have them burn coolant.

    Travasty Space
    Pilots of Epic
    #258 - 2013-02-04 23:42:58 UTC
    Ruby, Why do you argue against yourself?
    First you argue that local is the prefect intel tool(which it isn't) and use that as the base of your argument, and then you agree that local isn't the prefect intel tool thus destroying your own argument.

    Cloaky Camping does need to be fixed as people can simply choose to AFK if the heat is on and comeback at a later time when people have cooled off.
    RubyPorto
    RubysRhymes
    #259 - 2013-02-05 02:01:29 UTC
    Travasty Space wrote:
    Ruby, Why do you argue against yourself?
    First you argue that local is the prefect intel tool(which it isn't) and use that as the base of your argument, and then you agree that local isn't the prefect intel tool thus destroying your own argument.

    Cloaky Camping does need to be fixed as people can simply choose to AFK if the heat is on and comeback at a later time when people have cooled off.


    No, I argue that Local would be a perfect Intel tool if you removed AFK cloaking.

    I can put my argument into a formal form, if you'd like.

    I define a perfect intel tool for EVE as telling you whether there is a hostile in system and whether they are active. (We are ignoring AWOXers as irrelevant to the debate on AFK cloaking)

    Here is the case IF AFK cloaking is nerfed:
    1) IF one cannot be AFK while cloaked THEN Local tells you whether there is a hostile in system and whether they are active.
    2) One Cannot be AFK while cloaked
    _______
    3) Local tells you whether there is a hostile in system and whether they are active (my definition of a perfect intel system).

    This follows the known valid logical form Modus Ponens, therefore, if you accept the premises as true (and I think they're pretty easy to accept), you must accept the conclusion as true.

    Here is the case currently:
    1) IF one cannot be AFK while cloaked THEN Local tells you whether there is a hostile in system and whether they are active.
    2) It is Not True that One Cannot be AFK while cloaked
    _______
    3) It is Not True that Local tells you whether there is a hostile in system and whether they are active (my definition of a perfect intel system).

    This follows the known valid logical form Modus Tollens, therefore, if you accept the premises as true (and, again, I think they're pretty easy to accept), you must accept the conclusion as true.

    If you'd like to argue that one of my premises is false, you feel free.

    "It's easy to speak for the silent majority. They rarely object to what you put into their mouths." -Abrazzar "the risk of having your day ruined by other people is the cornerstone with which EVE was built" -CCP Solomon

    Travasty Space
    Pilots of Epic
    #260 - 2013-02-05 02:20:37 UTC
    RubyPorto wrote:
    Travasty Space wrote:
    Ruby, Why do you argue against yourself?
    First you argue that local is the prefect intel tool(which it isn't) and use that as the base of your argument, and then you agree that local isn't the prefect intel tool thus destroying your own argument.

    Cloaky Camping does need to be fixed as people can simply choose to AFK if the heat is on and comeback at a later time when people have cooled off.


    No, I argue that Local would be a perfect Intel tool if you removed AFK cloaking.

    I can put my argument into a formal form, if you'd like.

    I define a perfect intel tool for EVE as telling you whether there is a hostile in system and whether they are active. (We are ignoring AWOXers as irrelevant to the debate on AFK cloaking)

    Here is the case IF AFK cloaking is nerfed:
    1) IF one cannot be AFK while cloaked THEN Local tells you whether there is a hostile in system and whether they are active.
    2) One Cannot be AFK while cloaked
    _______
    3) Local tells you whether there is a hostile in system and whether they are active (my definition of a perfect intel system).

    This follows the known valid logical form Modus Ponens, therefore, if you accept the premises as true (and I think they're pretty easy to accept), you must accept the conclusion as true.

    Here is the case currently:
    1) IF one cannot be AFK while cloaked THEN Local tells you whether there is a hostile in system and whether they are active.
    2) It is Not True that One Cannot be AFK while cloaked
    _______
    3) It is Not True that Local tells you whether there is a hostile in system and whether they are active (my definition of a perfect intel system).

    This follows the known valid logical form Modus Tollens, therefore, if you accept the premises as true (and, again, I think they're pretty easy to accept), you must accept the conclusion as true.

    If you'd like to argue that one of my premises is false, you feel free.


    Local doesn't tell you if someone is cloaked or not, this disproves both. Your argument is that D-scan is a perfect intel tool not local.