Upcoming Feature and Change Feedback Center

... yeah that was kinda the point

sooo to ignore this i just repack the ship right?


or if you some how make it so i can't do that then i just use another ship i already had stored in the area

use ascendance plants and the warp speed lows

w/o the omaga and using 3 of the mid line accelerators you warp over 3 au/s how much faster do you want to go lol

The second ship wasn't that good of a point but can you please answer the repackaging point since attributes on ships are lost when a ship is packaged.

You have many "damaged" ships that will "repair" over time. You don't have to do it this way, you can just jump normally. It's an option for fast tavel at a price. You can just skip it if you have the time to wait for the timer to run down. And if not you might have a very good reason to just take the damage and still get out on top. If you want to relocate to some System far away it might be worth it to just take the damage and park the cap for a week then crawling through New Eden and risking it all the time. Or you REALLY need this cap somewhere to fight NOW even if it's not in top condition it still might make the day.

A fatigue system that is "ship" focused rather than player would open the game up and allow players to actually play the game instead of worrying about too much fatigue.

Move a Dread X distance (say for advance staging or just moving to a new system) then jump into a Blops, your not going to be very efficient when comes time to use it.

But;
If fatigue were applied to the ship class, you would still be able to use blops (and accrue more fatigue) but your Dread is stuck where it is until the related fatigue is gone.
Same for jump bridges, have fatigue on blops or a capital ship, you can still use bridges (play the game) and gain fatigue.

Fatigue could be broken up into classes, similar to what it is now but "ship class" specific, allowing those who need to travel reasonable distances in different ships to do so. Max out fatigue on capital ships, you can still use Blops and or bridges, at least until you also max those out if your actively playing the game.

My JF pilot also flies dreads, carriers and blops. Only problem is, I can't use any of those if I plan on using my JF, I can't use a bridge to get to a fight, I can't use my blops (even with the reduction in fatigue) and I certainly can't use another capital ship.
So I have this nice (88 mil SP) capital focused character that can only fly one ship, without being punished for playing the game.



Frosty - Repackaging works for moving to a new place (rigs are cheap), only if you have JF pilots willing to do nothing else.

Ocker, I think your idea is innovative, but it ultimately futher complicates a complicated and unintuitive system. I think what we need is a system that limits the movement of giant capital blobs in a more natural and intuitive way. Before, I suggested making it take time for ships to go through a cyno based off of their mass, and while I still personally like it, it met some resistance, so I'm going to take a slightly different approach and see what people think:

1: Give cynos mass limits, like wormholes.

2. Give cynos a warm up period, say 60 seconds, where nothing can go through.

3. Don't allow a cyno to be lit any closer than x distance from another cyno (my gut feeling is 100km).

4. Turn the entire jump fatigue mechanic into a simple timer, maybe 5-10 mintues or so.

This way,

1. Hotdrops are nerfed to encourage actual fights and not just ganks.

2. Moving small amounts of capitals will be relatively easy, and they can move as one coherent fleet.

3. Moving large amounts of capitals will be harder. You will be forced to break up your fleet either by time, by massing out cyno a single cyno and then lighting another one in the same spot, waiting a minute and continuing, or distance, by having fast ships go through to cyno, burn 100km away and light another cyno.

I agree that intel is too readily available. I would like to see local nerfed in some manner. Maybe only ships going through gates or undocking from stations are tracked in local, and only for a certain period of time before you disappear, because who knows, you might have jump-drived out, or logged, or went through a wormhole.

When it comes to a cyno delay, I think the number could be worked. Maybe 60 seconds is too long, though I think you badly underestimate the tanking potential of recons. I know that over 70k EHP is possible with double web, scram, NOS and cyno using nothing fancier than heat (which will last for more than 60 seconds), and we're not even talking about a T3 cruiser. A delay would give the defensive ship a chance to try to burn out of scram range, kill the cyno, or nuet it/jam it and warp out. It also gives the offensive players a chance to counter these things, with EWAR or counter-nuets or whatever. Hotdrops could actually potentially turn into fights. Right now, they almost never turn into fights.

.... you think 70kehp is going to last 60s?????

lets pretend they can what about cov cynos with blops you need to be done and off grid generally within 45s of the cyno being lit or you're screwed.
(not to mention they don't even last long enough for your delay)

surprise is one of the main advantages of a cyno if you don't want to deal with it you can put down a jammer before the fight starts.


(i also support the idea of ships similar to HICs that can produce a local cyno inhibitor(just like a standard one no effect on cov ops cynos))