Sovereign Tower Quest Scoring Explained

Sovereign Tower does not simply ask whether your strongest knight meets a Strength number. Wild Wits calculates a party score for each Round Table card — community launch data covers roughly 312 quests — and that score decides Critical Success, Great Success, Success, Failure, Major Failure, or Critical Failure. Curve Games’ solo RPG launched August 6, 2026; Patch 1.0.8 (August 11) reduced weaker-stat penalties and raised overlevel bonuses, so margins feel friendlier, but the skeleton of the formula remains the same.

This page explains the post-launch scoring model used across guides on this wiki. Pair it with Quest Outcomes for debrief labels, Quest Success Tips for workflow, and the Knight Quest Matcher for quick shortlists.

Score starts at −10

Every quest begins with a base score of −10. From there the game adds contributions for:

1. Party presence (requested seat count)
2. Stat averages versus listed requirements
3. Favourite meals eaten this cycle
4. Efficient / inefficient traits (and some gear-granted traits)
5. Signature knight attributes and special outcome overrides

A powerful knight can still be dragged down by a weak teammate. Balanced parties often beat one superstar plus passengers.

Mastering Round Table quests in Sovereign Tower

Send the requested number of knights

Check party size before you look at relics.

If a quest asks for 3 knights, sending exactly three matters because presence contributes to the score. Each assigned knight contributes roughly:

10 ÷ requested party size

When you send the full requested count, presence alone lifts the starting −10 back toward 0. Sending extras is not always better — another weak body can lower party averages. Sending fewer than requested leaves presence unfinished and usually hurts.

Meeting the required stats

Cards may list STR, AGI, CHA, MAG, WIT, and LCK (Luck). The game looks at the party relative to each requirement, not only the highest individual value. Community notes approximate a per-stat contribution near (average − requirement) × 0.66, with final effective stats clamped to 0–15 after gear.

Exactly meeting a requirement still yields a small positive (~+0.22) rather than zero. Falling short hurts more than overshooting helps on a single line — cover every listed check.

Patch 1.0.8 softens the pain of under-level stats and rewards overleveling more, which makes training ground cycles and careful XP more valuable late Act 1.

Meals add +0.5

A knight who ate a favourite meal during the current cycle contributes about +0.5 to the quest score on top of the affinity gain (~+1.5). Near a threshold, Kitchen snacks can flip Failure into Success. Full dish tables live on Cooking. Chester and Dulahan like every dish — easy score insurance once recruited.

Traits secretly matter (±1)

Quest conditions and categories apply flat +1 or −1 per matching trait per knight. The UI rarely spells these bonuses out, so they feel invisible.

Examples of condition tags: Flying Creature, Water, Cute Creature, Climbing, Woods, Crowd, Cave, Ghost, Track, Big Creature, Magic Ritual, Heavy Lifting, Investigation, Help, At Night, Musical, Unethical, Dragon, Need Flying Mount, Intimidation, People Involved.

Category examples:

Category	Efficient trait ideas	Traits that often hurt
Hunt	Hunter, Predator, Swordmaster, Hunting Bow	Animal Lover, Inattentive
Assassination	Killer, Deadly Weapon, Sadistic	Kind-Hearted, Naive
Diplomacy	Popular, Patient, Kind-Hearted	Intimidating, Arrogant
Scouting	Tracker, Finder	Clumsy, Inattentive
Relic Recovery	Resourceful, Patient	—

Equipment can grant traits you do not naturally have. That is why forge and alchemy timing belongs in the scoring plan, not only in the gear checklist — Annexes, Attributes.

Outcome bands

Score	Result	Gold	Damage pattern
≥ +10	Critical Success	×2	None
> +5	Great Success	×1.5	Roughly halved
> 0	Success	×1	Low
≤ 0	Failure	Failure path	At least some
≤ −5	Major Failure	Failure path	Higher minimum
≤ −10	Critical Failure	Failure path	Party can die

Only gold receives the Great/Critical multiplier. Relics, consumables, mounts, faction deltas, and satisfaction changes stay at face value. Do not chase Critical Success solely to “double a sword.”

Special outcomes override the normal path

Some quests list knight-specific special outcomes. The game checks those triggers in order; the first match wins and replaces the normal reward package. Triggering a special outcome often means giving up the gold and satisfaction you would have earned on a plain Success. Always scan special lines before optimising raw score — Quest Outcomes.

Emergency and deadline quests

Emergency cards and short deadlines compress the formula. You may lack time to cook, craft, and investigate. Prioritise presence + hard stats, then traits. The Grest pirate emergency gained +1 cycle in Patch 1.0.8 — see Grest Pirates — but other timers still punish slow kitchens.

Practical scoring workflow

1. Read party size, duration, and damage band.
2. List every stat requirement, including Luck.
3. Check special outcome names first.
4. Build a party that hits presence without tanking averages.
5. Stack efficient traits; remove inefficient ones if seats allow.
6. Feed favourites and equip trait-granting gear if the margin is thin.
7. Confirm with Quest Matcher, then lock the cycle.

Related reading

• Round Table — UI and assignment timing.
• 20 Tips — habits that feed good scores.
• Beat the Dragon Knight — spike exam for the formula.
• Systems Hub — mechanic index.

Treat scoring as readable pressure, not RNG superstition. When a debrief surprises you, ask which term of the formula moved — presence, average, meal, trait, or special override — before you blame the dice.