Start with the exact wording

Most apparent contradictions become easier when the group reads the actual text of:

1. the feature, spell, item or monster ability involved; 2. the relevant general rule; 3. any explicit exception.

Do not adjudicate from a feature name alone.

Specific exceptions matter

A feature that says it can do something the general rule does not normally allow is often intentionally creating an exception.

For example, Cunning Action explicitly allows a Rogue to take certain actions as a bonus action. The general rule that those actions ordinarily use an action does not invalidate the class feature.

The DM resolves remaining ambiguity

If the written rules do not settle the situation, the DM decides how it works for the current game.

A good ruling should usually be:

  • understandable;
  • consistent enough that players can plan around it;
  • proportionate to the situation;
  • easy to revisit if a more specific published rule or later clarification resolves the issue.

A quick ruling can be better than stopping play

Not every edge case requires a long rules investigation during a session.

For a low-stakes ambiguity, the DM can make a temporary ruling, continue play and verify the source afterward.

If the question materially changes a character's build or a major encounter, spending more time verifying it may be justified.

Document recurring decisions

If the same interaction is likely to recur, D&D Portal can store the decision as a campaign rule or note.

The note should record:

  • which campaign or parties it affects;
  • the ruling itself;
  • whether it replaces or interprets a published rule;
  • the source rule being modified when relevant.

Keep unresolved rules visibly unresolved

If the available source is incomplete or conflicting, treat the point as unresolved rather than inventing a rule.

If a source question remains unresolved, treat that point as unresolved until the relevant source can be verified.

That is preferable to publishing a clean but fabricated mechanic.