records
Evidence
Swords
Swords test close-range pressure and how a party manages space around an encounter.
Choose Swords when you want the weapon itself to be the first build question.
Axes
Axes let you compare a heavier-looking close option with the rest of the weapon list.
Use a repeatable route to learn the spacing before adding another layer.
Clubs
Clubs keep the first comparison grounded in the named weapon categories.
Test Clubs as a deliberate alternative rather than assuming a universal ranking.
Spears
Spears let you ask how reach changes the way a party approaches danger.
Let the encounter determine whether reach solves a real route problem.
Bows
Bows help you study distance, positioning, and the space your party needs.
Keep an escape route in mind while learning how distance affects preparation.
Path of Blight
Blight gives a character a distinct magical direction to test.
Choose Blight as an experiment, not as a sealed class or damage tier.
Path of Pyre
Pyre can frame a build around a different magical question.
Compare Pyre across more than one encounter before judging the direction.
Path of Rime
Rime adds another route for a flexible character to explore.
Use party needs and encounter space to decide whether Rime complements the weapon.
Path of Storm
Storm keeps the magical layer open to a separate experiment.
Treat the first investment as information about your route, not a final answer.
Adventuring
Adventuring supports the wider expedition rather than a single attack pattern.
Choose it when route reading and discovery are part of the build question.
Survival
Survival focuses on preparation, supplies, and staying effective away from town.
Consider it when a route is limited by recovery or resource pressure.
Dungeoneering
Dungeoneering gives dungeon preparation its own build direction.
Use a dungeon problem to decide what this investment should answer.
Weaponry
Weaponry connects the named weapons to longer-term build practice.
Choose it when the party is learning weapons together.
Oldways of Magic
Oldways of Magic links the general growth layer with the named Magic Paths.
Keep it flexible while you learn which magical direction the route rewards.
Source details: Share feedback through the game's community channels.
Read the records as build directions
Fourteen combat options fall into three useful groups. Weapons are the physical tools you bring into an encounter; Magic Paths set a magical direction; skill trees support exploration, survival, dungeoneering, or weapon use. These choices do not form a tier list: no damage rankings, cooldown tables, or universal best combination are established for the current demo.
Instead, begin with the player task in front of you. If an encounter asks you to control distance, compare a ranged option with a path that changes how you create space. If a route is long and resource pressure matters, compare the broader skills that help you prepare and read the world. If the party already covers one answer, take a different path so the group learns more from the same expedition.
Weapons set the first question
Choose from Swords, Axes, Clubs, Spears, and Bows. Each suggests a different starting question—close pressure, reach, impact, or distance—but no complete move list or numeric comparison is established yet. Test one category long enough to understand its spacing and resource demands before switching. A weapon choice should make you curious about how an encounter is solved, not make you feel committed to a class identity.
A useful first test is to keep the rest of the character relatively stable while changing the weapon. Return to a similar route, observe which attacks invite you closer, and note whether the party needs a different response. That small comparison is more reliable than choosing a weapon from a generic RPG reputation. Later choices in Magic Paths and skill trees can broaden the same weapon or cover a weakness that the first trip exposed.
Magic Paths add a direction
The four Magic Paths are Blight, Pyre, Rime, and Storm. They give a character clear thematic directions, but no complete spell catalogue or numerical effect table is established yet. Treat a path as an experiment. Decide whether you want to change the encounter’s space, prepare differently for a dungeon, or give the party a complementary tool, then test that idea in the playable build.
Magic becomes most useful when it answers a route problem rather than existing as decoration on the character sheet. A group that already has a strong close-range answer may learn more from a path that changes engagement distance. A solo player may value a direction that makes a mistake recoverable. Keep the first investment small enough to revise your plan, and record the encounter that convinced you to continue or change course.
Skill trees widen the build
The five skill trees are Adventuring, Survival, Dungeoneering, Weaponry, and Oldways of Magic. They cover the wider competencies around a run: finding a route, staying prepared, handling dungeon pressure, understanding weapons, or extending a magical direction. They are useful for players who do not want a build to be only about damage. A background can give the first story, while a skill tree explains what the character practices during the expedition.
Do not spend every early choice on the same answer before you know what the next location asks of you. If the group is short on preparation, Survival or Adventuring may answer more than another attack option. If a dungeon exposes a specific gap, Dungeoneering or Weaponry can give the next trip a purpose. Oldways of Magic creates a bridge between the broader skill layer and the four named paths, but no mandatory sequence is established. Use the five trees as verbs rather than labels: adventure to find a route, survive to protect supplies, dungeoneer to handle pressure, practise weaponry to understand spacing, or follow Oldways of Magic to extend a magical question. That framing keeps a classless build connected to what the party is actually doing.
A first-build method
For a first run, choose one weapon category, one Magic Path or broader skill direction, and one practical question. Keep the question narrow: can I maintain distance, can I recover after a mistake, can I prepare enough for a dungeon, or can this party split responsibilities without losing the route? Answer it across more than one encounter before changing everything. That gives the classless system time to show a pattern instead of turning every surprise into a new build.
The filter reduces the options to a comparison you can share or revisit. Weapon, Magic Path, and skill-tree filters update the URL without changing the underlying choices. Your final build belongs to the current player experience, not to a label. Choose an experiment, then let the Whisperwoods, Rivermere, and the dungeon route tell you what to keep.
Compare without turning the list into a tier chart
A clean comparison changes one variable and keeps the question visible. Use the same kind of route, bring a similar amount of preparation, and pay attention to what the weapon or path lets the party do that it could not do before. A category can feel valuable because it solves a positioning problem, saves a resource, or makes a solo mistake easier to recover from. None of those benefits needs to become a universal ranking to be useful.
The current options give names and broad roles, not a complete numerical model. That is good news for an exploratory game: build around curiosity instead of chasing a chart the demo does not establish. Write down the encounter that changed your opinion, then make the next investment answer that encounter. If a friend asks for the best option, ask what route and party shape they are trying to solve first.