Choose an ancestry for identity
The demo offers Freefolk, Mossling, Grimhorn, and Stonefolk. Build 0.7 uses all four as starting ancestries; earlier builds used a shorter list. Choose the one whose look and story you want to carry into the woods. An ancestry gives the character an identity, not a permanent combat class, so later choices can still change the way the run plays.
A first run does not need a theory for all four options. Pick the ancestry whose visual and narrative identity makes you want to stay with the character, then use the rest of creation to supply the practical direction. Different ancestries make a co-op party easy to read even when players later invest in similar weapons. Start with the option that makes you want to see what happens next.
Use a background as a starting story
Nineteen backgrounds give the character a stronger starting story than a blank class selection. Treat a background as a question you want the run to answer: what would this person carry into the woods, what kind of problem would they notice first, and which skill tree would feel like a natural next step? The choice can guide roleplay and early decisions without closing the build.
A practical method is to pair the background with one immediate action. If the background suggests a scout, begin by reading routes and using the Adventuring or Survival direction; if it suggests a fighter, test a weapon category and watch how preparation changes the encounter. These are player experiments, not locked bonuses inferred from the name. Keep a note of why you chose the background so a second run can make a meaningful contrast rather than repeating the same first impression.
Customise for a character you can read
The demo offers hundreds of character customisation choices. That breadth is useful when a co-op party needs a quick visual language: a player can recognise who is carrying the next route, who is trying a different weapon, and who is returning to town. It is also a chance to make the character’s silhouette match the story you imagined. Spend enough time to make the character legible, then move into the expedition; the meaningful build decisions happen in play.
The safest way to avoid menu fatigue is to make two passes. First, choose a clear visual anchor such as hair, horns, moss, or stone-like features that makes the ancestry readable. Second, select details that support the background you picked. No appearance choice has a stated combat advantage, so choose the look that helps you recognise the character and enjoy returning to it.
Connect the starting idea to growth
The larger growth target includes more than fifty RPG skills and more than five weapon classes, while the current combat options include four Magic Paths and five broad skill trees. That gives a new character several ways to grow after the first creation screen. Start with one thing you want to understand, such as how a bow changes spacing or how Rime changes a plan, and let the next choice respond to what the route actually demands.
There is no need to decide a final build before the first dungeon. A background can point toward Adventuring, Survival, Dungeoneering, Weaponry, or Oldways of Magic; a weapon can expose a gap that a Magic Path helps cover; a party can ask one player to explore a different answer. Use the named options to compare scope, then let the next expedition decide which direction deserves more attention.
Keep version boundaries visible
Build 0.7 uses four ancestries; earlier versions used three. Anchor your creation choice to the version you can launch, especially when comparing target skill counts, weapon counts, or features planned for later. A list from an older build is not a missing option in the current creator.
When you report feedback, name the ancestry, background, platform, and build you used. If the character creator behaves differently after a future update, that short context will make your comparison useful. For now, create a character with a readable identity, choose one practical question for the first expedition, and allow the classless growth system to answer the rest through play.
A creation checklist for the first run
Before confirming the character, say the concept in one sentence: a Mossling who wants to understand Bows, a Stonefolk who wants to prepare for dungeons, or a Grimhorn who wants to compare a Magic Path with a weapon. The sentence is not a build restriction; it is a lens that makes the first few choices easier to evaluate. Check that the ancestry is visually readable, the background gives you a story question, and the first expedition has one practical test.
After the first return to Rivermere, decide whether the character’s original question still matters. Keep it if it made the route clearer, or change one layer if the game exposed a different need. That measured adjustment is the strength of the current classless approach. It also gives feedback a useful shape: players can explain which identity they chose, what they expected, what happened in the route, and which change would make the next decision more satisfying. Keep appearance, ancestry, and background distinct in your notes. If a second character feels different because of the visual choices but handles the same route in the same way, that is useful information rather than a disappointment. If the route changes, ask which growth choice caused the difference before assigning it to the ancestry alone.