Plan a runeword without wasting runes
Finding a recipe is only the first check. You also need the right number of each rune, an eligible base, the exact socket count and the correct insertion order. The tracker helps compare plans, but it cannot inspect the item in your game. Use this workflow before spending a valuable rune.
1. Pick the recipe before the base
Open the runeword reference and check the permitted equipment types, sockets and game-mode restrictions. A similar-looking equipment type is not necessarily eligible. Normal and superior white/gray bases can support runewords; magic, rare, crafted, set and unique equipment cannot.
2. Count repeated runes separately
For Phoenix, the order is Vex → Vex → Lo → Jah. Its 4 sockets require 2 Vex, 1 Lo, 1 Jah. Owning one Vex and all the other rune types is still one Vex short.
| Rune | Copies required | If you own one |
|---|---|---|
| Vex | 2 | 1 still missing |
| Lo | 1 | Enough for this recipe |
| Jah | 1 | Enough for this recipe |
Enter actual quantities in the rune inventory. Compare what is missing before considering upgrades. Two plans can compete for the same high rune: a recipe being affordable does not mean you can make every affordable recipe simultaneously. Reserve ingredients for the plan you intend to make first.
3. Verify the exact item
Phoenix permits the equipment types Weapon and Shield, with exactly 4 sockets. Use the base reference to check requirements and maximum sockets, then verify the actual item's quality and sockets in game. A base maximum is not a promise that Larzuk or a Cube recipe will produce that number for every item level.
The listed rune requirement for this recipe is level 65. Your chosen base or other item properties can impose a higher requirement. Check strength and dexterity too; meeting the rune level alone is not enough to equip the result.
4. Treat upgrades as a separate cost
A rune-value calculation is not a promise of an immediately craftable upgrade. Higher upgrades also consume their specified gems, and Cube upgrades do not run backward. Review each upgrade formula, keep needed lower-quality gems, and do not count a rune both as an upgrade ingredient and as reserved equipment stock.
5. Insert in order, then update the tracker
Read the recipe alongside the item one last time, then insert the runes in the displayed order. The Hel and Town Portal recipe can remove socket contents, but destroys those contents; it does not recover your expensive runes or add sockets. The app's craft or quantity controls only update its records, so subtract materials when you actually consume them in game.
Keep experiments separate from owned equipment
Use the build planner to compare a proposed setup without treating it as owned gear. Keep notes on the intended base and missing ingredients. Use separate inventory profiles for separate stockpiles rather than pooling runes that cannot be transferred between your game modes. Export a backup before clearing storage or switching devices: this app's local saves are not a cloud account.
In the 33-rune catalog, names and recipes are reference data, while your quantities are private browser records. This page does not expose saved inventories to crawlers.
Sources and limits
This unofficial fan reference uses the app's released-game data. Check game edition, realm and patch before applying an equipment or encounter rule. Drop descriptions identify sources, not guaranteed outcomes. See Blizzard's 3.3 release notes and the pinned extracted game tables. Report corrections through Contact Us in the app menu.