Oracle Table Builder Method: Make Random Prompts That Actually Help

Use the Oracle Table Builder tool to create table sizes, tone bands, useful prompt categories, and boundary rules for solo play.

An oracle table building desk with blank table cards, dice, boundary tokens, category markers, and a notebook.
A useful oracle table starts with purpose, tone, and a boundary filter.
On this page

The Oracle Table Builder helps you design a table brief. It does not replace your judgment. The most useful output is a short structure you can fill with original rows that fit the current campaign.

Start With Purpose

Choose what the table is for: scene direction, encounter, sensory detail, complication, or yes/no oracle. Purpose keeps the rows from becoming a random pile of vibes.

Write the purpose as a question. “What complicates this route?” produces different rows than “What do I notice in the market?” A table that answers one question clearly is easier to use than a table that tries to be setting, mood, danger, clue, and plot all at once.

In the builder, choose that purpose, a randomizer, a tone, an uncertainty level, and a boundary filter. The result gives you a table shape, a question frame, and guidance for stakes and boundaries; it is a brief, not a finished set of random rows. Copy the useful parts into your notebook and make them specific to your game. Low uncertainty favors color and gentle movement; high uncertainty suggests more consequential results with ways to recover.

Choose a Randomizer

Match the table to what you have and how much variety you want:

RandomizerHow to write and use the table
d6Write six numbered rows and roll once. With a fair die, each row has a 1-in-6 chance.
d20Write 20 numbered rows and roll once. Each row has a 1-in-20 chance with a fair die.
2d6Write results for totals 2 through 12. Roll two six-sided dice and add them: 7 has six combinations out of 36, while 2 and 12 have one each. Put common results near the middle and rare ones at the ends.
Playing cardsAssign a prompt to each rank, or use the four suits as categories. Decide whether to reshuffle after each draw; without reshuffling, earlier draws change what remains possible.

You can combine neighboring 2d6 totals into one result, but their probabilities add together. If you want equally likely rows, use one die with one row per face instead. For a yes/no table, decide which numbers mean yes and no before rolling; the beginner oracle guide includes a six-result example.

Set Tone and Boundary

Choose gentle, strange, tense, or mixed tone. Then select a boundary filter: ordinary table, kid-nearby friendly, soft content only, or intense but bounded. These are prompts for your own decisions, not guarantees that every row or interpretation will fit. Check the rows yourself before using them.

Write at least two veto rules before filling rows. For example: no harm to children, no graphic injury, no sexual threat, no copied setting secrets, no real-world hate, or no results that force the character into cruelty. Choose the exclusions that matter to you and anyone sharing the space. You can also note subjects that may appear only indirectly or off-page.

If a result crosses a boundary, stop and replace or reroll it; you can revise the table for next time. A label such as kid-nearby is not an age rating, so consider what someone else might see or overhear. The guide to encounter tables with consent boundaries offers a way to record lines and softer limits.

Fill Rows in Your Own Words

Write rows that create playable movement: clue, cost, offer, delay, resource, mood, person, exit, or question. Mix direct and interpretive rows. “A locked gate” is concrete. “Someone benefits from delay” is flexible. “A useful tool breaks” creates cost. “A witness changes their story” creates motion. If every row is vague, the table may not help; if every row is too specific, it may fight the scene.

Write your own prompts rather than copying a published table. If you adapt or share material from a source, check its license or obtain permission where needed. Keep the row short enough to scan, and leave the player a choice about what happens next.

Build a Small Table

Suppose a courier is trying to reach a hillside village before nightfall. In the builder, choose Complication, d6, Gentle, Low, and Soft content only. Use the question “What complicates this route?” Add two lines: no graphic injury and no forced cruelty. Then write six original rows:

d6Route complication
1The direct path is blocked; a longer route is open.
2A traveler offers directions in exchange for a small favor.
3A familiar landmark is missing; the courier must check the map.
4Rain threatens the delivery; shelter is nearby but costs time.
5A useful tool needs a quick repair before the climb.
6A shortcut is available, but using it means leaving a clear trail.

A roll of 4 might mean the courier can shelter the package under a bridge or press on and risk a wet delivery. Decide which consequence fits the game, then make the choice. The row adds pressure without deciding the courier’s action for you. If the game has rules for time or damaged supplies, use them; otherwise, make a simple note of the consequence.

Test One Scene

Try three rolls as separate possibilities for the same sample scene. Interpret each in context and ask: does it answer the question, fit the chosen boundaries, and give me something to do? If one result is unclear, rewrite it. If several feel alike or do not help, change categories before adding more rows. Three rolls are a quick usability check, not proof that the table is balanced; revisit it after actual play.

Mark each row as keep, clarify, soften, or replace. A row that needs five minutes of interpretation may not be bad, but it may belong on a different table. Keep the finished table short enough that you will actually reach for it during play. For a stalled scene, the guide to balancing randomness and choice can help you decide when to roll and when to choose.

Written By

JJ Ben-Joseph

Founder and CEO ยท TensorSpace

Founder and CEO of TensorSpace and the editor of Fondsites: an engineer working across software, AI, cybersecurity, and biosecurity who builds the site's games and tools.

Keep reading