OMC FLY SAFE. FLY TOGETHER.
BALDUURSGATE · PIRATE OPS · PIR-02

3D INTERDICTION MAP

Route, celestial bodies, intercept point and effect sphere in space – rotate, zoom, centre.

Every number on this page is computed, not measured. None of it has been verified in game yet – review status NEEDS RE-CHECK.

Map

OriginDestinationIntercept point and effect sphereyour positioncelestial bodies

Drag to rotate, wheel to zoom. On a phone: drag with one finger.

Pirate Nav

QT abort

When to break the jump – target value, measured deviation with its sign, and the number you watch for in game. Negative means: break earlier.

Verify position

Run /showlocation in game and paste the clipboard content here. The page only reads what you paste – it does not access your clipboard and sends nothing anywhere.

Live navigation

When this page runs inside the BalduursGATE client, the client can hand a position copied with /showlocation straight to it. In a normal browser you keep pasting by hand – both lead to the same calculation.

The client sends nothing but a checked position contract. No other clipboard content leaves your computer – this page cannot read the clipboard at all.

Result

Where the numbers come from

Anchors and bodies
chronist/geo/bodies.csv – Stanton: 39, Pyro: 38 anchors, in km
Origin
VerseTime / Murphy Exploration Group, aus den Spieldateien (chronist/geo/QUELLEN.md)
Effect radius
chronist/qed.json – Reynie-QVG (20000 m)
Origin
Data.p4k · quantumenforcementdevice · Feld radiusMeters
Game version
sc-alpha-4.10.0-hotfix__1.0.191.55227
Calculation model
pir-02-rechenmodell/1 · ad74f7c0e9d2e2fe

Not offered for the interception calculation: Burke-QD (4 km), Tidelock QD (4.5 km), qed_rsi_s03_scorpius (5 km). These are dampeners: inside their jammer range they stop anyone from entering quantum travel, but they pull nobody out of it. Their radiusMeters field reads 1 – an unset field, not a one-metre radius. So there is no interception point for them, not because a value is missing but because none exists.

What we do not have

Protected and exclusion zones
Our game data carries no size for a protected zone. Only the device’s own check range (30,000 m) is sourced. The map therefore shows no exclusion volumes.
The exact shape of /showlocation
No hit in the game version’s global.ini (90,363 lines) – the command builds its output in code. The parser therefore accepts several clearly described shapes and states which one it recognised.
The unit of the coordinates
Also not provable. The page checks both readings against the extent of the system and says which one fits – or that it is ambiguous.
Physics grid and commlink
We have no solid data on this. So all that stands here is one line: DATA MISSING.
Movement of the bodies
We treat system positions as fixed. A body’s own rotation does not change that, and orbital movement is not represented in our data. Re-check on patch day.
Routes across several jumps
PIR-02 computes one straight quantum leg between two anchors. Jump-point chains across systems come later.

Physics grid / commlink: DATA MISSING.

To the Interdiction Planner → · Back to Pirate Ops