Karma

The current workspace contains 52 Karma records. Begin with the localized name, grade, ability family, and whether the record is regular or exclusive to a hero. Two Karma with similar art or a shared ability label can still have different growth, traits, costs, or compatibility. Use the roster and filters to create a comparison group that serves the same hero and purpose. An exclusive link is a published restriction, not a recommendation that the bound hero must always use that Karma. A regular record may be legal for several heroes, but legality alone does not make it the best choice. Open the exact detail and keep its identity visible throughout every level, ascension, and resonance comparison.

Karma progression has multiple axes. Level growth changes the published base stats according to the current curve. Ascension uses its own steps, material requirements, and cumulative costs. Resonance adds the published stat or trait changes for each unlocked step. Compare two candidates at the same level, ascension, and resonance state; otherwise a more-developed record can appear inherently stronger. The workspace controls allow each target to be changed independently so the resulting stats and costs remain attributable to one progression choice. A maximum view is useful for checking a ceiling, while the next affordable step is a different player question. Do not combine them into one score or assume every trait is active at level one.

When Karma is bound to a hero, read the bound hero, exclusive effect, general trait, and activation wording together. The hero link confirms compatibility and provides access to the hero’s full skills; it does not by itself prove final damage or uptime. For regular Karma, compare the ability restriction and the practical stat or trait the build needs. If an effect depends on a condition, evaluate whether the selected hero and encounter can actually maintain that condition. The database publishes the relationship and text without inventing hidden coefficients, animation behavior, stacking rules, or encounter-specific performance. Verify the decisive interaction in game before treating an exclusive label as a complete build recommendation.

Use the material planner when the decision depends on how much Gold and how many items are required to reach a chosen ascension step. Add more than one Karma or hero target to merge shared resources into a single requirement. Owned quantities remain local and reduce only the remaining column. Then open the build planner with the intended hero, add the Karma, and compare it alongside five equipment parts, Runes, set progress, and the Familiar slot. This order separates affordability from compatibility and compatibility from performance. A legal selection that cannot be completed with current resources is a future plan; an affordable record that violates a hero restriction is not a usable substitute.

The workspace can calculate published growth, show materials, expose resonance effects, and validate known hero links. It cannot know which Karma an account owns unless the player supplies local information, predict random acquisition, simulate a full rotation, calculate enemy-specific damage, or guarantee live availability. The selected detail state is a comparison tool, not a claim that every displayed maximum has already been reached. Treat missing values as unknown, keep candidate states equal, and confirm conditions inside the game before spending rare materials. After a data update, recheck growth curves, costs, traits, and exclusive bindings rather than preserving an old recommendation whose underlying record may have changed.