Player Features and Ideas Discussion

its shockingly funny to watch all of you running around worrying about frigates.


it clearly shows how incapable you are of understanding the very simple layout of these sov mechanics.

But frigates are indestructible! What can you do against them? /sarcasm off

But I mean....You start using the link from a position, you can not deviate more then 90 degrees or a certain verible from the start position or the link breaks....would this alleviate any of the trolling concerns at all? Considering people are worried about users trolling by orbiting at 100+km with a small sig moving at 7km a sec... Not just one guy, but like a fleet of 40+ inty or something in orbit doing a troll circle....If they had to stay within 90 degrees of the start position relative to the structure(you may be able to track them at some point if they make a mistake in their spiral with a couple long range defenders/trolling requires piloting skill etc).

Numerous counters exist,. If the almighty goons are afraid of a few trollceptors......you have concerns about being able to defend your renters. Boo frickin hoo. I wonder how all the FW folks deal with the ALMIGHTY ceptor.

hrm yes i need to assert my superiority over eveo but i can't be too committal, yeah, let's post a nice vague, unsubstantiated thing

mmm there it is

Renters huh.... hmm

Moa might end our 0.0 -renter- dream, then

So we're supposed to pretend that the gate is an ihub and the 27 people are sovlasering it...?

Based on the goals stated, I'm struggling to figure out why this isn't a new-style deployable.

Give it reasonably high EHP/omni resists along the lines of an MTU. Give it a TINY sig rad to make it hard to bomb and slow for sniper fleets to lock w/o significant sebo. Make it 50 to 100m3 in cargo volume. Make it vulnerable to ECM (though omni only; eg omni strengths that must ALL be 0 before jammed) so that it pauses cycling while jammed. Make it impossible to rescoop until a cycle completes successfully (eg destruction or win, no ability to scoop and run to save the deployable just because it hasn't finished/is contested/paused).

EDIT: A few other mechanics tweaks from replies; possibly make the cycle pause when the deployable is taking ANY damage. Possibly allow the cycle to be paused by neuting as well as ECM. Probably limit it so that a single pilot can only deploy ONE of these at a time, and must wait until her deployable is destroyed or re-scooped (after a completed/successful cycle) before able to deploy another one. Definitely generate KMs when these are destroyed, just like MTUs. Probably give them a maximum lifetime (2hrs or so) before they self-destruct.

Grid control? Check; virtually impossible to keep alive a deployable w/o grid control.

Troll-y? Not really... frigates can only carry a few without resupply. This allows legitimate use in fastfrigs/intys to contest abandoned sov, but makes it much tougher to troll entire regions (since they can't rescoop deployed units unless/until they cycle completely).

Occupancy? This makes it even easier for defenders to "prove" occupancy. Any ship that can control grid/apply DPS can destroy a troll deployable, without requiring a defensive e-link of their own. That said, the behavior that deadlocks control when more than one alliance's e-links are deployed should remain. Multiple can be deployed; only question is whether a single pilot should be able to deploy more than one at a time. EDIT: the fact you get a KM is also much better concrete proof that you actively defended sov vs. "I activated my defensive e-link until he ran away, I swear"

Defensible? With a good mix of EHP and sig, should be possible to tweak to a point where sniper/bomber attacks are not effective enough without grid control to pop it before it cycles successfully. Also, true null grid control against sniper/bomber is required (eg proper use of defensive bubbles).

EDIT: Among other things, this also really simplifies the timers, info about who is doing what, etc. The initial/warm-up cycle time is the time it takes to anchor the deployable. This would be the initial 2 or 5-minute timer. Once anchored, it sends out the alliance notification and immediately begins the 10 to 40 min long capture cycle, which can be very prominently displayed in space on the deployable's brackets, and makes it immediately clear to anyone with a decent overview what is doing the capturing (no need for magic ship special effects to figure out what is going on). Also allows defenders to intelligently pop the deployables that are furthest along in their capture cycle.

Some quickly made images to illustrate this concept:

The actual angles could be different, this one assumes you pass 90 degrees from the start point in relation to the structure which would deactivate the link.

2 IMAGES:

http://i.imgur.com/2A90q5S.jpg

http://i.imgur.com/Ndgfimz.jpg

There would be a plane you can not pass or the link will be broken.

An interesting idea...

Defenders must shoot the structure deployable. This is of course different from the SBU, as it has to be dealt with immediately (it will reinforce the thing, unlike SBU where the attackers must come back and still structure grind).

Too bad it will probably be buried, but a nice suggestion


EDIT: I'm serious, it is actually an interesting idea. Definitely better than the drop SBU -> Wait 3 hours -> Structure shoot thing.