What base does a Hero Siege runeword need?
Use a compatible white socketed base and match its socket count to the selected runeword.
- A runeword begins with a compatible white socketed base whose socket count matches the chosen recipe.
- Verify both properties before inserting anything, because the correct runes cannot repair the wrong base type or socket count.
- White quality, compatibility, and socket count are three separate checks.
Passing only the socket count is not enough if the base is incompatible, and a compatible type is not enough with the wrong number of sockets. The Journal entry should be compared with the item before any rune is used. No colored base exception or substitute recipe is supplied on this page.
Does rune order matter?
Yes; verify the current Journal entry and insert the runes in the displayed order.
- Rune order is part of the recipe.
- Read the current Journal entry, arrange the runes in that displayed sequence, and insert only after the base and socket checks are complete; guessing the order risks consuming the setup incorrectly.
- Sequence becomes relevant only after the base checks pass.
Lay out the runes in the Journal's displayed order and compare each position before insertion. This reduces the chance that a correct set is consumed in the wrong arrangement. The answer establishes that order matters, but it does not reproduce a specific recipe or promise that an older community sequence remains current.
Where is the current runeword list?
Use the in-game Adventure Journal as the current authority; community lists are navigation aids, not permanent official data.
The Adventure Journal is the current place to confirm a runeword recipe. Use a community list to discover a name or narrow possibilities, then locate that entry in the Adventure Journal. The in-game entry supplies the live recipe details needed for action. This two-stage use preserves the convenience of navigation without elevating a static list above the current game. A missing Journal entry is a reason to stop, not permission to infer the recipe from memory.
A safe runeword decision has a deliberate pause before insertion. Confirm that the item is a compatible white base, compare its socket count with the Journal entry, and arrange the required runes in the displayed order. Each check can fail independently, and later checks cannot repair an earlier mismatch. Community lists remain useful for discovering a runeword name, but the current Journal is where the actionable recipe belongs. If the entry is absent or the item does not match, the correct outcome is to stop. The page offers no alternate colored base, substitute rune, flexible order, or remembered recipe that would justify proceeding despite that mismatch. Passing the base and socket checks opens the order check; failing either one closes the insertion branch. Passing all three still supports only the Journal entry being viewed, not a permanent recipe table for other runewords or later versions.
Before you rely on this guidebase type, socket count, rune order, and the displayed recipe must agree in the current in-game Adventure Journal before runes are inserted. Community material can help navigation but is not a permanent official recipe list. This page therefore explains verification and failure branches without publishing a static list or inventing substitutions for a mismatched base.