What are Requirements?

A requirement is a condition the character must meet for an entity to be usable. The level-up wizard evaluates them automatically and greys out feats, classes, or spells that don't qualify.

Each requirement leaf has three parts: target (a path into the character sheet), operator, and value. Examples:

• abilities.strength.total >= 13 — Strength of 13 or more (Power Attack's prerequisite).

• combat.bab >= 1 — base attack bonus of +1 or more.

• feats.powerattack.possessed == true — has the Power Attack feat.

• classes.fighter.level >= 4 — Fighter level 4 or higher.

• skills.tumble.rank >= 2 — at least 2 ranks in Tumble.

The path is built using the target path browser in the requirement editor.

Multiple requirements on the same entity are AND'd together by default. To express OR, add a chain (group) node and place leaves under it.

Cleave needs Strength 13 AND Power Attack — two leaves, both must hold:

• abilities.strength.total >= 13

• feats.powerattack.possessed == true

A feat that accepts either Martial Weapon Proficiency OR a per-weapon variant uses an OR chain with two leaves under it:

• feats.martialweaponproficiency.possessed == true

• feats.martialweaponproficiencylongsword.possessed == true

Nested groups are supported — useful for prerequisites like (Dex 13 AND Improved Unarmed Strike) OR Monk level 1.

Common targets:

The slug is the entity name lowercased with separators stripped — Power Attack becomes powerattack, Knowledge (Arcana) becomes knowledgearcana.

Requirements gate eligibility. They don't model selection rules ("must pick at level 1") — that's handled by aptitudes and class-granted feats. They don't apply at runtime in combat — they're evaluated when the level-up wizard previews choices.