Karma Guide: Choose, Ascend, and Match Karma Without Wasting Materials

Start with the question you need to answer, not with a copied endgame build. The useful route is the one that matches your unlocked roster, current inventory, and next playable objective. The Karma catalog exposes ability, hero exclusivity, ascension, transcendence, resonance, and published material relationships; none of those alone proves final damage. Karma.

The build planner answers a loadout question before materials are spent: which Head, Chest, Leg, Hand, and Foot records are compatible with the chosen hero, and what official options can each selected piece actually roll? Begin with the hero because ability restrictions determine which equipment remains usable. Then decide whether the goal is completing a set threshold, checking a main-option pool, planning enhancement, socketing a Rune, or testing an exclusive Karma. Keeping that goal explicit prevents an attractive but incompatible piece from becoming the basis of the plan.

Fill the five slots in order and leave the picker on compatible records for the fastest workflow. Use Show all only when you need to understand why a specific item is disabled. After choosing a piece, inspect its main-option candidates, secondary-option candidates, enhancement target, reroll lock costs, and Rune socket. The Venomfog Shade Helmet example shows why these controls stay separate: an option displayed in the candidate pool is not a stat the item already owns, and a selected Rune roll is a planning input rather than a promised drop. Build Planner.

Results are ranked against localized names, descriptions, roles, effects, sources, locations, missions, categories, and useful keywords. Arrow keys move the active result, Enter opens it, and Escape clears the current query. Each result keeps up to a few verified connections visible, such as an exclusive Karma, recommended hero, item source, map position, or system route. These links let the player continue the same question without retyping it. A map query loads the published map index only when needed, so other searches remain responsive.

Treat names, requirements, relationships, counts, and displayed values as evidence. Treat live timing, random outcomes, account-specific availability, and unlisted triggers as checks that still belong in the game. The summary combines only published relationships and the choices currently made in the workspace. Set progress comes from equipped pieces; conditional set text remains conditional; exclusive Karma links stay tied to their supported hero; Rune values use the exact published roll selected in the socket. The verification row reports the current counts for equipment, sets, Karma, option entries, and Runes so the player can see the scope being searched. Probability labels describe candidate distributions and must not be converted into a prediction for one reforging or loot result.

A result’s category label explains what kind of page will open; the summary supplies context but does not replace the detail page. Multiple map locations are grouped with a count rather than duplicated as indistinguishable cards. The index uses public localized names and player-facing relationships. Unavailable areas do not appear, Belos material is kept separate from Orbis content, and unresolved rewards remain identified on the relevant system page. Karma.

Compare one constraint at a time. Keeping the same target while changing only the route, hero, slot, or milestone makes the cost of that decision visible and prevents several assumptions from being mixed together. Compare builds by the constraint that matters, not by filling every visible field. For a set plan, check whether the threshold survives replacing one weak slot. For a main-stat plan, compare only pieces available to the same hero and body part. For a Rune plan, distinguish the socketed published value from random equipment options. Enhancement and lock-cost views help budget a target, but the interface does not calculate final damage or conditional uptime. A cheaper compatible configuration may be more actionable than a theoretical combination that depends on several missing rolls.

When no result appears, shorten the query to the official name, clear only the current scope, and remove descriptive words one at a time. Search by the effect when an item name is forgotten, by the source when the target item is unknown, or by the location when several entities share a name. Do not treat the first high-ranked card as a recommendation; ranking measures text relevance, not combat power, farming efficiency, rarity, or account suitability. Open the detail record before making a resource decision. Hero Upgrade Materials.

Before committing, reopen every selected piece and confirm the hero restriction, part, set, main option, enhancement step, Rune roll, and Karma link. If a piece is missing, move to the equipment database or material planner instead of inventing a substitute stat. Revisit the loadout when inventory or the published options change, because saved selections can remain understandable while their available alternatives evolve. The planner establishes compatibility and published values; actual drops, reforging results, combat rotations, resistances, and final performance still require in-game confirmation. Build Planner.

Use global search as a router, then complete the decision in the specialized workspace. Move from a material result to its sources or planner, from a boss to exact phases and rewards, from a quest to its prerequisites, or from a map result to the selected location. If a localized query fails while the English official name works, keep the verified page and report the localization gap rather than inventing a synonym. Recheck results after a page update because available results and links can change with the published version. Finish by writing down one next action that can be verified: open a named page, test a rotation, visit a mapped point, confirm an unlock, or update the local plan after spending materials.