Skip to device check

Mode 07 · Rig · the step in between

You know what it has to do. Here is how the pieces go together.

A presentation says what the bait must do in the water. Tackle says whether the equipment can support it. Nothing said how to arrange the pieces to make it happen, which is the step where most rigs actually go wrong. Every measurement here is drawn from the depth and current you state, so changing one moves the whole assembly.

Local-only · condition context
No arrangement here predicts a bite. A rig is a mechanical answer to a mechanical requirement, and whether the fish agree is a separate question this instrument has never claimed to know.

07Rig

From what the bait has to do, to how the pieces are arranged

Presentation says what the thing must do in the water. Tackle says whether the equipment can support it. This is the step in between, and it is the one where rigs actually go wrong. Nothing here names a product — a rig is an arrangement of classes of component, and which brand of swivel is not a fishing question.

Quick start · worked mechanical jobs

Start with a recognizable job, then change what is not yours.

18 starting states

These are transparent form presets, not recommendations. Loading one fills the job fields below and nothing else. Every value stays visible and editable before the engine builds a rig.

The job

Optional after water and path are declared. If left blank, a built arrangement uses a visible assumed stand-in.

Left blank, it is derived from the depth and current and labelled as derived.

Not enough of the job is declared

Not enough of the job is declared to arrange anything. A rig is an answer to a mechanical requirement, and there is not yet a requirement here to answer.

  • · what the presentation has to do — the path
  • · which band you are fishing, or whether you are touching bottom
  • · what kind of water this is

Nothing checked yet. Add information to begin.