# Local Comms Blackout - Discussion Thread - Part Deux! **URL:** \ **Category:** Announcements\ **Tags:** feedback, official\ **Created:** [July 18, 2019, 7:57pm UTC](https://forums.eveonline.com/t/local-comms-blackout-discussion-thread-part-deux/176410 "2019-07-18T19:57:00Z")\ **Posts on this page:** 1\ **Showing post:** 1601
**Author:** ![Marcus\_Gideon](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/marcus_gideon/32/141713_2.png) [@Marcus\_Gideon](https://forums.eveonline.com/u/Marcus_Gideon)\ **Post date:** [July 31, 2019, 10:02pm UTC](https://forums.eveonline.com/t/local-comms-blackout-discussion-thread-part-deux/176410/1601 "2019-07-31T22:02:56Z")
> [@A couple of questions related to Blackout](https://forums.eveonline.com/t/a-couple-of-questions-related-to-blackout/179387/1): > > 1. Do you regard hammering of the D-Scan button every couple of seconds(for half an hour or longer) good/enjoyable gameplay? Let’s assume no rule-breaking automation is involved. > 2. The argument against automatic D-Scan for everyone was always that it will kill the servers. But when everybody has to spam it anyways, what’s the point about it staying manual? The point is that Intel / Self Defense should not be free, or automatic. You should actively work to keep yourself safe. Which is why you need to actively maintain watch on your Dscan. If you forget, and the service is not automated, then your forgetfulness could cost you. > [@](#): > > 1. If no local is so awesome, why aren’t there more people in wormhole space? At least not in the lower class ones with exits to high and low sec? There are plenty of people living, or at least operating, in WHs. The difference is that you cannot claim Sov in WHs. And you cannot use most of the Null sec mechanics (such as Cynos) in WHs. > [@](#): > > 1. With the Blockout now running, do you consider cloaky ships balanced in terms of somewhat even chances between the hunter and the hunted? Let’s assume same ships size/class. Everyone, and I do mean EVERYONE, always whines and cries about how Cloaking needs rebalanced. Forgetting all the while, that Cloaking IS a balance mechanic. Every game has Rogues. Every game has Spies. But it’s impossible to spy on enemy movements, on enemy bases, unless you can Cloak. And you need to do so for hours at a time, b/c not everything in Eve happens in seconds or minutes. So yes, Cloaking is still perfectly balanced. They still have to decloak to act in any meaningful way, other than just watching and reporting. And they cannot act immediately after decloaking, because most ships require a recalibration time after dropping cloak. The ONLY change that Blackout has on Cloaking, is that now you don’t get to know if there’s someone out there spying on you. So now you have to actively defend your space against spies. (See #1-2) > [@](#): > > 1. Do you consider pay EvE “pay to win”? What about a player with a single account in a single ship having to fight off another, but with 5+ accounts and as many ships. Let’s say 1 “dps” ships vs 3 (potentially cloaky) dps ships with 1 logi and 1 ewar. Not pay to win? And if you bring 3-4 buddies with as many ships, but the multi-account guy also has his 3-4 buddies with 5 ships each, still not pay to win? Absolutely! Ever since they started allowing Cash → PLEX → ISK, and further ruined things with Skill Injectors, this game is most definitely Pay 2 Win. Anyone with money to spare can shake their credit card vigorously at CCP, and start flying any ship they want that same day. And where it used to be an issue of Noobs training to sit in a ship, but not having time to train for properly operating the ship, they can Inject themselves straight to Mastery 5 if they want. BTW, “potentially cloaky” is irrelevant. There’s no difference between getting into a fight, and having more foes decloak, or having more foes warp in from somewhere. People need to stop blaming Cloaks for a situation going pear shaped. =) --- _[View the full topic](https://forums.eveonline.com/t/local-comms-blackout-discussion-thread-part-deux/176410)._