NotFred
   |
Posted - 2009.05.14 17:13:00 -
[1]
Edited by: NotFred on 14/05/2009 17:14:07
<Obligator bit about how bad the changes to cloaks are omitted, thatÆs been done to death already and acknowledged by CCP, I wont bore people with it again>
<Remaining worry>
What does worry me though is how these changes were ever allowed to go live in the first place.
For two or three days before the patch was even announced there was a nine page thread in the game dev forum full of people begging CCP not to let the changes on the test server go live. There was then further uproar in that forum, and in a few others, when the patch notes were announced.
Why was it only once the patch went live that CCP took notice? The information about the unintended consequences of this change was there, but either not read or not acted upon. To me this seems to negate the point of the game development forum and the test server in the first placeà
<more constructive bit follows:>
The obvious aim of these changes is to stop ECM ships from continuing to jam whilst cloaked. This needs to be implemented in a way that allows other modules to continue however (MWD etc).
Some people have suggested only cutting modules that target other ships. However, IÆm not sure how easy this is for CCP to code (depends how the existing code is setup to allow differentiation between targeted and untargeted modules), and as someone pointed out it would allow a pilot, if a jam cycle fails, to cloak-uncloak and immediately attempt to jam again.
To my eyes, a better solution would be this: A targeted module can only affect a ship whilst that ship is still targeted (At present if you unlock a target, or cloak, you still finish the modules cycle, it just fails to reactivate).
Result:
Modules that do not require a target lock are unaffected.
ECM modules (and any others that affect another ship during the cycle, remote reps?) stop as soon as the ship cloaks (or is jammed, or unlocks that target).
Attempting to cloak-uncloak to retry a failed jam cycle does nto work. You lose target lock but the module is still cycling, so you still have to wait out its cycle before you can activate again.
Not sure how easy that would be to do, but it seems to me like it would do the job very nicelyà
<comedy bit>
 Originally by: CCP Chronotis
This started out life as a minor defect where a code fix was made to stop the ECM jamming continuing to work after you had cloaked.
Soà despite the patch notesà you are in fact saying this is all BECAUSE OF FALCON? 
|