← All tools

Research branch

Tech Tree Planner

Pick a vehicle and see its required-vehicle branch: folder root at the top, unlocks indented below, with RP to your selection.

Shows the required-vehicle branch for that unit: the folder root at the top, then everything that unlocks from it. Highlighted row is your selection — not a full nation tech-tree map.

Pick a vehicle (or open with ?target=slug) to see its research branch.

How to use this tool

Uses datamine requiredVehicle edges (not the full in-game folder UI). Selecting a line root shows everything that unlocks from it; selecting a mid-tree unit highlights it and totals RP back to the root.

Map a War Thunder research branch from required-vehicle links: folder root at the top, unlocks indented below, with RP to your selected unit.

  • Roots show one chip in the unlock chain — look at the branch tree below.
  • Use Unlock Calculator when you care about SL purchase + crew train totals with a “already owned” cut.
  • Cross-check odd naval/air folders in the client.

Branch map, not a full nation tree

Pick a vehicle. WT Charts finds the root of its requiredVehicle chain, then draws everything that unlocks from that root. Your selection is highlighted. RP / SL / crew totals cover the unlock chain to that selection.

Line roots (no parent) still show a full downward branch — that is the planner you want when a short “path” looked empty before. For cut-from-owned totals, use the Unlock Calculator.

Limits of requiredVehicle edges

The client UI groups vehicles into folders and events that are not always a single parent pointer. Treat this as a best-effort graph from public data, then verify in-game before a long grind.

Frequently asked questions

Why did I only see one vehicle before?
Older builds only drew the unlock chain up to the root. A root vehicle is a chain of one — the branch tree below it is where the rest of the line lives.
Is this the full French / US / etc. tech tree?
No. It is the required-vehicle branch for the unit you picked, not every folder in that nation.

Limitations

  • • Edges are requiredVehicle only — not every hangar folder grouping.
  • • Very wide branches are depth/node capped so the page stays readable.