Interdiction is a word that gets used loosely. In VYPR’s context, it means one thing: stopping a specific ship from continuing on its current course, by force if necessary, for an operationally justified reason.
That justification matters. We are not pirates. Interdiction in VYPR operations is deployed against confirmed threats — hostile actors targeting our clients, ships running contraband through a secured zone, or targets designated under a specific contract. It is not a tool for harassing neutral traffic.
The mechanics are what most people think of: quantum interdiction devices, positioning, forcing a target out of jump. But the mechanics are the easy part. The harder part is what comes next.
Once you have interdicted a target, you have committed to an engagement that you now need to control. You need enough firepower to handle what you stopped. You need comms capability to issue instructions or negotiate. You need a decision framework for what you are going to do with this ship and this crew.
Half-executed interdictions — where someone yanks a ship out of QT and then cannot finish the job — are worse than not attempting it. They alert the target, compromise your position, and rarely achieve the objective.
If interdiction is part of an op, it should be fully planned. Who is running the interdictor? Who is handling the engagement once the target drops? What are the rules of engagement after contact is established? These questions need answers before the operation begins.
If you want to train on interdiction work, mention it in Discord.