Independent player guide

Hero Siege Quests Guide

Use questgiver and chain groupings as navigation, not as a guaranteed unlock order; prioritize quests that overlap your current act and verify rewards in the live Journal.

FocusNavigate by act, questgiver, chain, and the objective currently tracked in game.
FormatReference Page
Current boundarySeason and date labels stay attached to changeable details.

How should a player use a Hero Siege quest list?

Filter by questgiver, act and chain, then confirm the active objective in the in-game quest tab.

  1. Questgiver, act, and chain are navigation filters, not a guaranteed universal unlock order.
  2. After narrowing the list, compare the selected quest with the active objective shown in the quest tab so similarly named steps do not get combined.
  3. Start by identifying the current act, then the questgiver, then the chain name.

That narrowing makes the live quest-tab objective the deciding text rather than an external list order. If the objective belongs to Hunger Issue, Seething Souls, or Village of Lamia, the dedicated page can continue the task. A list entry without a matching active objective is navigation context, not proof the quest is available.

Which quests are worth doing?

Start with quests that naturally overlap campaign progression and provide a needed reward, without claiming every side quest is mandatory.

  • Prioritize a quest when it overlaps the current campaign route and offers a reward the character actually needs.
  • That rule supports a practical choice without claiming that every side quest is mandatory or that one reward has equal value for every build.
  • Campaign overlap reduces detours, while a needed reward gives the side task a reason tied to the current character.

Both conditions should be considered without assigning a fixed value to a reward this page does not document. The live Journal can confirm the reward before the player commits. A quest outside the current act or without a useful outcome may remain optional without being labeled bad.

What if a quest is not showing?

Check act progress, questgiver, tracked state and whether a similarly named step belongs to another chain before treating it as a bug.

  1. When a quest does not appear, check act progress, the expected questgiver, tracked state, and whether the name belongs to another chain.
  2. Those checks distinguish a progression mismatch from a display problem without inventing an unlock requirement.
  3. Act progress tests whether the chain is ready, the questgiver check tests whether the correct start point is being used, and tracked state tests whether the objective is already active.

Similar names can send a player into the wrong chain, so compare the exact title last. When all four checks align and the quest remains absent, the guide cannot safely infer a secret prerequisite or universal bug.

A quest list works like an index, not a script. The player supplies current act and active chain, the list narrows likely entries, and the quest tab confirms the objective that actually matters. Reward desirability then affects priority without rewriting availability. When no matching entry appears, act progress, questgiver, tracked state, and exact naming are the four observable branches. This approach also explains why the dedicated Hunger Issue and Seething Souls pages begin by checking the active task: instructions for a correctly named but inactive step cannot create progress. Village of Lamia remains an area reference until the live quest supplies more context.

Treat availability and priority as two separate decisions. Act, questgiver, chain, and the tracked objective answer whether the player is looking at the right task. Campaign overlap and a currently needed reward help decide whether an available side quest deserves attention now. A desirable reward cannot make an unavailable quest active, and an active side quest does not become mandatory merely because it appears in an index. When a title is missing, check the broader act and chain before comparing similar names; that order prevents a neighboring objective from being mistaken for the target. If every visible field agrees yet the task remains absent, the guide stops before any secret prerequisite or universal bug claim. The dedicated quest pages continue only after the exact active objective is known, while the Village page supplies bounded area orientation rather than a complete chain. This division keeps navigation useful without turning partial community listings into a fixed walkthrough or reward database.

Before you rely on this guidethis page is navigation by act, questgiver, chain, and active objective, not a complete reward table or guaranteed unlock order. Quest visibility and reward details must be read from the current in-game quest tab or Journal; a similarly named step may belong to another chain, so identify the tracked objective before treating absence as a bug.