FAST ANSWER / QUEST TIMING
Treat the least reduction as the current lead, not a rule.
One recent community reply reports that a party with -1, -2, and -2 cycle effects behaves like -1 cycle. That is a useful test case, but it has not been independently verified here and should not be treated as a universal stacking formula.
- Record the same quest, base duration, party, equipment, and build before dispatch.
- Run a baseline, then compare a party with one reduction against a mixed -1 / -2 / -2 party.
- Repeat after restoring the same state before publishing a general rule.
Patch 1.1.1: Silver Cat mount reduction
Official fix: a mount could fail to reduce The Silver Cat's duration. This does not establish a stacking formula. Update before comparing the same assignment; broader stacking claims remain unverified.
What the recent report actually says
A player asked whether quest-duration reductions stack across the whole party. Multiple replies used a -1, -2, -2 party as an example that only shortens the quest by one cycle, with the slowest member effectively setting the party result. Other reports mention mounts that do not visibly reduce time, an unchanged interface, and an Alwena long-quest issue. This is a set of conflicting community observations, not an official mechanic explanation or an independently verified formula.
- Keep the wording as a lead: 'reported to use the smallest reduction'
- Do not rewrite the claim as additive stacking
- Compare passive traits, mounts, and visible UI separately
- Record whether the effect appears before dispatch or only after the quest returns
Patch 1.0.11: some ultimatum durations are fixed
The official 1.0.11 notes fix some ultimatum quests whose duration was higher than one cycle. That is a quest-specific correction, not evidence that all reduction effects stack additively or that every long quest is a bug. Check the quest's visible duration in the current build before comparing party effects.
- Fixed: some ultimatum quests exceeding one cycle
- Compare a corrected ultimatum quest with an ordinary duration-reduction test
- Record the displayed estimate and the actual return cycle
- Keep the stacking rule marked community report / verify in build
- Evidence state: official patch note / universal formula unavailable
Latest lead: the slowest member may set the result
The practical lead is that one unmodified knight can prevent the party from receiving the full benefit of the other reductions. That would make a full-party setup more important than stacking one strong mount or item on a single knight, but the current public evidence does not establish whether every reduction type behaves the same way.
- Compare -1 / -2 / -2 with -1 / -1 / -1
- Test a party where every member has a reduction
- Keep the same quest, base duration, and party size
- Record whether knights return together or on separate cycles
Why this matters for dispatch decisions
A shorter quest can change which knight is available for the next request, but speed is not automatically the same as a better result. Keep duration, outcome class, relationship cost, and resource reward in separate columns so a faster failure does not look like an upgrade.
- Quest duration before and after the party change
- Critical Success, Critical Failure, or Unexpected Outcome
- Relationship, armor, treasury, or item changes
- Whether the next quest board or character state changed
The minimum useful verification
Use one quest with a repeatable base duration. Keep the preceding day, quest choice, equipment, and party order unchanged. Test one reduction, then the mixed party, then a party where every member has the same reduction. If the result changes after any unrelated variable moves, mark the interaction unresolved.
What will change when it is verified
Once the behavior is reproduced in the current build, replace the community-report label with an in-game verification label, add the exact quest and build, and link the result from the knight roster. Until then, use this page to prevent a costly assumption rather than to promise a fixed formula.
SEARCH QUESTIONS / SHORT ANSWERS
Common questions
Did Patch 1.0.11 fix long Sovereign Tower quests?
It fixed some ultimatum quests that lasted longer than one cycle. That does not establish a universal reduction or stacking rule, so compare the visible duration and actual return cycle in build 1.0.11.
Do quest duration reductions stack in Sovereign Tower?
A community report says a mixed -1 / -2 / -2 party may behave like -1, but the interaction is not independently verified. Test the same quest with a baseline, mixed party, and matching reductions before relying on it.
Why does my Sovereign Tower quest take too long?
First compare the displayed duration with the actual return cycle and check whether the quest is one of the ultimatum cases addressed by Patch 1.0.11. Then test party reductions separately; a single community report does not prove that reductions stack additively.
Baseline source: official Sovereign Tower page on Steam. Additional reference: official Patch 1.1.1 notes. / recent community discussion on knight stats and quest duration. / official Patch 1.0.11 notes. This note is an independent editorial guide; evidence status is shown where it matters. Last checked: September 19, 2026.
September 19: added the relevant official 1.1.1 fix; old-save recovery and wider route conditions remain unverified.