D&D 5e Rules & Adjudication Questions for Dungeon Masters

Yes, a familiar can be captured while it is physically present, but a familiar created by Find Familiar is unusually difficult to keep kidnapped. The spell makes the familiar a creature that acts independently and obeys its summoner, so ordinary restraints, cages, grapples, or similar fictional obstacles can affect it when their rules apply.

The important limitation is the summoner's control over the spell. Find Familiar lets the caster use a Magic action to dismiss the familiar temporarily to a pocket dimension, and the spell does not make that dismissal depend on the captor's permission. If the familiar is reduced to 0 hit points, it disappears as well and can return after the spell is cast again. Anything the familiar was wearing or carrying is left behind when it disappears.

That means a kidnapping works best as a short-term complication, not as a way to permanently confiscate the character's class or spell feature. A villain might seize the familiar to steal what it carries, force an immediate choice, or exploit a moment when the caster cannot act. If the plot requires a longer captivity, establish a specific magical reason rather than quietly removing the spell's escape options.

No. Under SRD 5.2.1, Cone of Cold is not a valid contingent spell for Contingency even though its range is Self. Contingency requires a spell of 5th level or lower with a casting time of one action that allows you to choose yourself as its target, and it further states that the contingent spell affects only you.

Cone of Cold has a range of Self because the cone originates from you, but its effect is directed at creatures in the 60-foot cone: those creatures make Constitution saving throws and take the cold damage. The range entry identifies where the area originates; it does not make you the spell's sole target.

That distinction matters for other “Self” spells too. Some spells genuinely affect the caster, while others use Self to define the origin of an area or emanation. Contingency works with the former when the other requirements are met, not automatically with every spell whose range line says Self.

At the table, I would explain the ruling in those terms rather than as a balance exception: Cone of Cold cannot become contingent because the spell's effect is on creatures in its cone, while Contingency restricts the stored spell to affecting you.

Destroying the floor does not automatically end Magic Circle under SRD 5.2.1. The spell creates a magical cylinder centered on a point on the ground, lasts for its stated duration, and does not include a rule saying that damaging or removing the surface dispels it.

If the spell is reversed, a creature of the chosen type is prevented from leaving the cylinder. The runes appear where the cylinder intersects the ground or another surface, but those markings are a description of the effect, not a stated object that can be broken to terminate the spell.

The awkward case is what happens after the floor disappears. The spell does not explicitly explain whether its original point remains fixed in space or how an unsupported creature interacts with the bottom of the cylinder. That geometry is a GM adjudication, but it is different from saying the spell itself has been destroyed.

If you want the possessing spirit to discover a structural loophole, make that a house rule or encounter feature and signal it before the reveal. For example, cracks could disrupt the visible runes or the party could learn that this version of the binding depends on an intact boundary. Then the escape becomes counterplay the characters could anticipate rather than a surprise exception to the spell.

No. Appearance does not determine Charisma, and a frightening character can have high Charisma. SRD 5.2.1 describes Charisma as measuring confidence, poise, and charm; those qualities can produce persuasion, command, intimidation, or presence without requiring the character to be conventionally attractive or pleasant.

Likewise, a low Charisma score does not require a stutter, illiteracy, or any specific disability. The rules describe scores from 2–9 as a weak capability and 10–11 as the human average, but they do not prescribe a personality or mannerism for each number.

For roleplay, decide what happens when the character tries to make an impression. A scarred undead with high Charisma might be composed, magnetic, terrifyingly articulate, or impossible to ignore. One with low Charisma might be unsettling but poor at directing that reaction, easily misunderstood, or socially withdrawn.

NPCs can still react to an unusual appearance according to the situation. That fictional reaction is separate from the character’s underlying Charisma score.

Rules reference: D&D 5e SRD 5.2.1 — Ability Scores and Charisma.

A monster's XP value is determined from its Challenge Rating, not by separately adding up its hit points, Armor Class, attacks, and other statistics. In the 5e rules, each Challenge Rating maps to a fixed XP value on the XP-by-Challenge-Rating table.

So if a published monster already has a Challenge Rating, the procedure is simple: read its CR and use the corresponding XP entry. For example, CR 1 is worth 200 XP, CR 2 is worth 450 XP, CR 5 is worth 1,800 XP, and the table continues through CR 30. The rules also state that XP can be awarded for defeating a monster in combat or neutralizing it in another way.

A custom monster is a different problem. You first need to determine an appropriate Challenge Rating using whatever monster-building guidance your game is using; the XP table does not itself calculate CR from raw statistics. Do not assign XP by improvising a formula from damage or hit points alone.

For encounter preparation, keep the two steps separate: establish or verify the creature's CR, then convert that CR to XP. That makes the XP award consistent with the same rating used to judge the monster's overall threat.

Look for a monster trait that explicitly allows movement through creatures and objects; in the current 5e rules, that trait is commonly called Incorporeal Movement. It lets the creature pass through an object as difficult terrain, so an ordinary wall or closed door does not stop that movement.

Examples in the 5.2.1 rules include the wraith, specter, ghost, and will-o'-wisp. Their versions of Incorporeal Movement also impose 1d10 force damage if the creature ends its turn inside an object. That matters tactically: the monster can emerge through a wall, attack, and retreat, but remaining embedded in solid material carries a cost.

Do not assume every ghostly, ethereal, or flying creature can do this. A monster needs text that permits passage through objects, or another specific ability that produces the same result. Likewise, a burrowing speed normally does not let a creature tunnel through solid rock unless a trait says it can.

For encounter design, use wall-passing sparingly and telegraph it. A cold spot, voice through stone, or attack from an impossible angle gives players information they can react to instead of making the ability feel like an arbitrary ambush.

Yes, the two properties are not inherently contradictory: Two-Handed governs how many hands are required to attack with the weapon, while Light governs the special interaction available to Light weapons.

A weapon being Light does not by itself mean that it must be wielded in one hand. Likewise, Two-Handed does not say that a weapon cannot possess other properties. If a homebrew weapon has both, apply each property according to its own text.

Under the current Light-weapon rule, however, the follow-up attack involves a different Light weapon. That makes a two-handed Light weapon mechanically awkward in normal play because the character still has to satisfy the hand requirements of the weapons involved. The Light property should not be treated as an unstated exception to those requirements.

For homebrew design, decide what behavior you actually want before assigning the keywords. If the intention is simply 'easy to handle despite its size,' the Light property may introduce interactions you did not intend. If the intention is to permit a special one-handed use, write that exception explicitly instead of assuming Light provides it.

The properties can coexist; whether the combination produces a useful weapon is a separate design question.

The quoted Paper Bird wording does not make the item a reliable detector of false names. It says that you speak a creature's name and the bird flies to the recipient, but the text you provided does not define “name” as a secret true name, legal name, birth name, or verified identity.

That leaves an adjudication gap. I would treat the spoken name as an identifier the magic uses together with the sender's intended recipient. If the characters know someone as “Mara,” the bird can seek that person even if Mara is an alias, because nothing in the quoted effect says a false name causes failure or reveals deception.

The same principle avoids turning the item into an accidental doppelganger test. If a replacement is presenting itself under the victim's name, decide which creature the sender actually means. If the sender means the original victim and that person is dead or otherwise unreachable, resolve the item according to its normal delivery limitations rather than redirecting it solely because another creature is using the name.

The complete Paper Bird rules are not in SRD 5.2.1, so this is a practical reading of the supplied text, not a verified SRD rule about aliases or true names.

No. Under the current D&D 5e wording, the audible version of Alarm produces a handbell sound for 10 seconds that is audible within 60 feet of the warded area. The spell does not provide ordinary audibility beyond that distance.

That 60-foot limit is tied to the warded area, not to the caster's current location. Alarm can ward a door, window, or area within the spell's range when cast; once triggered, creatures close enough to that warded area can hear the bell. Someone farther away does not get to hear it merely because the surroundings are otherwise quiet.

The mental version works differently. It alerts the caster mentally if the caster is within 1 mile of the warded area, and it wakes the caster if sleeping. It is therefore the built-in option for receiving the warning at a much greater distance.

At the table, I would treat the stated distances as the spell's defined magical effects rather than trying to model real-world sound propagation. If you want an alarm that alerts an entire fortress or carries farther through corridors, add a separate bell, messenger, linked magic effect, or explicit house rule instead of silently extending the spell.

Identify is not limited by an item's rarity or power in the general rule. When you cast it on a magic item, you learn the item's properties and how to use them, whether it requires attunement, and how many charges it has if applicable. You also learn what spells are affecting it, and the name of a spell that created it when relevant.

That does not mean Identify reveals everything about every exceptional item. The current magic-item rules specifically say that most methods of identifying an item, including the Identify spell, do not reveal a curse. A cursed sword can therefore disclose its ordinary magical properties while keeping the curse hidden unless a specific rule says otherwise.

Artifacts are also special in some ways: for example, the general rules say they can be destroyed only by a special method and are otherwise immune to damage. But there is no general rule saying that artifact status by itself defeats Identify. If a particular item's description creates an exception, that specific text takes priority.

So for a “high-end” item, begin with Identify's normal information, then check the item's own rules for hidden properties, curses, or explicit exceptions. Power level alone is not a reason to make the spell fail.

A changeling secret is usually more satisfying when several clues create suspicion before magic finally confirms it. Detect Evil and Good is not a general changeling detector: the spell locates specific creature types, not “shapechangers” as a category. Moonbeam is more relevant because its current text can force a creature that has changed shape back to its true form after a failed Constitution save. The exact interaction still depends on the Changeling feature text being used at your table.

For accidental exposure, give the disguise pressure points that can fail naturally. Someone from the Feywild may ask about a custom, family, place, or memory the character cannot convincingly explain. An observer may notice that the supposed eladrin never displays expected changes in appearance or behavior. A crisis can be stronger than an investigation: the character might need to change shape publicly to escape, impersonate someone, or save an ally.

The best reveal does not have to be a binary trap. Let small inconsistencies accumulate, then give the player a meaningful choice about whether preserving the secret is worth the cost.

If the entire party is trapped inside a Mirror of Life Trapping, the RAW escape options from inside are extremely limited: a trapped creature can escape its cell by using magic that allows planar travel. Otherwise it remains confined until something outside the cell releases it.

The mirror itself provides several external release mechanisms. A creature near the mirror can use its release command word to free a named prisoner. Destroying the mirror releases every trapped creature. If all twelve extradimensional cells are occupied and the active mirror traps another creature, it also releases one existing prisoner at random to make room.

That distinction matters when the whole adventuring party is already inside. They cannot simply search the cell for a hidden latch or attack the mirror from within unless the DM adds such an option. If nobody has suitable planar magic, progress depends on the outside world: an ally, enemy, curious stranger, or later victim can interact with the mirror.

For adventure design, use that dependency to create play rather than a dead end. An NPC might bargain for a release, the captor may question prisoners through the mirror, or an outside ally may need instructions. Any new escape route is a campaign ruling, so present it as an added circumstance rather than as RAW.

In the 2024 D&D 5e rules, starting ability score increases come from your background, not your class. A standard background lists three ability scores. You either raise one of those by 2 and a different one by 1, or raise all three by 1; none of those increases can take a score above 20. Your class still tells you which ability is its primary one and what tends to matter for its features, but it does not hand out the starting +2/+1.

That means “put +2 and +1 anywhere” is only partly accurate. With a published background, your choices are limited to that background’s three listed abilities. The rules for creating a background also let that background choose three appropriate ability scores before applying the same +2/+1 or +1/+1/+1 pattern. If your table is using a custom background, you may therefore have more freedom.

When checking a character, look at the background first, then apply its ability score options. Treat class recommendations as build guidance, not as the source of those starting increases.

Cosmic Omen is not obviously underpowered just because its number is small; roll manipulation is valuable when it changes an outcome rather than merely adding average damage. A d6 averages 3.5, but the important question is how often that modifier turns a near miss into a hit, a failed saving throw into a success, or the reverse for an enemy.

Judge the feature on three axes. First, timing: a modifier is much stronger if you can apply it when a roll is already close to the target. Second, action economy: an effect that does not consume the action you wanted to spend on a spell or attack can add value without replacing your normal turn. Third, frequency: unused charges are worth nothing, while a few well-timed uses can decide important moments.

That still may not make the feature satisfying for you. Summons, transformations, and new actions visibly change how a character plays; a quiet probability adjustment may feel less exciting even when it performs well. Separate “does this meaningfully change outcomes?” from “does this make level 6 feel different?” before deciding the subclass is weak.

Start with the character’s history, then translate that history into the background mechanics. The current rules already give the DM an official route for doing this: the SRD describes creating a unique background or customizing an existing one to fit a campaign or a player’s character story.

Write the concept in one sentence first—for example, “grew up maintaining remote lighthouses on a dangerous coast.” Then choose the three appropriate abilities, an Origin feat, two skill proficiencies, one tool proficiency, and an equipment package that follow from that life. Those mechanical choices should express the concept rather than replace it.

Keep nonmechanical history outside the bonus package. Contacts, former employers, debts, beliefs, family ties, reputations, habits, and meaningful possessions can matter in play even when they grant no numerical benefit. In fact, those details often give the DM more useful hooks than another proficiency.

If the table uses only preset backgrounds, discuss the constraint before character creation. A preset can be convenient, but it should not force a player to rewrite an otherwise coherent history merely to obtain useful abilities.

The clean separation is: mechanics describe what the past trained the character to do; fiction describes who was there, what happened, and what can return to matter now.

Use passive Perception for a character's general awareness when the DM is checking whether they notice something without actively searching; use a Wisdom (Perception) check when the character is actively trying to notice something and the outcome is uncertain. Those are related tools, not interchangeable versions of the same roll.

In the 5e rules, passive Perception is 10 plus the character's modifier for Wisdom (Perception), including applicable modifiers. It represents what the character may notice without the DM asking for a roll. The Search action, by contrast, can call for a Wisdom check using Perception when a character deliberately looks, listens, or otherwise searches.

Passive Perception is therefore not automatically a minimum result for every active Perception check. If a character actively rolls and the total is lower than their passive score, that does not by itself mean the roll should be replaced.

At the table, describe anything obvious without a check. Use passive Perception when hidden information may be noticed incidentally, and call for an active check when a player's declared method creates genuine uncertainty. This keeps Perception from becoming a repetitive “roll whenever you enter a room” procedure.

No saving throw becomes inherently more valuable just because the characters reach a particular level; its practical importance depends on which effects the campaign uses and what failure costs. The rules assign different abilities to different kinds of threats, and the effect causing the save determines the consequence of failure.

That distinction matters more at high level because losing hit points is only one way an encounter can become dangerous. A failed save can also remove actions, impose a debilitating condition, change a character's behavior, separate someone from the group, or otherwise damage the party's action economy. In an encounter where those effects target Wisdom, for example, a reliable Wisdom save may matter more than avoiding another instance of ordinary damage.

Proficiency also matters. A character adds their Proficiency Bonus only to saving throws in which they are proficient. As characters advance, proficient saves therefore receive an increasing bonus while an unproficient save does not automatically gain that benefit. Against increasingly difficult effects, a weak save can remain a significant vulnerability.

For encounter design, do not turn that observation into a fixed hierarchy such as "Wisdom is always better than Dexterity." Examine what failure actually does. Damage, lost turns, forced movement, concentration loss, control, and character removal create different kinds of pressure.

High-level encounters become more varied when the DM tests several defenses and varies the consequences, rather than repeatedly attacking Armor Class or the same favored saving throw.

Give an obscure rule a short lookup window, make a provisional ruling if the answer is still unclear, and verify it after the session. The goal is not to know every rule from memory; it is to prevent one uncertain interaction from consuming the table's attention.

A practical procedure is to give the lookup about two minutes. Ask the player proposing the interaction to find the actual relevant text while you keep track of the scene. Once it is found, first establish what the rule says, then decide whether any other rule or specific feature modifies it. Reading the wording aloud is usually more useful than debating what somebody remembers the rule doing.

If the answer remains ambiguous, announce a temporary ruling and continue. Write down the question so it does not disappear once play resumes. After the session, check the relevant rules carefully and tell the group what interpretation will apply in future sessions.

Avoid retroactively reconstructing ordinary scenes every time a ruling turns out to be wrong. Correct the rule going forward unless the mistake materially changed something important, such as a character death or a major irreversible consequence.

Players with unusual combinations can also help by flagging them before play. The DM remains the adjudicator, but rules knowledge does not need to be a one-person workload. A consistent fast-ruling procedure preserves both fairness and momentum better than either guessing confidently or stopping the game for a twenty-minute rules investigation.

Count the encounter as overcome when the characters have meaningfully neutralized the challenge, not only when they kill whatever was opposing them.

For D&D 5e, the rules explicitly say that characters earn XP as they overcome challenges and complete adventures, and that a monster's XP can be awarded for defeating it in combat or otherwise neutralizing it. Killing is therefore not the required method. ([D&D Beyond][1])

At the table, judge the result by the obstacle's function. If a guard exists to stop the characters entering a building, bribing the guard can fully overcome that challenge if the agreement genuinely gives them the access they needed. Distracting the guard for thirty seconds can also be enough if thirty seconds is all the plan requires. Persuasion, stealth, deception, intimidation, trapping an enemy, forcing a retreat, or arranging safe passage can all change the situation decisively.

The important distinction is between resolving an obstacle and merely postponing it. If the guard realizes the deception moments later and begins pursuing the party, the challenge has changed but may not be finished. Similarly, avoid awarding the same monster's full XP once for bypassing it and again simply because the party later fights the same unresolved opposition.

Ask one practical question: did the characters' choice change the state of the scenario enough that this obstacle no longer prevents the objective they were pursuing? If yes, treat the solution as meaningful even when no initiative was rolled.

A Beast Master companion’s reaction attacks depend on the exact subclass feature text; the general 2024 reaction rules alone are not enough to confirm a flat yes or no. A reaction is an immediate response to a trigger, and after a creature takes one it cannot take another until the start of its next turn. An opportunity attack is a common example: when a visible creature leaves your reach, you can use a Reaction to make a melee weapon attack or an unarmed strike.

What still has to be checked is whether the Beast Master companion’s rules grant, restrict, or replace that normal reaction use. Read the feature for three separate points: whether the companion functions as a creature with its own Reaction, which actions it may take without a command, and whether any command restriction explicitly includes reactions rather than only actions on its turn.

Do not infer the answer solely from how the Ranger commands the beast on its turn. Until the specific Beast Master wording is checked, treat reaction attacks as a provisional table ruling rather than confirmed RAW, especially if a character build depends on them.

A natural 20 on a Perception check is not automatically a success in D&D 5e. Automatic success on a natural 20 is a rule for attack rolls; an ability check succeeds when the total result meets or exceeds the DC.

That also means a 20 does not let a character perceive something that cannot be perceived. If a secret is behind a solid wall with no sensory clue, or the character is looking in the wrong place, a high Perception result does not create information from nowhere. The DM should call for a check only when success and failure are both genuinely possible.

When the total does succeed, give the player the strongest information the character could reasonably obtain from that method. A very high result can justify clearer detail, noticing secondary clues, or reducing ambiguity, but that is adjudication rather than a special critical-success rule.

If the player rolled without being asked, first decide whether a check was appropriate at all. You do not need to invent a hidden door or bonus discovery simply because the die showed 20. Reward good observation with useful, actionable description, not with information that breaks the fiction.

No, not by the Charmed condition alone. Being Charmed restricts how you can act against the creature that charmed you and gives that creature an advantage in social interaction; it does not say that you automatically believe the charmer, lose awareness of contradictions, or stop receiving information from other effects.

For a lie-detecting magic item, read the item’s own text next. If it passively vibrates whenever its wearer is told a lie and it has no exception for Charmed creatures, the condition does not inherently switch the item off. The wearer could therefore notice the vibration while still being Charmed.

What that information means is a separate question. A Charmed character can know that a statement appears false and still be constrained by the condition’s actual effects. The DM can describe the resulting tension: the item warns the character, but the magical influence still affects what actions are available toward the charmer.

If the earrings are homebrew, their wording controls the unresolved details. Decide whether they detect deliberate lies, factual falsehoods, half-truths, or mistaken statements. Those definitions matter more to the item than the Charmed condition itself and should be established consistently before the next ambiguous case.

For a level 5 game using the 2024 rules, the higher-level starting-equipment guideline is normal starting equipment plus 500 gp, plus 1d10 × 25 gp, plus one common and one uncommon magic item. That is a useful baseline, not a requirement that every one-shot must put that much spendable cash into a market scene.

For a one-shot, work backward from the choices you want the market to create. Pick three or four purchases that could matter later—healing, a tool, useful ammunition, a clue-bearing curiosity, or a situational consumable—and price them so one character cannot simply buy everything. If the stalls mostly sell mundane goods, the listed equipment prices are a good anchor.

Haggling works better with a floor than with unlimited percentage reductions. Decide each seller’s normal price and lowest acceptable price before play. A good Persuasion result might move the offer toward that floor, add a small extra item, or reveal a cheaper alternative. That keeps the social scene meaningful without letting one high roll erase the economic choices the market was meant to create.

Land's Aid is underwhelming when only half of the feature matters, but considerably better when the same action both hurts several enemies and restores an ally. Its value comes from combining effects, not from competing with dedicated damage or healing options one at a time.

The feature uses a Magic action and one Wild Shape use. You choose a point within 60 feet, creating a 10-foot-radius area. Creatures you choose there make Constitution saves, taking 2d6 necrotic damage on a failure and half on a success, while one creature in the area regains 2d6 hit points. Both amounts rise to 3d6 at druid level 10 and 4d6 at level 14.

That makes positioning the real test. Hitting one enemy while nobody needs healing is usually a poor use of an action. Healing one ally while catching no worthwhile enemies also wastes much of the feature. Catch two or three enemies around an injured ally, however, and one action is solving two problems without spending a spell slot.

The Wild Shape cost also matters differently from a spell slot because a druid recovers one expended Wild Shape use after a Short Rest and all uses after a Long Rest. Judge Land's Aid by how often your combats produce those combined-use situations. If they rarely do, it will feel weak even though its maximum turn can be efficient.

Correct the mistake according to how much it changed a player's decision, not according to how embarrassed the DM feels about getting the rule wrong. Most errors need a brief correction and continued play; only some justify rewinding consequences.

First ask whether somebody made a meaningful choice because of the incorrect ruling. Did a player spend a spell slot, use a limited feature, expose a character to danger, abandon another plan, or lose an opportunity they would reasonably have taken? If so, repair that specific cost when practical. Restore the resource, revise one immediate consequence, or return the affected choice to the player.

If the error did not materially change a decision, fix the rule going forward. Reconstructing several turns or half a session to achieve perfect historical accuracy often damages pacing more than the original mistake did.

The same applies when a clever player action unexpectedly trivializes an encounter. That is not automatically a DM failure. If the action works under the agreed rules and the fictional circumstances support it, let the success matter. The next challenge can respond to what happened instead of forcing the current scene to reach its planned difficulty.

Explain the correction briefly and avoid turning it into a defense of the DM's competence. Players can dislike an outcome without trust being broken. Trust is more likely to suffer when rulings visibly change to preserve the DM's preferred result or when a correction erases a choice that was made in good faith.

There is no general D&D 5e rule establishing how real-world drugs interact with thri-kreen or other insectoid physiology, so treat this as a consistent setting ruling rather than trying to calculate it from real entomology. Creature rules can give particular beings resistances or immunities to poison, but that does not create a universal rule for everything that resembles an insect.

Decide first what kind of physiology the creature has in your setting. It might process humanoid substances normally, require much larger doses, react strongly to substances harmless to humans, or be unable to metabolize them at all. You do not need a separate pharmacology system for every species; two or three broad traits are usually enough.

Mechanically, translate the substance into game effects rather than real dosage calculations. Choose an onset time, duration, an appropriate Constitution save if resistance is uncertain, and consequences such as the Poisoned condition, altered speed, disadvantage on a narrow category of checks, or another specific effect. Particularly incompatible substances can simply be ineffective or dangerous.

Write the ruling down once it matters. Consistency will make the fictional biology feel intentional, while still leaving room for individual creatures with explicit resistances, immunities, or unusual metabolisms.

No: a paladin should not become an oathbreaker merely because their deity broke an agreement the paladin did not choose to violate. Nothing in the core paladin mechanics transfers a deity's breach into an automatic loss of the character's class features.

If the deity rescues the paladin, make the divine intervention create consequences for the deity's conflict rather than punishing the player for information they never possessed. The rescue might expose the deity's disobedience, alert the rival power, place a visible mark on the paladin, create recurring visions, or leave the character owing a specific service. Those complications generate future decisions without dismantling the player's character.

The intervention can also reveal part of the hidden divine politics without becoming a complete lore dump. Let the paladin understand enough to realize that the rescue cost something, then allow later investigation and encounters to uncover why.

If you genuinely want the event to alter the paladin's subclass or mechanical abilities, discuss that change with the player first. A class transformation works best when it expresses a choice the character makes. Here, the more interesting oathbreaking belongs to the god, so let that breach reshape the world around the paladin instead.

The Help action should grant Advantage under the 2024 rules; adding the helper’s skill modifier would be a house rule, not RAW. For an ability check, the helper chooses one of their own skill or tool proficiencies and an ally close enough to assist. That ally gets Advantage on the next check using that skill or tool before the helper’s next turn, and the GM decides whether the assistance is actually possible. Help with an attack instead distracts an enemy within 5 feet and gives Advantage on the next allied attack against it.

Replacing Advantage with the helper’s full modifier creates a different scaling problem. A highly specialized character could become a portable bonus for someone else, and that bonus could stack with Advantage from another source. The result rewards modifier stacking more than cooperation.

If the goal is to make the quality of the helper matter, keep the existing math and make the fiction carry that distinction. Require a plausible method of assistance, enforce the proficiency requirement for ability-check Help, and refuse Help when a second person cannot meaningfully contribute. That keeps cooperation concrete without turning every task into bonus arithmetic.

First decide whether the attempted theft is physically possible; if it is, Dexterity with Sleight of Hand proficiency is usually the most appropriate check for covert manipulation. D&D 5e does not require a roll simply because a player describes an unusual action: the DM first determines how the action can be resolved and calls for a check when the outcome is genuinely uncertain.

Sleight of Hand fits when the challenge is secretly manipulating or removing an accessible object without the other person noticing. Acrobatics would normally be relevant only if agility, balance, or unusual body movement were actually the obstacle. Performance or another Charisma-based approach might matter if the character first needs to convincingly create a distraction, but that is a different problem from physically taking the item.

Avoid automatically turning one strange action into a chain of three or four checks. Decide what the important uncertainty is. If the distraction is already established, one Dexterity check may be enough. If both gaining the person's cooperation and stealing the object are uncertain and independently consequential, resolving them separately can make sense.

The original golden-teeth example also demonstrates an important limit: a die roll does not make an impossible action possible. If the teeth are firmly attached, they cannot simply be pickpocketed during a kiss. The player would need a plausible method of removing them first, with whatever consequences that method creates.

Advantage and Disadvantage lose nuance when several meaningful circumstances collapse into the same mechanical result, but a DM can preserve those circumstances without making the dice mechanic more complicated. Rules-wise, multiple sources of Advantage do not stack, multiple sources of Disadvantage do not stack, and a roll affected by both has neither, regardless of how many sources exist on either side.

That simplicity is useful for speed, but it means a carefully prepared ambush and a small moment of assistance can both produce the same two-d20 roll. Rather than adding extra d20s, let additional favorable circumstances change what the roll can accomplish or what failure costs.

For example, Advantage might already represent attacking from concealment. A second favorable factor could mean the character also has an escape route, avoids exposing an ally, identifies the enemy leader before attacking, or retains good cover if the attack misses. Several disadvantages can work the same way: one may impose Disadvantage while another worsens the consequence of failure, restricts movement, or creates a new problem in the scene.

This keeps the core resolution quick while allowing the fiction to remember that three good ideas are better than one. If a table instead wants stacking numerical modifiers, make that an explicit and consistent house rule rather than improvising different bonuses whenever the standard mechanic feels insufficient.

Under the 2014 passages quoted in the question, the crafting procedure does not provide a normal rules path for creating a legendary item. The general rule requires a formula before crafting begins, while the formula guidance says legendary-item formulas do not exist. A listed cost or time does not, by itself, remove that prerequisite.

That does not mean legendary items cannot exist in the setting. The downtime rules are a procedure available to characters; they are not necessarily a complete historical account of how every relic in the world was made. A legendary item could come from a lost method, divine intervention, an extinct civilization, a unique event, or some other origin the campaign does not model with ordinary crafting.

For player characters, the clean approach is to decide which layer you want. If you are using those 2014 crafting rules strictly, legendary creation needs an explicit exception or a different procedure. If the campaign is meant to support legendary crafting, establish the exception openly—perhaps a unique blueprint, impossible component, location, or quest—rather than pretending the quoted formula restriction is not there.

The important distinction is between the existence of legendary items in the fiction and access to a standard crafting recipe.