Rules edition: Revised 2024 rules (5.5e); the Oath of Hexes is homebrew, not an official D&D subclass. There is no single rules text for this oath: different creators may give it different spells, curses, and features. Before adding one to a campaign, the DM and player should agree on the exact version, how it works beside the chosen Paladin class, and what happens if later play reveals a balance problem.
Start with the Exact Homebrew Version
“Oath of Hexes” is a theme, not a standardized subclass. One version might focus on curses and control; another might add spells, defensive auras, or damage. Never approve a name or summary alone. Read the full document together, including its level requirements, resource costs, durations, saving throws, and any rules for ending or resisting its effects.
Record the source and version you approved. If the player found the subclass online, save a link or copy so everyone is reviewing the same text. If a feature depends on another homebrew rule, identify that dependency too. This small bit of preparation prevents table disputes that sound like rules arguments but are really people using different versions.
Choose the Paladin Rules First
Decide whether the character uses the revised 2024 Paladin or a legacy 2014 Paladin. The class versions differ in features and progression, so a subclass designed for one may not transfer cleanly to the other. Do not combine the subclass with both class versions at once. If you adapt it, write down which class rules apply and make that ruling consistent for the whole campaign.
For a 2024 character, the Paladin gains its subclass at level 3. Review each homebrew feature against what an official Paladin receives at that level and at later subclass levels. A feature that is reasonable at level 15 could overwhelm a level 3 party; a powerful effect may also need a resource cost, a limited duration, or a saving throw to keep it interactive.
Check the Whole Feature, Not Just Its Damage
A curse can affect play in several ways at once: it might reduce an enemy’s options, improve the Paladin’s attacks, help allies, and last across multiple turns. Assess the total effect and its reliability, not only the damage number. Ask practical questions before approving it:
- What does it cost? Identify the action type, uses, recharge, spell slot, or other resource the text actually requires.
- What can resist it? Check its range, target limits, saving throw, condition immunities, and whether the target can end the effect.
- How long does it last? Clarify when the duration ends and whether the Paladin must maintain Concentration.
- What does it combine with? Consider the feature alongside the character’s attacks, spells, subclass abilities, and other party members’ effects.
- Does it create choices? Strong control is easier to manage when enemies have meaningful counterplay and the player must choose when to spend limited resources.
Read ambiguous wording literally before play and agree on a clear interpretation. In particular, check whether a feature calls for an attack roll, a saving throw, or neither; whether it uses an action, Bonus Action, or Reaction; and whether applying a new curse ends an older one. Do not assume that a feature works like the Hex spell unless its text says so.
Watch Action Economy and Concentration
Paladins already make meaningful turn-by-turn choices among attacking, casting, moving, and using class features. A homebrew curse that requires a Bonus Action each round can compete with other abilities even if its damage is modest. A curse that adds damage without requiring a new action may be more powerful than it first appears, especially if it can trigger more than once on the Paladin’s turn.
Concentration deserves equal attention. If a curse requires Concentration, it competes with other spells that use the same rule and can end when the Paladin fails a Constitution saving throw after taking damage. If it does not require Concentration, ask whether its duration and effect are still appropriate. Avoid silently adding or removing Concentration; change the written rule only as an explicit table revision.
Give Enemies Counterplay
Curse-focused play works best when enemies are not reduced to passive targets. Use the approved feature’s actual limits: a successful save, limited range, a short duration, a break condition, or a scarce use may already create fair counterplay. Do not invent immunity just to shut down a character. Instead, vary encounters so that some situations reward the Paladin’s specialty while others ask the group to adapt.
Keep the character’s spotlight in mind, too. If every important foe is immune to the subclass’s signature effect, the homebrew choice feels pointless. If every foe is vulnerable, other characters may have little to do. A mix of enemy types, objectives, terrain, and social challenges lets the concept matter without solving every scene.
Set a Revision Policy Before the First Session
Tell the player how feedback will work. If a feature repeatedly dominates encounters, clarify that the table can revise it after discussing what is causing the problem. If it underperforms, the same process can restore its intended fantasy without making the character feel punished. Agree whether changes take effect immediately, between sessions, or after a short playtest.
When changing a feature, alter one problem at a time and keep a note of the old wording. That makes it easier to tell whether a fix helped. Avoid balancing by piling on arbitrary drawbacks—such as narrative stigma or extra resource costs—that were not part of the agreement.
Roleplay the Oath Without Forcing an Alignment
A curse-themed Paladin does not have to be evil. The character might believe curses are a measured sentence for serious harm, a way to protect a vulnerable community, or a sacred duty accepted at personal cost. Work with the player to define who or what grants the oath, what conduct violates it, and whether the curse has visible signs or social consequences.
Ask the group how dark themes should appear in play. A character who curses enemies can create strong drama, but the player should know whether the campaign treats that magic as frightening, ordinary, or forbidden. Use the answer to shape scenes and relationships—not to take control of the player’s choices.
Official Alternatives if Homebrew Is Not a Fit
If the table does not want new mechanics, consider an official Paladin subclass whose published features already support the desired story, or describe an existing Paladin spell and feature as a curse while leaving its mechanics unchanged. Cosmetic descriptions still follow the feature’s normal range, targets, action, and duration. That approach keeps the character concept while avoiding a balance review of a new subclass.
For a character build using a particular Oath of Hexes document, the advice depends on that document’s actual text. Keep its version available at the table and ask the DM before choosing feats or spells that rely on how a curse feature works.
Related Paladin Guides
For current class progression and official Paladin features, see our Paladin guide. If your character is using an official oath with a curse-like theme, our 2014 Paladin Multiclass Guide can help compare class choices; verify that any linked build reflects the same rules edition as your campaign.
