Understand what a Runeword requires
The August development update and version 0.21 announcement describe Runewords as ordered combinations. A sequence uses three or five runes and grants a global bonus when valid and active. The combination is deterministic rather than a different random recipe for every player. A shared sequence still needs to be reproduced with its order intact.
The retained sources do not provide a complete recipe dictionary. They also do not establish a named best Runeword for every class or damage type. A valid example would require the exact sequence and its confirmed effect. Recipes and effects not recorded in the research remain 待确认.
Check order before replacing a rune
An ordered sequence is more specific than a collection of the same rune names. Reordering the entries means you are no longer reproducing the recorded combination exactly. Before replacing a rune, compare each position with the original setup. This prevents an order mismatch from being mistaken for a missing stat or a balance change.
The source material does not say that every arrangement of three or five runes is valid. Having the right number of entries is therefore not sufficient proof of activation. Record the activation result shown in the game rather than inferring it from the number of occupied positions. A complete explanation of every invalid combination remains 待确认.
Understand Runeword Discovery
The August announcement describes Discovery as making more combinations valid. It is not presented as a requirement to grind every individual combination before using the system. This matters when comparing two saves that produce different results from a shared sequence. Check the player's Discovery state alongside the copied order and unlock.
The retained research does not establish the precise Discovery threshold for each sequence. Assigning a numerical threshold without the corresponding verified recipe would be speculative. The same limitation applies to a claimed guaranteed bonus from increasing Discovery by a particular amount. Use the current activation display to verify the result on your save.
Review rune effects changed in version 0.21
The 0.21 announcement identifies Adr with Added Attack Force and Kyn with Increased Proc Chance. It identifies Ydr with Inverted Attack Force and Lith with Ally Summon Amount. Those names describe different mechanical roles. They should not be substituted for each other merely because an old build uses a similar slot arrangement.
The same update explains that negative Attack Force pulls enemies toward the damage origin. That interaction is particularly relevant when reviewing an inverted-force setup. It does not establish an exact pull distance or guarantee control against every enemy. The Attack Force guide separates the documented direction change from unverified scaling formulas.
Distinguish reusable runes from recipes
Version 0.19.7 states that Xal, Xol and Xul can be reused indefinitely on the same or different abilities. This is a documented property of those named runes in that announcement. It does not establish the same behavior for every rune in the game. A general rule should not be inferred from a specific exception.
Reusing a rune and activating a Runeword answer different questions. One concerns how a named rune can be applied, while the other concerns a valid ordered sequence and its global bonus. Keep these checks separate when troubleshooting a setup. The retained sources do not provide a complete rune inventory or acquisition table.
Check known planner and display fixes
Version 0.21 fixes an Auto-Build issue involving three identical runes and Yiln. If an old report matches that situation, its version matters when interpreting the failure. The fix does not prove that every inactive Runeword comes from the same bug. Recheck the sequence and unlock before generalizing from that report.
The 0.21.1 hotfix corrects an upgrade display that incorrectly showed a decrease for Ydr. A misleading preview and an actual effect reduction are different claims. The announcement confirms the display correction, not an undocumented rebalance of every related stat. Compare the installed patch and the current result when evaluating an older screenshot.
Use a reproducible activation check
First record the game's version and confirm that the Runeword system is unlocked. Then copy the complete three-rune or five-rune sequence in its original order. Check Discovery and read the resulting activation information. These steps follow the dependencies described by the official announcements.
If the combination still fails, keep the exact sequence and the observed message together. Do not replace the missing explanation with an invented recipe, hidden level requirement or guaranteed grind target. A source-backed recipe can resolve that gap once one is available. Until then, the sequence-specific requirement remains 待确认.