More actions
No edit summary |
|||
| Line 46: | Line 46: | ||
The third thing is that negative and positive effects are stacking-penalized separately. So, one +% and one -% effect to an attribute suffers no penalties, whereas with two +% and two -% effects, one of each would only be 86.9% effective. This situation doesn't generally come up in practice though, since if you're fitting modules that both add to and detract from the same stat on your ship, you're probably doing it wrong. | The third thing is that negative and positive effects are stacking-penalized separately. So, one +% and one -% effect to an attribute suffers no penalties, whereas with two +% and two -% effects, one of each would only be 86.9% effective. This situation doesn't generally come up in practice though, since if you're fitting modules that both add to and detract from the same stat on your ship, you're probably doing it wrong. | ||
It can be hard to tell exactly what suffers stacking penalties and what does not. For instance, the Overdrive Injector System II gives +12.5% velocity at a cost of -20% cargo capacity, and the description claims it suffers stacking penalties. The velocity bonus is stacking-penalized, but the cargo drawback is actually ''not''. Similarly, the Warp Core Stabilizer II gives you one extra warp core strength at a cost of -40% targeting range and -40% scan resolution. It doesn't mention stacking penalty in the description, but the drawbacks ''are'' actually stacking-penalized.<br> | It can be hard to tell exactly what suffers stacking penalties and what does not. For instance, the [http://wiki.eveonline.com/en/wiki/Overdrive_Injector_System_II Overdrive Injector System II] gives +12.5% velocity at a cost of -20% cargo capacity, and the description claims it suffers stacking penalties. The velocity bonus is stacking-penalized, but the cargo drawback is actually ''not''. Similarly, the [http://wiki.eveonline.com/en/wiki/Warp_Core_Stabilizer_II Warp Core Stabilizer II] gives you one extra warp core strength at a cost of -40% targeting range and -40% scan resolution. It doesn't mention stacking penalty in the description, but the drawbacks ''are'' actually stacking-penalized.<br> | ||
We can learn from this that it is not the module itself which determines whether its effects are stacking-penalized, but rather the attribute affected.<br> | We can learn from this that it is not the module itself which determines whether its effects are stacking-penalized, but rather the attribute affected.<br> | ||