Player Features and Ideas Discussion

Adding shortcuts to ONLY activate or deactivate modules.

For weapons, it is not actually too much of using same shortcut to activate or deactivate a module, since they are mostly fast cicle and actually work while deactivating and readly activate upon ending the cicle, so if you deactivate it by accident, you reactivate it and dont lose much. Still lose, but it is not critical.

For functional and defensive modules however, the inhenerent common keyboard rate of repeat, and the precision needed in timing to not deactivate a module when retrying to activate it is too high, creating an effective difference on the margin of error handling in attacking and defending.

Due to the ever present delay between what you command, what you see and what the server process, sometimes the milisecond which takes to see if you activated a module and respond in stress to its lack of activation increases the rate of mistakes that you are subject while defending even lower than when you are attacking.

I said distinct shortcuts, as in the shortcuts setup in the options window, for a shortcut to activate and another one to deactivate. There is a way to do it already in place, but it is a contra-producent one.

If there were no reason to have it, there were no reason to have another way to do it. Simple as that.

The reason it could be more accessible I listed in the opening post so it is just to read it.

What I am saying is just instead of making the use of hold, it could just make 3 shortcuts for modules. But for a person who does not use functional modules and just play eve for a space shooter, there is no reason, and that is why many people doesnt really know that you can have a way to use the keyboard in a manner to not "spam" the command.

There is no use.

I sense a heavy button spam user.....


If something tied to say f6 is not instantaneous....they press the button at a rate that would have a pro competition FPS player going damn, that some impressive APM (actions per minute) you got going on their. So the are turning it on/off constantly.

Pressing the button once and waiting for server to catch up really the fix here. Same key press that starts a process also being the one that stops is kind of a universal programming thing. Well short of old faithful break keys like control c. But control C kind of a sledgehammer....kills the whole thing lol.


Its the curse of gui really. Only command line stuff gives you any validation once you press that button the computer says I got this. Some Linux command I run spit out output in no time at all. Other commands, especially if they call up script files or take in input files....I get very clear signs its thinking and get the less than subtle hints to just let her do her thing really. Subtle hint is no command prompt with system/user and blinky cursor letting me type lol.