What a first descent should answer
Do not enter a dungeon with a build that exists only on paper. Bring one weapon question, one preparation question, and one way to recover when the route pushes back. The Slurpers Den gives the current demo a named test space with a mushroom theme, and three additional dungeons broaden the comparison. That variety is enough to encourage experimentation, but it does not establish one structure for every dungeon.
A first descent can succeed even when it ends early. Learn how the party reads danger, which supplies matter, and whether the current weapon or Magic Path supports the route. If the group returns with a clear next experiment, the run produced useful progress. The pressure comes from deciding how much of the route to spend before turning back, not from pretending that every room must be cleared in one attempt.
Prepare through the whole village loop
Gathering, crafting, cooking, and upgrading form the preparation loop. Use them as linked decisions rather than four chores. Gather what the next route can realistically provide, cook or craft when it changes your readiness, and upgrade when you understand which weakness is costing the party time or recovery. A player who carries every possible material may be less prepared than a player who knows why each item is in the pack.
The party should agree on a stop rule before the descent. Decide what resource loss, route complication, or injury makes a return to Rivermere worthwhile. Solo players can use the same rule by marking the last safe point mentally; groups can call it out before the pressure rises. The point is to turn retreat into an expected part of the expedition rather than an embarrassing surprise.
Leave room for encounters
The wider region includes travelling NPCs, random encounters, and ambushes. A dungeon plan that assumes an uninterrupted walk will be fragile, because an encounter can spend supplies or change the party’s attention before the entrance. Keep a simple fallback: who calls the retreat, who carries the shared materials, and which player watches the route while the others act.
Party scaling may add enemies rather than simply increase enemy health. Test that pressure in the playable build, then plan around the result: more bodies do not remove the need to notice threats, agree on a target, and preserve a way out.
Let the build serve the dungeon
The classless system lets the dungeon teach you what to value. A weapon can answer a spacing problem, Dungeoneering can make the route itself part of the build, Survival can support a longer trip, and a Magic Path can provide a different answer to pressure. No damage hierarchy is established, so judge a choice by whether it makes the next decision clearer for the party.
If you are learning with friends, assign questions rather than rigid roles. One player can watch the route and supplies, another can test close pressure, and another can compare a Magic Path. Group XP and scaling difficulty mean that learning can be shared, but communication still matters. After the run, keep one observation and change one thing; that creates a clean comparison for the next dungeon.
Return with a useful next step
A dungeon run should end with a better plan, whether the party reaches the deepest room or decides to leave. Sort the materials that change preparation, note the encounter that consumed the most attention, and decide which skill or weapon question deserves the next test. A village return is part of the loop because it turns an uncertain expedition into a deliberate next departure.
The demo’s named locations and encounter pressure make that loop visible without sealing the full game’s future content. Use the current scope to decide what you can explore now, treat untested tactics as provisional, and keep future release windows separate from the next descent. The best dungeon guide is not a perfect route; it is a habit of learning before the next descent.
Brief the party before the door
A short briefing prevents most avoidable confusion. Name the dungeon, the reason for entering, the resource that must be protected, and the signal for turning back. Then ask each player what they are testing: a weapon, a Magic Path, preparation, or route awareness. This keeps a classless party flexible while giving every decision a job. If the group cannot explain why it is carrying an item, that is a reason to simplify the pack before the descent.
After the first room or major encounter, take a deliberate pause. Compare the cost of the route with the information gained and decide whether to continue. The pause is especially valuable when scaling adds more enemies in co-op, because a party that rushes after an easy opening can spend recovery before it understands the real pressure. A good briefing does not remove surprise; it makes the party able to respond to it together. Mark the first room that changed the plan, not only the room that caused the most damage. That detail tells you whether the problem was enemy pressure, route choice, missing preparation, or unclear communication. Bring that answer back to Rivermere, then change one part of the kit before the next descent so the following run can teach you something new.