At a glance

  • Name the specific failure before changing your build.
  • Test one variable against the same baseline.
  • Check current passive tooltips where public sources disagree.
In this guide

Before rerolling a Clover RPG build, decide whether you need different actions or a different passive. Community references describe magic as a moveset choice and race as a source of passive effects and stat bonuses. A passive cannot teach an unfamiliar attack pattern; a new magic does not automatically fix defensive timing.

Name the problem your next change must solve

Write one goal: finish a solo encounter more reliably, support a group, or land a short sequence against a moving opponent. Describe the observed failure. 'I run out of mana before the next opening' is actionable; 'my build is not S-tier' is not.

Record your current magic, race, weapon or style, relevant stats and activity. Keep that setup as a baseline. A comparison means little if the enemy, equipment and several other choices change together. The notebook stores observations; it does not calculate damage.

Scroll sideways to compare all columns →

Observed problemInvestigate firstEvidence needed before rerolling
You cannot use a spell reliablyIts aim, range, conditions and recovery.A repeatable situation where the current action fails your goal.
Spells work but resources run outResource use, downtime and the current race tooltip.Whether the proposed passive addresses the resource you actually lack.
Your weapon does most of the workWeapon timing and the current physical bonuses.A reason the proposed change helps that same sequence.
You die during failed defensive inputsSpacing and defensive practice.Separate an input error from a survivability limitation.
You want a different combat rhythmAnother magic's documented kit.A specific action you want, rather than its rarity label.

Use race descriptions as hypotheses, not a tier list

Across the checked community race references, Human is associated with improved selling, Elf with reduced spell expenditure, Dark Elf with spell damage, Eldritch with physical damage, and Dryad with conditional regeneration. These descriptions suggest questions to investigate; they do not establish an optimal race or a measured advantage for your encounter.

An Elf-related benefit matters if spell expenditure is the bottleneck. An Eldritch-related benefit matters if your attacks qualify. A selling benefit serves another goal. Check the live tooltip before treating an exact modifier as current.

Scroll sideways to compare all columns →

Reported benefitUseful comparison questionCommon comparison mistake
Lower spell expenditureCan the same sequence be completed with less downtime?Adding an extra spell and calling the result a like-for-like test.
Spell or physical damageDoes the same applicable attack behave differently?Changing weapon, stats and target at the same time.
Conditional regenerationWhen does the condition appear, and does it matter in this encounter?Assuming an effect is continuously active.
Improved sellingDoes the displayed sale value change for the same item?Using an economic perk as a damage ranking.

Check the rare-race tooltip before building around it

BloxInformer's table pairs Lesser Demon with Heavenbound/Divine Retribution and Lesser Angel with Wrath Unbound/Hellsworn. Another community directory reverses those packages. A copied recommendation may depend on a swapped label.

Check the current race description and any implementation restriction before building around the effect. Counting websites cannot resolve the conflict. A contract-related description also does not establish that its associated progression system is available.

Compare magic by the action you want to gain

Choose the action you need before choosing a rarity label. These examples are community-reported kit functions, not tested balance rankings; confirm their availability and conditions in the current spell menu.

An action helps only if its range, unlock and recovery fit your encounter. Compare it with your current sequence before spending rerolls.

Scroll sideways to compare all columns →

Magic and reported actionPotential useQuestion to verify
Light: Divine Field ally healingGroup recoveryDoes its alternate activation help your group here?
Wind: Aerial EfficiencyAirborne castingDoes your actual sequence meet the airborne condition?
Shadow: Void Beam recastRanged pressureCan you perform the recast reliably?
Time: Slow Zone / Time StopSpace controlDo the effects apply to your intended target?

Make a keep, practise or change decision

Keep a setup that meets your goal. Practise first when missed inputs or inconsistent aim cause the failures. Consider changing one component when you can name the missing function, verify the replacement and accept the consequences shown by the current interface.

Before confirming any reroll, read what it replaces, whether existing progress is affected, its displayed cost and whether the previous result can be kept. Community descriptions of reset behaviour are not a substitute for that confirmation. Set a limit in available resources before starting.

Save the baseline, proposed change, supporting evidence and result to compare. Public sources were checked October 25, 2026; this is a decision framework, not a live balance test. Consult the magic and race directories, record your comparison in the build notebook, and use the probability tool after establishing a reliable rate.

Put this guide to use

Keep the next action and the observations you want to compare in your local player tools.

Record your baseline build

Before you head out

Should I reroll magic or race first?+

First decide whether you need a new action, a relevant passive or more practice. Check the current replacement and reset rules before rerolling.

Is Lesser Demon or Lesser Angel better?+

The checked community tables disagree about which rare race owns two passive packages. Check the current game tooltip before making a build decision; this guide does not turn that conflict into a tier ranking.

Sources & review notes

Reviewed October 25, 2026. Developer information takes priority. Disputed community claims, original practice suggestions and hypothetical calculations are identified in the relevant passage.

How we use sources and update guides