More actions
→Extra Modules for Tackling: ABs are often not fast enough |
→To fit a stasis webifier or not?: Webs beat ABs; scrams alone don't |
||
| Line 367: | Line 367: | ||
==To fit a stasis webifier or not?== | ==To fit a stasis webifier or not?== | ||
Stasis webifiers are great modules as they significantly decrease the speed of a target ship. Stasis webifiers are fairly short ranged, with a range only slightly longer than a warp scrambler. This makes fitting a stasis webifier a good decision if the tackler is already fitting a warp scrambler, since they will be operating well inside webifier range anyway. | Stasis webifiers are great modules as they significantly decrease the speed of a target ship. Stasis webifiers are fairly short ranged, with a range only slightly longer than a warp scrambler. This makes fitting a stasis webifier a good decision if the tackler is already fitting a warp scrambler, since they will be operating well inside webifier range anyway. Furthermore, if the tackler is engaging an enemy fitted with an afterburner, the warp scrambler will not be enough to hold the enemy in place, and the webifier will be required for the tackler to be able to stay in range. | ||
If the tackler is fitting a warp disruptor, the decision is slightly less clear cut. They first need to decide whether they plan to fly inside stasis webifier range; despite the fact that they have a long ranged warp disruptor, the tackler will generally be harder to hit if they orbit as close as possible, and they may want to fly inside web range anyway. If they do, fitting a stasis web makes a lot of sense. On the other hand the tackler may want to stay outside of stasis webifier range, either because they are flying a Tech 2 interceptor which will be running its microwarpdrive all the time, or because they want to avoid their target's webs and energy neutralizers. If this is the case, there's not much point fitting a stasis webifier since the tackler is unlikely to be in range to use it and they would be better off using that mid slot for a different module (for example a sensor booster to help them lock faster, or a tracking disruptor to protect their fleet-mates from the opponent's turrets). | If the tackler is fitting a warp disruptor, the decision is slightly less clear cut. They first need to decide whether they plan to fly inside stasis webifier range; despite the fact that they have a long ranged warp disruptor, the tackler will generally be harder to hit if they orbit as close as possible, and they may want to fly inside web range anyway. If they do, fitting a stasis web makes a lot of sense. On the other hand the tackler may want to stay outside of stasis webifier range, either because they are flying a Tech 2 interceptor which will be running its microwarpdrive all the time, or because they want to avoid their target's webs and energy neutralizers. If this is the case, there's not much point fitting a stasis webifier since the tackler is unlikely to be in range to use it and they would be better off using that mid slot for a different module (for example a sensor booster to help them lock faster, or a tracking disruptor to protect their fleet-mates, and themselves, from the opponent's turrets). | ||
==To fit a sensor booster or not?== | ==To fit a sensor booster or not?== | ||