GearTools
Plan your gear for the current season — or tell GearTools the stats you want and let it find the set.
Then every item tooltip in the game tells you whether a drop belongs to one of your plans.
GearTools is read-only. It never equips, buys, upgrades, disenchants or changes your gear in any way. It plans, it calculates, and it annotates.
Plan a set by hand
Pick a class, a spec and a preset, then fill sixteen slots from the season's loot — raids, Mythic+, delves, world bosses, crafted gear and the catalyst. Choose the upgrade track and rank for each piece and watch the stat table follow.
Presets are account-wide, so you can plan for an alt you have not rolled yet.
Or search for the stats you want
Give the search a target — 2,000 mastery, 30% haste — and a priority
order, and it finds the set that reaches them.
Targets come first. GearTools will spend as much of your stat priority as a target costs, and only then use the priority to decide what to do with what is left over. If a target cannot be reached it says so, and by how much, rather than quietly returning something close.
Search either the season's full loot table (what should I aim for) or the gear already in your bags (what can I wear right now). Lock the slots you have already decided, change a target, and search again.
Crafted gear's two secondaries are a choice the search makes for you — the result names the pair to ask the crafter for.
Recognise a drop without opening anything
Every item tooltip in the game — bags, loot rolls, the Great Vault, chat links, the Auction House — gains a line for each preset that item belongs to:
GT: Warrior / Fury — Raid BiS (Hero 4/6)
GT: Paladin / Protection — M+ (Myth 2/6)
It covers every preset you have saved, on every character.
Numbers that match your character sheet
Primary, stamina and all four secondaries, as ratings and percentages, with the difference against what you are wearing. The current column reproduces your character sheet exactly — gems, enchants, class bases, buffs and mastery coefficients included — so the two can be compared without mental arithmetic.
Diminishing returns are modelled rather than merely flagged: a stat past a breakpoint shows the penalty in effect, hovering it explains which thresholds you have passed, and the search scores effective rating rather than raw.
Sim it properly
One button produces a complete, paste-ready SimulationCraft profile in Raidbots format, carrying your enchants and gems over from the gear you are wearing.
What GearTools is not
It is not a simulator, and it says so on screen. It adds up printed stats. It does not model DPS, set bonuses, trinket procs, enchants or gems, and it cannot tell you that a lower-item-level trinket is better because of what it does. Trinkets are picked by hand for exactly that reason.
Use GearTools to narrow the field. Use SimulationCraft to settle it — that is what the export button is for.
Getting started
Click the GT button on your minimap, or type /gt. The window is free-standing: it does not open with the character sheet, does not move when Blizzard rearranges its panels, and reopens where you left it.
The two windows are the icons down the left edge — armour for the planner, the magnifier for the search. Hover either to see what it does.
Languages
English and Russian. Any other client gets English rather than blanks. Everything the game itself localizes — class, spec, item, stat, instance and encounter names — is read from the client's own APIs and is correct in every language.
Where the data comes from
The season's items, upgrade tracks, ranks, item levels and bonus IDs ship as a generated data file built from Raidbots' published client data, so every rank of every track has an exact item level from the moment you install. Nothing has to be learned first and nothing accumulates with play.
PvP gear is deliberately absent. It scales in instanced PvP and is measured in a currency this addon does not model, so its item level says nothing useful here.
GearTools is not affiliated with or endorsed by Blizzard Entertainment or Raidbots.
Found something wrong? Leave a comment on the project page — every fix in the current release came from someone reporting exactly that.

