Spend early skill points toward a usable action and the conditions that make it work. Check prerequisites, preserve resource recovery and movement, and avoid relying on a late interaction before you can reach it.
Compare build directions · Follow the point checklist
Read the tree before choosing a destination
Count connecting nodes as well as the destination. A spell, its modifier and the condition it needs can belong to different parts of the route. An attractive final node is not a complete early plan.
Current EA points, resources and resets
| Rule | Current information | Evidence boundary |
|---|---|---|
| Act I level cap | 25 | Official Early Access FAQ |
| Pre-launch point estimate | About 60; not a current verified total | Developer’s pre-launch tree explanation; approximate total, not a level-up formula |
| Stamina | Resource for physical actions | Developer’s combat explanation |
| Concentration | Resource for spells; basic-attack hits restore it in combat | Developer explanation; exact recovery amount depends on further verification |
Skill respec and attribute resets
Skill-point refunds and attribute resets affect different parts of a character. Check the current service, cost and unlock requirement before relying on a refund. The respec guide separates these actions from changing race or class.
Demo and Early Access routes
The official EA content announcement describes a skill-tree overhaul. Older Demo node names, connections and point costs should not be copied as a current EA allocation. The developer’s tree post describes the system before launch, so its totals are historical context.
A skill-point reset, an attribute reset and changing class are separate questions. Do not assume they are one free operation. Until costs and refund scope are verified, choose the next purchase for a concrete reason: obtaining an action, meeting its prerequisites, supporting recovery or fixing a recurring failure.
Early skill-node priorities
| Current problem | Type of node or choice to inspect | Check before buying |
|---|---|---|
| You lack a useful active action | A reachable spell in the selected tree | Prerequisites, total path cost and its role in the loadout |
| Your main action works but creates a timing problem | Its modifiers | What the chosen option replaces |
| A payoff has no setup | An application or resource-generating interaction | The generator works with the spender you intend to use |
| You keep being caught after attacking | A movement or survival option available to the combination | Whether it addresses the actual failure |
| A desired book is unusable | Attribute training or relevant attribute support | The exact book requirement, not its theme |
Before you spend a point
ACTION
1. Pick the next usable action
Choose what the character should be able to do next. Check whether the spell is already learned, can be equipped and meets its requirements.
ROUTE
2. Trace every prerequisite
Count the complete path to that action or modifier. Do not spend as though a distant node were available immediately.
INTERACTION
3. Supply the condition
If a payoff consumes Bleeding, Burning or another stack, identify the action that supplies it. Check resource generation before adding a spender.
RECOVERY
4. Keep the character playable
Preserve a way to recover, move and survive. A modifier that changes movement can alter the whole sequence.
Start with the action, then inspect its branch
Choose one action you expect to use repeatedly. Identify whether you want it to apply a status, spend a status, create space or contribute another specific job. Then inspect the branch that supports that job.
Small attribute nodes, active spells and modifiers are different kinds of investment. A connecting attribute node may be part of the route to an action rather than the final reason for taking the path. Count that cost instead of comparing only the destination icons.
Check whether the new action will earn an active slot. Dimraeth allows five equipped spells. A node granting a useful spell can still be a poor immediate purchase if you do not intend to replace any of the five actions currently doing necessary work.
The Dimraeth skill-tree explanation separates the race, class and archetype contributions. That distinction matters when a route shown for another combination is unavailable on your tree.
Preserve a movement skill's useful behaviour
Vortex provides a practical modifier lesson. The Minotaur Brawler example considers changing its form, then values retaining movement. That movement contributes to survival and positioning, so removing it changes more than the skill's damage.
Before spending on a modifier, read what behaviour disappears or changes. If the action currently gets you out of danger, identify the replacement escape tool before converting it into something less mobile.
This is not a rule to avoid damage modifiers. It is a rule to compare the full trade. If another action now handles movement reliably, the alternative modifier may make more sense for your current loadout.
Learning a spell and casting it are different
Check the learning requirements before investing attributes. Then inspect the casting costs and the available slot. Owning a spellbook, learning its spell and equipping it are separate steps.
The community mechanics video discusses these distinctions at 00:38–02:56. Exact costs apply to the demonstrated spell and version, not every spell.
Attributes, experience and book requirements
Earned experience and completed attribute training are separate stages. If your next goal is a spellbook with a requirement, check the current attribute value and the training cost before spending elsewhere.
Flaming Strike has a concrete pre-release learning example involving Memory and Adventure requirements. The point of the example is that more than one attribute can matter, not that every current version must retain those recorded numbers.
A world spellbook can fill a gap without granting every exclusive modifier from another class or archetype. Decide whether you need the book's base action or a specific tree-supported interaction. Those are different reasons to invest.
Read the Dimraeth spell-equipping guide if the book is obtained but the action is not usable. Skill-point spending will not fix a spell that simply has not been assigned to the intended slot.
Match setup with payoff
A modifier can change an action’s role. Recheck whether it applies, benefits from or consumes an effect. Do not combine incompatible variants in one planned configuration.
The mechanics video gives an example of a buff conversion at 04:32–05:57. Verify the current tooltip before copying its numerical values.
Effect-based builds need the condition that activates their benefits. A bonus against Bleeding targets asks for a way to apply Bleeding. A skill that spends Rage asks for a generator. A Fireball modifier that consumes Burning asks for Burning stacks on the target.
Write the interaction in order before investing. If you cannot identify the setup action, the payoff may be a later purchase rather than the next point. Taking several payoffs together does not supply a missing generator.
Recheck the sequence after obtaining a new skill. In the Minotaur Bleed example, the jobs assigned to Vortex and Pulverize evolve. Copying a generator from one stage and a spender from another can produce a written build that was never actually used as a complete configuration.
Modifier choices can be exclusive
A spell can have several appealing variants without allowing every variant simultaneously. Choices may be exclusive within an aspect. Read which option is selected and what selecting another replaces.
Fireball is a useful example: charged, piercing, rapid and Burning-consuming behaviours offer different decisions. They should not be combined into an imaginary early spell with every advantage at once.
After a modifier purchase, test the new input and timing. A charged behaviour can ask for a longer safe opening. A stack-consuming behaviour can change the order of your actions. Treat the modifier as a gameplay change rather than merely a percentage increase.
Follow the route for your actual build
| Chosen direction | Detailed route |
|---|---|
| Elf Shadow Bleed | Shadow progression and source video |
| Minotaur Brawler Bleed | Minotaur starter priorities |
| Human Magician Fire | Burning setup and recovery |
| Minotaur Brawler Stun | Blunt conversion prerequisites |
This page explains the decision method. The Fire and Stun guides explain their supported interactions; the Bleed guides discuss creator examples. None is a verified universal node-by-node allocation.
Test one meaningful change
Use a familiar encounter. After changing one skill or modifier, check that the intended effect appears, resources recover and movement still works. Record teammate and pet support before comparing results.
A useful first purchase checklist
Before confirming a point, check the destination and all connecting costs, the action's role, any exclusive modifier choice and the loadout slot it would use. Then ask what changes in the next encounter.
If the answer is only that a distant build might eventually need it, compare that purchase with something that improves an action you use now. Early points are most useful when the character can put them to work immediately, while still keeping the intended later direction in view.
Sources and version scope
- Developer: skill trees
- Developer: spells and effects
- Community mechanics explanation
- Official Steam images
Official and pre-release illustrations are labelled individually. They are not a substitute for current allocation screenshots.