Goliath Paladins work with the published rules; a table does not need house rules to make the character effective. If your group wants a different feel, agree on one specific change and test it with everyone’s input.
Rules edition: examples in this guide refer to the legacy Goliath from the 2014 Elemental Evil Player’s Companion and the 2014 Paladin. Every change below is optional homebrew, not official rules. The 2024 Goliath has a different trait package; do not combine its Giant Ancestry or Large Form with 2014 traits unless the DM deliberately approves a mixed-rules character.
Start with the table’s goal
Before changing a trait, describe the play experience you want: fewer reaction conflicts, more chances to use a defensive feature, more physical stunts during exploration, or a clearer character theme. Then make the smallest change that addresses that goal. A benefit used every round can affect encounter balance more than a rare narrative option, even if the die roll looks modest.
Possible changes to discuss
Change when Stone’s Endurance is used
The 2014 Stone’s Endurance uses a Reaction after you take damage and reduces that damage by 1d12 plus your Constitution modifier. One optional table rule is to let the player decide after seeing the damage total, before applying the reduction. This reduces guesswork while keeping the Reaction and use limit. It makes the feature more reliable, so the DM should consider that when planning difficult encounters.
A larger change is removing the Reaction requirement. That frees the character to use an opportunity attack in the same round and raises the trait’s power. Try it only if the group agrees that this is the goal, and review it after a few sessions.
Adjust the number of uses
In the legacy rules, Stone’s Endurance recharges after a Short or Long Rest. A DM might choose a different rest schedule to match the campaign, but changing it to multiple uses per Long Rest is not automatically a small adjustment. Compare how many encounters the group has between rests and how often the player currently gets to use it. Set a clear limit and revisit the choice if it prevents meaningful danger or feels irrelevant.
Keep Powerful Build within its printed scope
The 2014 Goliath’s Powerful Build counts the character as one size larger for carrying capacity and for the amount they can push, drag, or lift. It does not make the character larger for grappling, shoving, weapon reach, or attack damage. If the table wants a special contest or feat of strength, the DM can resolve that situation using the normal rules or approve a specific one-off ruling. Extending the trait to grapple larger creatures is a substantial homebrew change and should be written down before it affects a combat.
Avoid stacking several buffs at once
Adding a bonus to damage reduction, extra uses, advantage on unrelated checks, and broader size benefits together can make one character’s defenses and utility much stronger than the rest of the party’s. Test one change at a time. Record the exact wording, when it applies, what resource it costs, and whether it replaces or adds to an existing feature.
Make the agreement clear
- Get the DM’s and players’ agreement before the character relies on a change.
- Write down the trigger, action or Reaction cost, use limit, and reset condition.
- Use the same ruling for comparable characters and situations.
- Set a review point after a few sessions; adjust or remove the change if it crowds out other characters or creates repeated disputes.
For an edition-separated build using the published options, see the Goliath Paladin build guide. For character history and campaign development, see the backstory guide and character-growth guide.
Official Rules Sources and References
- D&D Beyond legacy Goliath rules.
- D&D Beyond Basic Rules (2024), Character Origins — current species and background rules.
- D&D Beyond Basic Rules (2024), Character Classes — current Paladin rules.
- D&D Beyond Basic Rules (2014), Classes — legacy Paladin rules.
Consult the 2014 source your table uses for the legacy trait text. This article describes optional table changes; it does not replace the official rules.
