Scope: This is a homebrew concept and design guide, not an official subclass or a set of playable rules. No specific Oath of Hexes rules text or creator is identified here, so the name does not imply a standard spell list, Channel Divinity, aura, or capstone. Choose either the 2014 or revised 2024 Paladin as your rules framework, and review the exact homebrew document with your DM before using it.
A Paladin whose vows bind fate, punish wrongdoing, or carry a curse can be a compelling character concept. The theme alone does not determine how the character works mechanically. One creator might write a subclass around protection, another around control, and another around a single-target mark. Treat each document as its own homebrew option rather than assuming that features described under the same name are interchangeable.
Start with one design promise
Before drafting features, describe the oath in one sentence. For example: “This oath makes the Paladin a patient pursuer who marks one foe and helps the party keep pressure on that target.” That sentence is a design goal, not a feature. It gives the writer and playtest group a way to decide whether an ability belongs in the subclass or is merely an attractive extra.
Decide what the curse means in the setting. Is it a vow witnessed by a deity, a fey bargain, a consequence of breaking a sacred law, or a metaphor for relentless pursuit? These are narrative choices. They need not impose an alignment, require an evil patron, or make every Oath of Hexes character behave alike.
Choose one Paladin rules framework
Write the rules version at the top of the homebrew document. A subclass designed for the 2014 Paladin should not silently borrow revised 2024 class features, and a design for the revised class should not assume that older character options work unchanged. If a group intentionally adapts a feature across versions, record the adaptation and use it consistently.
- 2014 rules: use the legacy Paladin class and its subclass progression as the baseline. The 2014 Divine Smite is a class feature triggered by a qualifying melee weapon hit; it is not a bonus-action spell.
- Revised 2024 rules: use the revised Paladin class. Divine Smite is a spell with a bonus-action casting time, so a homebrew ability that also uses a bonus action competes for that turn’s bonus action.
Those are different class frameworks, not interchangeable descriptions of the same action economy. The class and spell references below are official starting points; they do not contain an Oath of Hexes subclass.
Write complete rules before judging balance
A title such as “Curse of Binding” is not enough to evaluate an ability. Each draft feature should say who can use it, what action or resource it costs, which target it affects, what roll or saving throw is involved, how long it lasts, and how it ends. If the feature depends on a condition, define how that condition is applied and whether it can affect a creature more than once at a time.
Keep each effect legible at the table. If an ability both weakens an enemy, strengthens allies, adds damage, and lasts after the target drops, playtesters may struggle to identify which part is doing the work. Begin with the smallest version that delivers the design promise; add complexity only when a test reveals a specific gap.
Check the whole turn, not just the damage
Curse-themed effects often interact with attacks, spells, Concentration, and party tactics. During review, record when the Paladin can apply the effect and what they give up to do so. Check whether it uses an action, bonus action, reaction, Channel Divinity, spell slot, or another resource. Then test the exact rule alongside the selected Paladin class, rather than assuming all Paladins have the same choices on a turn.
Evaluate the total impact, including accuracy changes, movement limits, saving-throw penalties, damage, duration, and benefits granted to allies. Ask how an affected creature can resist, end, or play around the effect. Avoid stacking several strong penalties without a clear limit, and do not call an ability “balanced” solely because it deals little damage.
Build a playtest that can answer a question
Write down a test question before the session: “Does the mark create a meaningful target choice?” is more useful than “Was the subclass fun?” Try more than one encounter shape, such as a single durable foe and several weaker foes. Note how often the signature feature is used, whether it crowds out the Paladin’s other class features, and whether the rest of the party still has useful decisions to make.
Change one part of the draft at a time. If the feature is rarely used, find out whether its cost, trigger, range, or effect is the obstacle before increasing its power. Keep the version number and date on each playtest copy so the group is discussing the same rules text.
Use official options as references, not templates
Compare the draft with published Paladin subclasses from the same rules version and at a similar character level. Look at how those options divide their identity among spells, limited-use features, defensive support, and later improvements. A comparison can reveal whether a draft is unusually broad or reliable, but it cannot prove balance by itself: playtesting and the exact wording still matter.
If the group wants the theme without new mechanics, consider describing an existing oath’s features as curses while leaving their rules unchanged. The official Oath of Vengeance, for example, can support a relentless-pursuer story. Cosmetic changes still need the DM’s agreement, but they avoid introducing a new rules subsystem.
Questions for the character and the table
Use these prompts to give the concept a distinct voice: What promise did the Paladin make? Who witnessed it? What would count as justice rather than revenge? Can the oath be fulfilled through mercy, or only through punishment? What does the Paladin do when the target is innocent, the evidence is wrong, or the party chooses a different course?
Agree on the answers that matter to the campaign before play. A curse can be unsettling without taking control away from another player, forcing a character’s choices, or turning every disagreement into a threat. The DM and player should set boundaries for themes such as coercion, body horror, or supernatural punishment.
For a Dungeon Master’s approval checklist—including how to record a specific source version, review counterplay, and set a revision policy—see the Oath of Hexes campaign guide. That article addresses whether to allow a supplied homebrew document; this page focuses on shaping and testing the concept.
