Player Features and Ideas Discussion

Will you also create a ship that can track a ceptor moving at 4000 m/s ?
Cause that was your policy right ? Having a counter to everything ?

This change solves nothing.

Yes, in case you can make it to the attacker alive thru places like X-7O in a ship with 0 tank.

A swing and a miss indeed!

Sov requires that you put some skin in the game. Let's review what it took to take sov away from someone through the ages of eve.

***

Iteration 1: Tower Sov

Implementation: You had to have a higher percentage of moons towered in the system than anyone else to hold sov.

What did it take to capture: A fleet of battleships or dreads to go through each moon to strip/reinforce each tower. You couldn't do it with frigates as the tower would shred you.

Value at Risk: Billions

***

Iteration 2: Dominion Sov

Implementation: You need a TCU anchored and online in the system.

What did it take to capture: 51% of the gates in had to have a Sovereignty Blockade Units on them in order to make the system vulnerable and then you had to field enough DPS to take the structures down..

***

Iteration 3: Aegis/Fozzie Sov

Implementation: TCU anchored and online in the system.

What does it take to capture: An interceptor with an entosis link.

***

Now do we see a problem here? You've gone the route of World Of Warcraft by slowly pandering to the lowest common denominator. You see smug bullsh*t like https://eveskunk.com/e/353067497 where the sole goal is to troll sov and create nodes with no intention of capture. (Yes I am calling MOA lowest common denominator)

Recommendation: Entosis Link fits on Cruiser or larger hull only. Like a cyno, it restricts your movement. You've stated yourself.

Drastically reduced time of uncontested sov capture - CCP Fozzie

Yes, in case you can make it to the attacker alive thru places like X-7O in a ship with 0 tank.

Surely the real problem is that Interceptors should never have been given interdiction nullification in the first place. This was a huge mistake and should be rolled back yesterday.

Interceptors online needs to go away.

Hey everyone. With vacation season winding down here in Iceland, we're fast approaching the first release since the Aegis Sovereignty deployment: Galatea on August 25th.

Galatea will contain the first (and definitely not the last) set of updates to the sov capture system released in Aegis, thanks in large part to your excellent feedback and observations we've made of the first few weeks of the new system on Tranquility. This first set of adjustments is focused on the capture times and maximum number of Command Nodes, as well as some tweaks to the Entosis Link penalties itself.

The first and most significant change in this release is that we are reducing the base capture time of Structure Command Nodes from 10 minutes to 4 minutes, and Station Services from 5 minutes to 4 minutes. This means the capture times for these structures will range from a minimum of 4 minutes (for defenders and when the multiplier is at its base of 1) to a maximum of 24 minutes (for attackers against a 6x multiplier structure). This change only applies to Command Nodes and Station Services, NOT to the initial reinforcement of a sov structure (which keep their current base capture time of 10 minutes).

To help ensure that defenders maintain a robust but fair advantage, we are also starting the defending alliance off with 60% control in the overall event tug of war when nodes start spawning. This means that an uncontested defense will now require capture of 8 nodes at 4 minutes (plus warmup) a piece, down from 10x10 before. In total, the fastest possible defense would require 4 players and 12 minutes post-Galatea, compared to 5 players and 24 minutes pre-Galatea.

To help reduce the clutter that builds up in lower value systems when capture events are left for extended periods of time uncontested, we are also reducing the cap on total nodes that can spawn per structure from 20 to 10. We are also reducing the spawn rate of randomly appearing extra nodes by approximately 50% (this second part only applies to the randomly spawning extra nodes, not the the nodes that spawn instantly when old ones are completed).

We are also making an adjustment to the penalties on the Entosis Link module itself. The mass penalty is being replaced with a "speed limit" to 4000m/s. This means that the normal subwarp engines of a ship with an Entosis Link fitted will never accelerate it past 4000m/s. This limit was chosen to have the smallest possible impact on ships fit for engagement and combat while having a larger impact on the escapability of evasion fits than the mass penalty.

We are also releasing the first batch of Sov UI little things, which CCP Punkturis and CCP Sharq sourced from your feedback in this thread. These changes include an overview of sov data in the constellation show-info window, direct access to the default vulnerability timer and a new region column in the sov dashboard and improved tooltips in the infrastructure hub UI. Punkturis is continuing to work on improving the sov UI and we encourage people to keep posting their requests in the little things thread.

Finally this release also contains a number of bug fixes, some of which are quite visible (Alliance logos once again appearing in space on the TCU) and others which improve handling of rare edge cases (such as alliances disbanding mid-fight) and back-end code.

The Galatea is just the beginning of our commitment to iterating and improving nullsec and sov. We are hard at work on the changing coming in future releases, including formal methods for dropping sov, the ability to turn IHub upgrades on and off, updates to the formula for calculating activity defense multipliers, new PVE experiences for sov nullsec and much more. Nullsec and Sov remain our focus here at Team Five 0 and we'll be continuing to update you on progress as we go forward. We are listening to your feedback and continuing to observe the results of our changes as we make them.

These Galatea changes will also obviously not be the final changes to the capture mechanics themselves. We have some changes we know we want to make (like partially captured structures returning to defender control at a slow constant regeneration pace to reduce the need for "maintenance linking") and others that we don't want to rule out but that also need more investigation and internal/external discussion before making final decisions (such as ship restrictions on Entosis Links). Thanks to everyone who's been providing constructive feedback so far, we hope you'll continue.

Thanks everyone, and good hunting!

An Atron with a single overdrive can break 4km/s, and catch troll ceptors now.

You can just burn away as soon as someone comes in local to defend. No risk for attacker at all

but I've scoured 25 systems and not red/neut to be found.

I wasn't aware you LIVED in a system whilst NOT being there. That's some impressive shitposting right there.

There is no risk for an attacker if no-one is there. WORKING AS INTENDED.