An oracle table is a way to ask chance a narrow question. It does not write the story for you, replace consent, or prove what must happen. It gives you friction, color, pressure, or a direction so you can make the next choice.
Ask a Smaller Question
Weak oracle questions are huge: “What happens?” or “Is the town bad?” Stronger questions name the decision point: “Does the guard recognize my symbol?” “What useful detail is in the room?” “What complication appears before I leave?” “Is the rumor mostly true?”
If the question is too broad, any answer will feel arbitrary. If it is too narrow, the oracle cannot surprise you. Aim for a question that changes the next scene.
Pick the Table Shape
Use a d6 table for simple choices. Use d20 when you want variety. Use 2d6 when common results should happen more often than extremes. Use cards when suit or color can carry meaning. Use a coin only for questions where yes/no is actually useful.
Write rows in your own words. If you are adapting a published game, follow the license and do not repost protected tables.
Keep Boundaries Active
Every table should have a veto rule. If a result breaks the age rating, content note, accessibility need, or tone, reroll or replace it. That is not cheating. The player remains responsible for the table.
The Oracle Table Builder can help you choose a shape, but the rows should fit your session and boundaries.
Interpret in Context
Do not read the result as a disconnected command. Read it through the current place, character, weather, resource, and open question. “Delay” means something different in a quiet bakery, a dungeon corridor, and a winter road.
After interpretation, move. Add a clue, cost, offer, danger, or sensory detail. Then return to play.
