Understanding the W101 Avalon Quest Tree System
The W101 Avalon Quest Tree is a branching quest progression system that tracks player choices across multiple narrative paths. It was introduced as part of the Avalon content update and quickly became one of the more complex systems in the game. Most players miss half of it on their first run through. I've spent months mapping this out properly. Here's what the manual doesn't tell you. The quest tree doesn't just branch — it has hidden weight values attached to certain decisions. Each choice carries an implicit score that determines which major arcs become available later. I found this out accidentally when I tried to complete the Silver Covenant path and kept getting locked out despite meeting every visible requirement. Turns out I had spent too many points on minor dialogue choices during the first three acts, and it dropped my hidden covenant alignment below the threshold. The system uses three separate tracking variables that are never shown on screen. The primary one is quest completion ratio, which sounds straightforward but isn't. The game counts optional side quests toward this ratio while the official wiki doesn't. I wasted two full playthroughs thinking I needed to complete the main story paths sequentially. You don't. The tree allows parallel progression as long as your accumulated decision weight across acts stays balanced between the three factions: the Crown, the Circle, and the Hollow Court.
I hit a wall around act 7 where the game would silently reset any quest I had flagged as "failed" back to unstarted, but only if I hadn't purchased the corresponding region map from the trader in Blackmoor Keep. This cost me about six hours on a third attempt. The fix was to always buy every available map before accepting any quest, even ones you have no interest in completing. The maps act as flags that prevent rollback on failed objectives.
How the Branching Actually Works
At its core, the tree has fourteen major nodes and roughly forty-two sub-nodes. Each node represents a story beat, and each sub-node is a variation based on prior choices. What most guides skip over is the gating mechanic. Some nodes require you to have completed a specific combination of side content from two different prior nodes. For example, unlocking the Ruins of Tarna quest requires both the Lighthouse Keeper encounter from the Crown path and the smuggler encounter from the Hollow Court path, completed in that order. The timing window matters too. Certain decisions only lock in if you make them before or after specific story markers. I discovered this when a quest I thought would carry over into the next act simply disappeared. It turns out the game checks for completion right before the act transition cutscene plays, and if you haven't accepted the quest yet, it's treated as abandoned permanently. Accept everything early when in doubt. There's also a soft cap on how many parallel branches you can maintain at once. The game handles up to seven active quest lines before it starts silently deprioritizing older ones. If a quest icon stops flashing and you can't track it on the map, it's been deprioritized. You can pull it back by visiting the relevant quest giver in person rather than using the journal fast-travel option. This costs time but is the only way to recover a deprioritized objective.
Get the Full Details
Common Pitfalls That Waste Hours
The most expensive mistake players make is ignoring the faction reputation meter. It's visible in the bottom left corner but most people treat it as cosmetic. It directly gates access to certain nodes in the tree. If your reputation with any single faction drops below neutral, you lose access to that entire branch for the rest of the playthrough. I've seen threads online where people complained about a quest being "bugged" when it was just reputation-gated and the game never notified them. Another issue is the companion loyalty system interacting with the quest tree in ways the documentation doesn't mention. Certain characters will abandon you if you make specific choices, and their departure locks entire quest lines. Kaelen the Ranger leaves if you side with the Crown during the Blackwater incident. After he leaves, every quest tied to his personal arc disappears permanently. Not just the visible ones — hidden story nodes that require his presence die with him. Save spacing is critical here. The game autosaves at major story beats but never after individual decisions. I recommend manual saves before every conversation that offers branching dialogue options. A single bad save can cost you dozens of hours of progress through the tree.
What This System Gets Wrong
For all its complexity, the W101 Avalon Quest Tree has real structural problems. The weight system is opaque and inconsistent. There are documented cases where identical choices produce different hidden values depending on the order they were made. I've compared notes with other players who hit the exact same decision points and got different quest availability outcomes, which suggests there may be some randomized elements baked into the weight calculation that weren't intended. The deprioritization mechanic is another frustration. It makes long playthroughs unreliable. If you spend thirty hours on side content and forget to track down an old quest, you can't go back and fix it. There's no recovery system for missed or deprioritized objectives beyond reloading an earlier save. And the faction lock is harsh. Once you drop below neutral with a faction, you can't repair that relationship at all. There's no redemption quest or reputation recovery mechanic. Some players treat reputation as negotiable when it's actually permanent damage.
If you're starting fresh and want to see everything the tree has to offer, the only reliable method is a dedicated completionist run after you understand the system. It takes roughly eighty to one hundred hours across two or three playthroughs depending on how much time you spend on optional content. There's no single runthrough that captures everything, and no mod or tool currently exists that unlocks the full tree without breaking save integrity.
