D100 Curses Table

Overview

A compiled d100 curse table from r/DMAcademy community. Each curse creates specific mechanical or roleplay constraints that generate play consequences rather than fixed outcomes, making curses into campaign-shaping complications rather than simple debuffs.

Curse Taxonomy

The raw table groups naturally into several referee-useful categories:

Mechanical/Movement Curses

Curses that directly restrict action options or combat capability: - Directional constraints (cannot turn right, eyes/feet repositioned) - Weight and mobility effects (feet sink, heavy weapons, swimming failure) - Environmental interaction restrictions (cannot open twist-locks, compelled sprint in corridors)

Referee utility: These curses generate navigational puzzles and force creative problem-solving in dungeons and hexcrawls.

Sensory/Perception Curses

Curses that alter how the character perceives or is perceived: - Perception inversion (can't see people, can't see traps, reversed light/dark vision) - False perception (believes in nonexistent traps, body-swap delusion) - Selective invisibility (one species invisible, personal darkness aura)

Referee utility: These curses create asymmetrical party dynamics and reward player improvisation over straight problem-solving.

Communication/Expression Curses

Curses that restrict language, speech, or expression: - Forced speech patterns (must speak in rhyme, compulsive monologues, random volume) - Speech impediments (must repeat words, cannot control tone, gibberish on spellcasting) - Behavioral compulsion (must answer only with lies, must agree to suggestions, must hug everyone)

Referee utility: These curses actively interfere with standard social encounters and negotiation, forcing creative NPC interaction tactics.

Economic/Resource Curses

Curses affecting money, supplies, and equipment: - Gear displacement (armor teleports away, weapon material shifts, equipment glows) - Coin degradation (gold to silver to copper, coins to wooden toys) - Consumption pressure (must eat 4x normal, alcohol intoxication amplified)

Referee utility: These curses create logistical pressure that feeds back into expedition planning and shopping downtime.

Death/Consequence Curses

Curses that introduce death pressure or forced action: - Scaling death threat (instant death on monster CR roll, must kill one humanoid per week) - Forced action (must read new book weekly, must close every door) - Reversal mechanics (gravity inverts at dawn, instant healing but must kill daily)

Referee utility: These curses create hard tactical pressure but with clear escape paths through play — useful for injecting urgency into flagging campaigns.

Temporal/Cyclical Curses

Curses that trigger on time basis or repetition: - Daily cycles (languages randomize after rest, gravity reversal at dawn) - Multi-day effects (immediate task success but delayed explosion, progressively worsening nightmares) - Contingent triggers (next item grabbed is bound forever, any ritual after curse succeeds then burns)

Referee utility: These curses create campaign momentum and session-to-session narrative arcs.

Curse Application Procedures

Pre-Curse Setup

Use this workflow to introduce curses into play:

Identify the curse source: enemy spellcaster, trapped treasure, NPC deal gone wrong, divine punishment.
Choose curse category match: pick a category that creates desired play friction.
Set removal condition: standard (dispel, remove curse), earned (quest-driven), or permanent-until-end.
Communicate mechanical scope clearly to player before first game session under curse.

At-Table Resolution Loop

When curse effects trigger:

Announce trigger: clearly state what condition activated the curse.
Resolve mechanical impact: if saving throw or check required, resolve before narrative frame.
Name the consequence: describe the in-fiction effect (not just "disadvantage on stealth" but "your boots squeak loudly").
Invite creative workaround: ask player what they do in response; many curse effects have discoverable solutions.

Long-Term Campaign Integration

Track curse effects across sessions:

Session 0: curse imposed or discovered.
Session 1-2: initial friction; player learns curse scope.
Session 3+: player develops workarounds or seeks removal quest.
Resolution point: cure achieved, curse adapted-to, or character accepts it as permanent identity trait.

Design Principles

Strong curse design in this table follows three patterns:

Constraints are specific, not punitive: curses create new choices rather than close off options. Example: "must wear shoes causing pain" creates tension between armor and comfort, not a simple nerf.
Effects interlock with player skill and creativity: many curses have discoverable workarounds that reward clever thinking. Example: "cannot turn right" can be managed with party positioning or by moving backwards.
Narrative hooks emerge from mechanical constraint: the curse becomes a story element, not just a penalty. Example: "stalked by invisible imp" generates NPCs responses and creates future complications naturally.

Referee Tooling Value

For campaign design, this table is useful as:

Downtime complication source: introduce curses during town turns or faction cycles.
Enemy ability substitute: use curses as faction magic effects to introduce into hexcrawl/wilderness encounters.
Consequences for player actions: curse as payment for forbidden pacts, resource theft, or territorial violation.
Equipment or ability tie-ins: "cursed relics" become playable loot with mechanical meaning.

Conversion Notes for System-Agnostic Use

The source is D&D5e-adjacent but many effects translate cleanly:

Ability checks/saves: shift to opposed rolls, attribute tests, or simple save-DC paradigms.
Hit points and damage: mechanical effects work on attrition/exhaustion systems too.
Spell-triggered effects: adapt to any spellcasting framework by triggering on ability use instead.
Duration language: "until curse lifted" works on any system; scale durations to your session length (1d4 hours = 1d4 rounds in fast time).