Rules scope: This is a homebrew NPC and encounter-design guide. It combines selected legacy Goblin traits from Volo’s Guide to Monsters with selected 2014 Barbarian features. It is not an official Goblin stat block, and adding character-class features does not automatically give an NPC a balanced challenge rating.
Decide what this enemy is for
A Goblin Barbarian can make a useful named guard, rival, or short encounter centerpiece when the players have a reason to care about the outcome. Decide the enemy’s objective before choosing its combat features: protect an escape route, hold a bridge until allies retreat, capture a trespasser, or bargain for the safety of a community. A clear goal gives players alternatives to reducing the NPC to zero hit points.
Do not treat the playable Goblin traits as the same thing as the official Goblin monster stat block. Choose the monster statistics that fit the encounter, then identify any player-race or Barbarian features you are adding as homebrew. A custom creature should have a role, limits, and a difficulty estimate; the phrase “2nd-level Barbarian” alone does not supply those.
Build a simple, transparent stat block
For a quick NPC, start from an existing creature stat block that is close to your intended threat. Keep its listed Hit Points, Armor Class, attack bonus, damage, and challenge rating together unless you are intentionally rebuilding the monster. If you add Rage resistance or a stronger attack, reconsider the whole encounter rather than assuming the original rating still applies. The 2014 Dungeon Master’s Guide gives a process for creating monsters; the Basic Rules explain how to estimate combat-encounter difficulty.
Use only the mechanics that matter to the scene. A compact version might have:
- One defensive feature: If you add 2014 Rage, say when it begins and track its limited uses. Rage grants resistance to bludgeoning, piercing, and slashing damage while it lasts, subject to its rules; it does not make the NPC invulnerable.
- One movement feature: Legacy Nimble Escape lets a Goblin take Disengage or Hide as a bonus action. Both it and entering Rage require a bonus action, so the NPC cannot use both on the same turn.
- One offensive choice: Reckless Attack can grant advantage on the NPC’s Strength-based melee weapon attack rolls for that turn, while attack rolls against it have advantage until its next turn.
Do not assign arbitrary hit points, armor class, or “survives four to six hits” expectations from party level alone. Compare the final statistics and number of enemies with the encounter-building guidance, account for the party’s resources and terrain, and adjust after play if the fight is consistently too dangerous or too easy.
Make the terrain create choices
Small size does not let a Goblin pass through every narrow opening or ignore movement rules. Describe actual cover, routes, and obstacles, then use the table’s movement and hiding rules. A low wall might give cover; a side tunnel might be passable only by smaller creatures; a climbable scaffold might offer a slower route to an elevated position. Give the party ways to respond, such as blocking an exit, using a ready action, negotiating, or drawing the NPC away from its objective.
Use Nimble Escape for a specific purpose. Disengage can help the NPC move without provoking opportunity attacks that turn. Hide requires appropriate conditions, and the DM decides whether the Goblin can be concealed. Neither action guarantees that the party loses its turn or cannot pursue. Rage also has an upkeep condition in the 2014 rules: if the Barbarian’s turn ends without it attacking a hostile creature or taking damage since the previous turn, the Rage ends.
Keep the encounter fair and readable
Show the players what the NPC is trying to do and what its special features look like. If it retreats, make the route visible and give the party a way to intercept or follow. If the creature is meant to return later, establish how it escapes and what cost or consequence the party can impose. Avoid adding an unannounced fear effect, automatic escape, or extra reaction just to force a planned scene.
Account for action economy. Several low-level enemies can be more dangerous than one stronger enemy because they make more attacks and can surround characters. If the Goblin has allies, give them simple jobs—guarding a door, trying to free a prisoner, or using ranged attacks from a clear position. Do not give every ally the same resistance and mobility package without recalculating the encounter.
Give the Goblin a reason to fight
Build a person, not a stereotype. The NPC might be protecting someone, defending a chosen home, seeking payment, or trying to avoid a fight while saving face. Decide what would make them stop, surrender, or accept a deal. Let the players discover those motives through what the Goblin says and does, rather than assuming all Goblins share one culture or personality.
Rewards should follow the encounter and the NPC’s resources. A personal token, useful information, a key, or a captured map can be more appropriate than a high-value magic item. Keep treasure separate from challenge rating: do not promise that a particular NPC level or rating guarantees a specific reward.
