# Local Comms Blackout - Discussion Thread - Part Deux! **URL:** \ **Category:** Announcements\ **Tags:** official, feedback\ **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:** 3897
**Author:** ![Arrendis](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/arrendis/32/432594_2.png) [@Arrendis](https://forums.eveonline.com/u/Arrendis)\ **Post date:** [September 16, 2019, 6:33pm UTC](https://forums.eveonline.com/t/local-comms-blackout-discussion-thread-part-deux/176410/3897 "2019-09-16T18:33:25Z")
> [@Archer\_en\_Tilavine](#): > > If the nullsec blackout won’t come back for all of nullsec, perhaps it could come back for some of nullsec by breaking nullsec down into upper nullsec and lower nullsec, where only lower nullsec is blacked out. Just like empire space is broken down into hisec 1.0 - .5 and lowsec .4 - .1, nullsec could be broken down upper nullsec 0.0 through -.5 and lower nullsec -.6 through -1.0. > > Another way the blackout could come back: Just like there might be system wide cyno jammers in effect, there could be a system-wide blackout mechanism. Of the two, the second is the better idea. Not because it preserves local, but because it’s _active_. It will always be better to set up things so ‘players want X, they do Y’, rather than just ‘X is how it is’. For example: players want the best ratting or mining anomalies, they have to invest in an IHUB upgrade.[1] It also opens up counter-play options. Let’s turn it around: Assume Blackout is the ‘default’ condition of null[2]. CONCORD doesn’t provide those services there. But players can put down a structure, or a service module in an existing class of structure, that provides it. Other players then get a few options: blow up the structure. Maybe _hack_ the structure, either with an entosis link or some other module designed to bring the hacking mini-game into more prominence[3]. Basic success: you shut down local. Basic failure: you don’t. Critical success: you get the option to just make _you_, or your group, not show on local in that system for 30m, or an hour, or something. You still get all the perks of local, but nobody sees you coming/going in that system. Critical failure: you shut off local… for _you_. You won’t even know you failed. It’ll look like success, after all. Active gameplay offers counterplay. The biggest problem w/cloaks right now is: there’s no counterplay. Sure, you can decloak someone… if you can get inside 2km of their ship. But if you weren’t there when they cloaked? Perfect stealth, uncounterable. We lack things like active sonar, or other tools to (even briefly) expose cloakers. * * * 1 This is not saying players _having_ the best anomalies is necessarily a good idea, only that it’s better to make them _do_ something to get them, rather than just giving those anoms to them. 2 Go farther: gates function, because they’re paired, but without the Communications Arrays (or whatever), _the fluid routers don’t work_. What does that do? - No chat channels at all. Maybe preserve fleet chat for ships on-grid, but not beyond that, because there’s no FTL communications. - No cloning. The same QE He-4 used for Local is used to transmit your head to your next clone. Jumpclones would only work within the same structure, and if you die… looks like it’s time to go back to ‘did I update my clone?’ in Nullsec. 3 Really, hacking has _so much_ potential in an environment where everything’s controlled by computers. Hack ACLs. Get yourself temporary docking rights in enemy citadels. Be really baller and turn off _tethering_. Get access to jump gates, or bypass the toll. --- _[View the full topic](https://forums.eveonline.com/t/local-comms-blackout-discussion-thread-part-deux/176410)._