Guardian is the most specialised conventional tank: exceptional Threat, Armor Use, Parry, and Mitigation make it the safest class for building a dependable front line.
What the Guardian profile means
Guardian has four weights clustered at the very top of the class table: Threat at 1.8, with Armor Use, Parry, and Mitigation all at 1.7. Vitality follows at 1.5. That is an unusually coherent recruitment profile. A newly generated Guardian is being pushed toward the exact collection of attributes that a front-line defender wants rather than toward a broad assortment of unrelated strengths. The class also has the largest health modifier in the current data, ×1.7, while its damage modifier is only ×0.7. Read that split literally: this is a survival and control chassis.
Attribute weights describe how strongly the class biases a hero’s generated attributes. They are not direct damage multipliers, and a 1.8 does not mean “80 percent more effective in combat.” Use the values to compare likely recruits and to understand why strong Guardians repeatedly appear with similar strengths. The final hero still needs to be judged from the actual sheet.
Recruitment priorities
Start with Threat. Guardian owns the highest recorded Threat weight, so a candidate who misses badly there is surrendering the class’s clearest advantage. Armor Use, Parry, and Mitigation form the next checkpoint. A recruit does not need to win every one of those rows, but a candidate with solid results across all three is more useful than one spectacular number surrounded by defensive holes. Vitality is the tiebreaker when two candidates have comparable control and mitigation.
Discipline, Bravery, Positioning, and Strength sit in the supporting band. They matter, but the class does not need every secondary attribute to be exceptional before it can perform its basic job. Leadership at 1.1 is a mild lean. There is no need to make every Guardian the guild’s social centre. Spellcraft and Healing are both suppressed at 0.3, and Marksmanship is only 0.4. An unusual high roll there is a curiosity; it should not distract from a weak defensive core.
Party role and class pairings
A Guardian gives the rest of the party permission to be specialised. The most natural partners are damage classes that do not want enemy attention: Arcanist, Ranger, and Blademaster. The Guardian’s own low damage modifier makes that division of labour important. Pairing a safe tank with weak damage can produce a group that survives but clears too slowly, so make sure at least one party slot is carrying genuine finishing power.
Any of the three healers can work behind this front line, but they solve different roster problems. Cleric is the direct-healing option, Druid adds support and control, and Bard brings team-oriented utility. Check the synergy table for named bonuses before locking the party; a good attribute match and an active named synergy are separate advantages.
Race fit without overfitting
Races that lean toward Vitality, Armor Use, Resolve, Strength, or Leadership will often score well against the Guardian profile. That makes Dwarf, Goliath, Dragonborn, and Aasimar reasonable pages to inspect first. It does not make every member of those races better than every other candidate. Race tendency is a small directional input, while the hero’s rolled attributes, traits, wage, and the vacancy on your current roster are the decision that actually matters.
Human is also easy to underestimate. Its modest Leadership, Decisions, and Teamwork lean does not maximise the Guardian’s largest numerical weights, but it can support a balanced party member without imposing a severe negative tendency. Use the race recommendations as a shortlist generator, never as an automatic hire rule.
Common mistakes
The first mistake is paying for offence on a class with a 0.7 damage modifier while ignoring a mediocre Threat or Mitigation line. The second is treating the ★ markers as a shopping list that every recruit must complete. Stars mark class-leading weights. They are not minimum requirements. The third is putting two extremely defensive heroes together without checking whether the party can finish fights efficiently.
Finally, do not read old screenshots or remembered values as current truth. This page is tied to the version shown above, and archived builds remain available through the version switcher. If the class changes, compare the numbers in the changelog before applying an older recommendation.
A practical decision rule
For a first pass, reject Guardians whose defining defensive attributes are collectively poor. Among the survivors, favour the candidate with the most even combination of Threat, Armor Use, Parry, Mitigation, and Vitality. Then use traits, wage, age, and party synergies to choose between close candidates. This produces a defender built around the class’s real data instead of a single exciting roll.