Player Features and Ideas Discussion

One entosis link per ship. It's the second point of the restrictions.

That's a pretty nice set of changes, and neatly deals with a lot of the issues raised in the previous two threads.

The mass increase in particular was very slick in terms of limiting max speed of long range / kiting doctrines while not arbitrarily making them utterly infeasible. Keeping T1 links viable on Interceptors is a good choice, though I feel that limiting them to 30km range might be too much. 50km for the T1 links would open a lot more options for small ship doctrines, as controlling a 30km sphere is child's play in brawling frigates even against kiting frigate comps. 50-60km forces brawling frigate comps to make different choices to ensure they've got enough of an engagement envelope to counter kiting comps.

Stats on the T2 / Large (+1 on the idea to rename them) seem good, the cap use / grid of the T2/ Large should force folks who want to use them on small ships to make significant sacrifices to do so, which is good.

I don't see the point of using Stront to fuel these, especially at these low levels. Resupply is trivial for anyone with half a brain, even small ships can run these for hours. As other posters have said, it adds no interesting gameplay. It seems like the stat chlarifications - particularly for the T2/Large Entosis Link - force enough fitting sacrifice that a fuel requirement isn't really needed. Either make the fuel use high enough to impose a significant logistic burden - which gives the advantage to larger / more organized groups - or remove it entirely IMO.

I missed that.

Head>desk.

From the last thread and if my memory serves, it will remain at this value (i.e. vulnerable) until flipped or fully controlled and this vulnerability will continue PAST the window.

What about size and tech differences? There's enough new stats to add some extra trade-offs.

Small Entosis Link I:

• Requires Infomorph Psychology 1
• +250,000 mass when online
• 5 Minute Cycle Time, 25km range
• 10 PWG, 1 CPU
• 50 Capacitor per cycle
• Consumes 10 Stront per cycle
• Cost ~20m

Small Entosis Link II:

• Requires Infomorph Psychology 4
• +225,000 mass when online
• 5 Minute Cycle Time, 35km range
• 12 PWG, 1 CPU
• 45 Capacitor per cycle
• Consumes 8 Stront per cycle
• Cost ~50m

Standard Entosis Link I:

• Requires Infomorph Psychology 2
• +1,000,000 mass when online
• 2 Minute Cycle Time, 200km range
• 100 PWG, 10 CPU
• 500 Capacitor per cycle
• Consumes 4 Stront per cycle
• Cost ~80m

Standard Entosis Link II:

• Requires Infomorph Psychology 4
• +900,000 mass when online
• 2 Minute Cycle Time, 250km range
• 120 PWG, 10 CPU
• 450 Capacitor per cycle
• Consumes 3 Stront per cycle
• Cost ~120m

INB4 100pwg 10km/s 250km lock range interceptor with enough cap to run the module is impossible. The mass addition alone was the perfect solution.

There's nothing stopping attackers from running multiple Entosis Links on a structure, or using remote ECCM to make them nearly impossible to jam. Plus the defender has to actually control the grid enough to tick the timer back down or the defense never ends.

Also you could always use a Triaged Carrier with their EWar immunity to completely bypass cheap ECM spam entirely. Of course then you also can't just use a Triaged Carrier and nothing else because the defenders can then just park a single Drake with a link on the structure and completely halt your Cap progress.



and a few more:

• Do the nodes allow anchoring deployables in their vicinity?
• Will the nodes have a decloaking sphere around them?

[/quote]

• What do you mean by Deadspace? They're not gated, if that's what you're asking.
• It's not first to 10 nodes it's 10 net node points. Meaning if you can get 10 more than your opponent you win, but if you get 10 and your opponent got 5 you still need 5 more.
• Yes, but they count as an attacker and they can't actually take Sov, and IIRC from the previous thread they can't use them on nodes for the actual capture event.
• Yes, but no progress is made.
• Hasn't been specified yet
• I would assume so.
• I would assume not, since the Entosis Link cycle prevents cloaking, so there's no need to stop someone from being cloaked next to the node since they can't impact anything while cloaked.

I don't think it's mean to be a major requirement here. Keep in mind this is something that's meant to go on for at least an hour in a well defended system, and every ship starting a link needs one cycle of warmup. For a completely uncontested Node event with full occupancy metrics that's a minimum of 210 Strong using a 'T2' Link.

Also since the event is going to go on for a long time ships are likely to need a lot of ammo in addition to whatever stront they use to capture. If the fuel requirement is pushed too high it goes from being a minor consideration in a long fight to a major hassle to deal with, and makes Amarr ships (with their lack of ammo requirements) the default capture boats since they'd be the only ones able to hold enough Strontium to run a full capture.



Read the original blog post, most of this is answered there. The only thing that isn't is the structure related stuff, because that falls under the Structure revamp.

Capitals don't take 5 times as long, they just cycle for five times as long. It's not number of cycles it's time spent cycling. So a Carrier with a t2 will have a 10 minute warm-up cycle and then takes the same amount of actual time to perform a capture as any other ship, it just does it in 'fewer cycles' but as a result is also vulnerable for longer.

The defender doesn't need to run their links as long as the attacker. Check the blog post for timer mechanics.

Nah it's sorta ok you're not grinding through EHP but EntosisHitPoints

I'm glad to see you've decided to ignore whatever idiot came up with this line.