quests.xml is a small change (about 200 lines), but there are changes that take effect at the attribute level. There are no renames of existing quest ids.
Key Changes
Routing / Onboarding
- Added
starter_quest="quest_whiteRiverCitizen1"to<quests max_quest_tier="6" quests_per_tier="10"> - Added
<action type="SetCVar" cvar="StarterQuest" value="1">toquest_whiteRiverCitizen1
New attribute filter_tags (most important)
- Added
<property name="filter_tags" value="poi" param1="filter_tags"/>to many POI-clearing quests (either alongside the existingextra_tags="", or as a replacement) - For
buriedquests, usefilter_tags value="buried" param1="extra_tags"(note the param1 setting)
Guards for trader-to-trader quests
- Added the
cvar="IntroComplete,TraderToTraderQuests"attribute totier2_nexttraderthroughtier5_nexttrader, along withquest_hint_requirement="BiomeProgression"
Other
- New dev quest
test_bandit(not intended for production use)
Impact on MODs
- Since there are no renames of existing quest ids, xpath that targets ids is generally safe.
- However, if you are using setattribute/replace on the same quest / quest_list, the mass addition of
filter_tagsor the addition ofcvar=guards can cause hunk offset drift or duplicate attribute definitions. - Because of the
cvar="IntroComplete,TraderToTraderQuests"guard, the nexttrader quests won’t appear if TraderToTraderQuests is disabled in the sandbox. If your trader routing depends on this, check the default value.
Reference: Example Diff
- <quests max_quest_tier="6" quests_per_tier="10">
+ <quests max_quest_tier="6" quests_per_tier="10" starter_quest="quest_whiteRiverCitizen1">
<property name="extra_tags" value="" param1="extra_tags"/>
+ <property name="filter_tags" value="poi" param1="filter_tags"/>
- <quest id="tier2_nexttrader"/>
+ <quest id="tier2_nexttrader" cvar="IntroComplete,TraderToTraderQuests"/>
*Based on investigation immediately after applying the experimental version (equivalent to B252).
Related: List of MOD Development Articles