Put Points Toward the Problem You Actually Have
Clover Legends stats are divided into Melee, Defense, Magic, and Mana capacity, with points earned as your character levels. Allocate Clover Legends stats around the attacks you use, the hits you can survive, and whether mana limits your spell rotation rather than copying another player's four numbers.
The Stats panel also includes an available-points counter, individual plus buttons, an Add per tap field, Auto assign controls, and Reset Stats. Those controls matter as much as a suggested build: the wrong batch size can put more points into an attribute than you intended, while automatic assignment can make it harder to understand a manual adjustment.
Obey's September 14 walkthrough at 4:02 shows this menu and a reset. Use it to locate the controls, then choose an allocation for the attacks and enemies you are using now.
Start by making a distinction between three different numbers. Your character level earns progression and stat points. Your Book Level unlocks grimoire spells. Your individual attributes represent an allocation you can change. A high value in one is not a substitute for progress in the others.
| Stats panel element | What it tells you | Practical use |
|---|---|---|
| Available stat points | Unallocated points on the account | Know how much you can distribute |
| Melee | A separate melee attribute | Compare when evaluating close-range attacks |
| Defense | A separate defensive attribute | Investigate when taking damage stops your route |
| Magic | A separate magic attribute | Compare when evaluating spell-focused combat |
| Mana capacity | A separate mana attribute | Investigate when mana limits casting |
| Add per tap | The amount associated with a plus-button action | Control allocation increments |
The useful question is not whether all four numbers are large. It is whether the next points improve the part of a fight that currently costs you the most time or causes failure.
Allocate Points Without Losing Track
Open the Clover Legends stats panel between fights so you can read the counters without an enemy interrupting. Note your available points before you start. If you want to make a deliberate manual change, set Auto assign to Off and inspect the Add per tap value.
The recorded menu has Add per tap set to 10. That is a value on the demonstrated account, not an instruction to use batches of ten at every stage. A smaller increment is easier to evaluate when your available budget is limited; a larger one is convenient only when you already know where the points should go.
Use the plus button next to the intended attribute, then read both the attribute total and available balance again. This simple check catches a mistaken selection immediately. It is easier to correct your plan after one allocation than after several taps across four rows.
| Before you tap | During the change | After the change |
|---|---|---|
| Note available points | Select one attribute's plus button | Confirm the expected row increased |
| Read Add per tap | Make one deliberate allocation | Confirm the available balance decreased |
| Check Auto assign | Keep the setting stable | Reopen the panel after the next level |
| Choose a combat problem | Avoid changing equipment simultaneously | Repeat a familiar encounter |
Auto assign is convenient when you want to keep fighting between levels. Watch how your totals change after leveling, then decide whether that allocation suits the build you intend to develop.
For a manual plan, write down a short priority rather than four permanent percentages. For example: improve the main spell rotation, add survivability if ordinary enemies interrupt it, and revisit mana only if the resource bar prevents another useful cast. That priority remains useful as enemies change, whereas a copied ratio can preserve an old problem.
Avoid treating unspent points as a collection to save indefinitely. They cannot help an encounter while sitting in the available pool. The reason to pause is to decide what the account needs, not to wait for a mythical perfect distribution that applies to every book and island.
Build Around a Repeatable Fight
A Clover Legends stats build is easier to judge against one familiar quest than against random enemies across several islands. Choose a target you can defeat reliably. Keep the same grimoire, accessory, skill sequence, and distance while assessing a point change.
For a spell-centered account, Magic is the relevant attribute to examine first, but watch the whole encounter rather than only the largest damage number. If you run out of mana before the enemy falls, additional offensive investment may leave the interruption unchanged. If the enemy defeats you before you finish the rotation, survival is the immediate limitation.
Melee deserves a separate comparison if close-range attacks are central to your play. Test the basic attack of the book you actually use: different grimoires have visibly different basic attacks. Compare the result against the same enemy before deciding where the next allocation belongs.
| Repeated problem | First comparison to make | Keep separate from the stat decision |
|---|---|---|
| Spells land but fights take too many rotations | Magic allocation | Missed shots and locked spells |
| You lose fights before completing attacks | Defense allocation | Standing inside avoidable attacks |
| Casting stops when mana is exhausted | Mana capacity allocation | Waiting for a skill's cooldown |
| Close-range attacks are your main damage source | Melee allocation | Assuming all basic attacks scale identically |
| Results vary wildly between attempts | Repeat the same encounter | Critical hits and different enemy types |
Mana and cooldown are particularly easy to confuse. If a skill is unavailable because its timer is still running, a larger mana pool is not the same as reducing that timer. If the timer has ended but you cannot afford another cast, the resource limitation is different.
The Forge provides separate equipment effects that can overlap with these goals. In Obey's Forge segment, accessories advertise damage, critical effects, health regeneration, and cooldown reduction. Keep the accessory unchanged while judging your Clover Legends stats so you do not credit the wrong upgrade.
Book progression matters too. The official game description identifies Book Levels 10 and 20 as spell-unlock milestones, with awakening raising the book's level cap and improving damage and critical performance. A newly unlocked spell can change your rotation more than a small point adjustment.
That suggests a useful review schedule: reconsider your priorities after unlocking a spell, switching books, equipping a meaningful accessory, or moving to a harder enemy group. You do not need to rebuild after every single level. Reassess when the way your character fights changes.
Reset Stats With a Replacement Plan Ready
The Clover Legends stats menu has a Reset Stats button. In the recorded sequence around 4:09–4:15, the allocated values become zero and the available pool becomes 11,162.
The numbers before the reset make the result easy to follow:
| Attribute | Before the demonstrated reset | After the demonstrated reset |
|---|---|---|
| Melee | 3,488 | 0 |
| Defense | 2,594 | 0 |
| Magic | 3,624 | 0 |
| Mana capacity | 1,456 | 0 |
| Available points | 0 | 11,162 |
The four starting allocations add up to the displayed returned pool. These figures describe Obey's character, not a build recommendation. Copying them would preserve that account's priorities even if your book, equipment, and enemies were completely different.
Before resetting, capture your current distribution and decide what you intend to change. A useful reset has a reason: you moved from a close-range approach to spell-heavy combat, discovered that mana was not your bottleneck, or spread early points without understanding the menu.
Read the current reset confirmation and any displayed cost before committing. Keep your replacement allocation ready so the returned points can immediately support the combat approach you want to try.
Once reset, allocate the points before returning to a difficult fight. Start with the priority that motivated the reset, then cover the survival or resource shortfall you already observed. Recheck the totals when finished so you do not leave a substantial part of the pool unused by mistake.
For a fair before-and-after comparison:
- Keep the same book and accessory equipped.
- Fight the same enemy type on the same island.
- Use the same opening spell and follow-up sequence.
- Compare several attempts rather than one lucky critical hit.
- Notice whether you finish, survive, and can cast when needed.
This turns Clover Legends stats into a practical adjustment instead of a cycle of copying builds and resetting whenever a different video appears. The best distribution for your next quest is one that addresses an observed limitation and remains usable when the fight lasts longer than expected.
Clover Legends Stats FAQ
Is there one best stat ratio for every grimoire?
No single ratio follows from the four menu labels. Your attack choices, unlocked spells, accessory effects, mana use, and survival all affect what the next points should address. Begin with your primary combat approach, then adjust against the same quest until the allocation supports a reliable rotation.
Does character level unlock all grimoire spells?
The official description ties new spells to Book Levels 10 and 20. Character progression and book progression should therefore be tracked separately. If a spell remains locked, look at the book's level requirement rather than assuming more points in Magic will unlock it.
Does Reset Stats delete the allocated points?
Obey's demonstration returns the allocated total to the available pool: 11,162 assigned points become 11,162 available points. Check the current confirmation before using it, then redistribute before combat.
Should beginners use Auto assign?
Use it only after watching where newly earned points go. Manual allocation is clearer when you are learning which limitation matters. Once your Clover Legends stats priorities are stable, convenience is useful, but an automatic setting should support your build rather than decide it unnoticed.