Player Features and Ideas Discussion

You're gonna hate me for this, but I still wanna propose it. :)

Suggestion: Make capconsumption of a module set to null when they have reached 100%.

As in; Ab's, Mwd's, reppers, shield modules and so forth, can be applied immediately after de-cloak/de-warp and just sit there, burning with no capconsumption until NEEDED. - As in, a repper, will be active, but at 100% armor/shields/hull, they will still continue their cycles, but cost no caps. Same for propmods, while you sit idle, they won't cost caps, and if you fly at 50% speed, they will only cost 50% cap.

That's it.

Rip it.

Dantes

Most of those are actually impossible to do, and that's on top of that being a dumb idea.

Uh how? All you need to do is set a relationship based on the percentage of the value you're influencing and then attribute that to capacitor consumption. You could also time it to what you're using and when, so eg a MWD will use an increasing amount to its total capacitor usage per cycle based on the percentage of velocity you're currently at to top speed within the cycle.

It's not about 'micromanagement' or 'dumbing' down.

You could limit the module usage to being used after it's needed for repair devices or propulsion mods (can't be activated until you need it, deactivates it when you don't). This really changes when you need to interact. Mining already does this, so why is it limited to mining?

Cap is drawn at the start of cycle, boosters are the only untargeted mod that draw cap when they do their thing. Actually check how fast a prop mod makes you go when you're orbiting something, and that's ignoring their start up which is basically a huge amount of free cap with this proposal. So yes, it is dumb.

So you are sat in a non cap-stable ship with everthing fired up. Somebody jumps you and you engage. How would the server know which mods should run and which not when you open fire, maneuvre and start taking hits at the same time? And if the first active cycle doesn't wipe out your cap something will shut down in the next cycle but which one?

Assuming that for armour reps you mean that it won't be drawing cap until you take armour damage means you either get a free shorter first cycle based on where the cycle is (potentially almost instant if really lucky). If you don't get the benefit until a full cycleruns then you could potnetially have to wait two cycles for it to kick in.

I can't see any way this would work sensibly without removing a chunk of actual player skills.

did you read what i said?

where did i argue that i should be able to activate and forget a prop mod or repper?
How does it take more skill when a prop mod is activate and forget?

Prop Mods also affect acceleration, not just top speed. As well as agility and a few other things.
Reps problem has already been identified. etc

So..... my vote goes for a flat no on this also as a general thing

For specific modules I could see this to some extent.
Example being the RAH. It has a base cost + an extra cost for adapting (which matches current cost when added)
So if it isn't adapting you only pay the base cost.
TSB where it costs a little cap per cycle and more on the cycles it breaks locks. (meaning less cap than now if it doesn't break locks)


But those are modules where it has a 'dual' function so to speak where at a basic level it does something but sometimes does a secondary effect.

A lot of EvE gameplay can be passive. Paying attention should be rewarded. So -1

How should the server decide, if you need your armor repairer at 0, 27 or 63% of armor damage...?
fit a passive shield fit or an armor buffer fitting and become happy :)

yeah there is no way to tell the system if you are idle or not, you cant base the whole thing on velocity because in large fleet fights and missions there isn't a lot of movement on larger ships so your tank would be turned off or operate at a percentage which is ********.